Spring Web Services 1.5.0 Release Candidate 1 released

[Arjen Poutsma]

Dear Spring community,

I'm pleased to announce that Spring Web Services 1.5.0 RC1 has been released! This release candidate release introduces:

• WS-Addressing support for both client and server, supporting the August 2004 and final versions of the specification,
• A new and improved XSD-to-WSDL generator that inlines included and import XSDs,
• Support for Spring Security
• Support for the Java 6 HTTP Server
• Two new samples, showing Plain Old XML usage and WS-Addressing with the Java 6 HTTP server

Additionally, there are other minor improvements and bug fixes.

Spring-WS 1.5.0 RC1 is the first milestone in the 1.5 series, which is now feature complete. The 1.5.0 series is 95% backwards compatible, though support for Java 1.3 has been dropped, in favor of Java 1.6. Java 6 is required to build.

The next release in this branch will be 1.5.0, to be released around the 28th of March, unless a second release candidate is required. After 1.5.0 final has been released, there will be a 1.0.4, backporting all bugfixes in the 1.5 branch.

For Maven users, please note that this release is not published at the central maven repository. Instead it is published on Amazon's S3 service, like all Spring milestones. To use it, add the following repository to your POM:

<repository>
   <id>spring-milestone</id>
   <name>Spring Milestone Repository</name>
   <url>http://s3.amazonaws.com/maven.springframework.org/milestone</url>
</repository>

For more information, see http://static.springframework.org/spring-ws/sites/1.5/

Cheers,

Arjen

[5er_levart]

The latest (as of now) 1.5.0-rc1-SNAPSHOT version of spring-ws on the http://s3.amazonaws.com/maven.spring...k.org/snapshot Maven repo does not contain the

org.springframework.ws.wsdl.wsdl11.DefaultWsdl11Definition

class neither the

org.springframework.ws.wsdl.wsdl11.ProviderBasedWsdl4jDefinition

class although the API docs for 1.5.0-rc1 at the http://static.springframework.org/sp...ocs/index.html do contain them.
I belive the Maven distribution is not complete. Or am I missing something?

Regards, Peter

[5er_levart]

The sourceforge distribution is fine though, so I'm just going to manualy install those jars to my local maven2 repository for now...

[alex.arica]

Is there any options to specify in the context file in order to a use the new XSD-to-WSDL generator feature that inlines included and import XSDs?

[Arjen Poutsma]

The latest (as of now) 1.5.0-rc1-SNAPSHOT version of spring-ws on the http://s3.amazonaws.com/maven.spring...k.org/snapshot Maven repo does not contain the

org.springframework.ws.wsdl.wsdl11.DefaultWsdl11Definition

class neither the

org.springframework.ws.wsdl.wsdl11.ProviderBasedWsdl4jDefinition

class although the API docs for 1.5.0-rc1 at the http://static.springframework.org/sp...ocs/index.html do contain them.
I belive the Maven distribution is not complete. Or am I missing something?

Well, I moved the code over from the sandbox and released before a snapshot was built. So the endresult was that the RC1 release contained code which wasn't in the snapshot.

[Joshua White]

Alex,

I hope this helps:

    <bean id="someService" class="org.springframework.ws.wsdl.wsdl11.DefaultWsdl11Definition">        
        <!--
        This is how you used to do it....            
        <property name="schema">
            <bean class="org.springframework.xml.xsd.SimpleXsdSchema">   
          <property name="xsd" value="someSchemaFileWithImportsAndIncludes.xsd"/>
            </bean>
        </property>        
        --> 
        <!--This is how you do it to include all referenced schemas inline-->
        <property name="schemaCollection">
            <bean class="org.springframework.xml.xsd.commons.CommonsXsdSchemaCollection">                
          <property name="xsds" value="someSchemaFileWithImportsAndIncludes.xsd"/>
                <property name="inline" value="true"/>
            </bean>
        </property>                        
        <property name="portTypeName" value="myPortTypeName"/>
        <property name="locationUri" value="http://localhost:8080/services/myServiceName"/>
    </bean>

Regards,

Joshua

[alex.arica]

I modified the context file as you suggested. Spring-WS has generated a WSDL that inlines the imported XSDs. It works great!

Thank you for your help Joshua.

[Arjen Poutsma]

I modified the context file as you suggested. Spring-WS has generated a WSDL that inlines the imported XSDs. It works great!

I'm happy to hear that!

Obviously, I will add/change the documentation for this, but it's good to hear that people are using it already.

[ray_harrison]

I'm happy to hear that!

Obviously, I will add/change the documentation for this, but it's good to hear that people are using it already.

Hi Arjen,

Great work! It isn't clear how (or if) this can be applied to pre-defined WSDLs. Can you clarify?

Thanks
Ray Harrison

[Arjen Poutsma]

Hi Arjen,

Great work! It isn't clear how (or if) this can be applied to pre-defined WSDLs. Can you clarify?

Not sure what you mean by pre-defined WSDLs, and how this should work in combination with them. but you can't use this approach as a substitute for the SimpleWsdl11Definition. This is more or less the successor to the Wsdl11DefinitionBuilder.