Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: Spring Web Services 2.0.0 M2 released

  1. #1
    Join Date
    Jul 2005
    Location
    Rotterdam, the Netherlands
    Posts
    1,562

    Default Spring Web Services 2.0.0 M2 released

    Dear Spring community,

    I'm pleased to announce that Spring Web Services 2.0 Milestone 2 has been released!

    This is the second milestone release in the 2.0 release cycle. The most important new feature in this release is the ability to use arbitrary parameter types in @Endpoint methods (similar to @Controller methods in Spring-MVC). The big improvement to the 1.5 @Endpoint model is that you can mix and match parameters, and are not as limited in the return types. This means, for instance, that you can have the following @Endpoint method:


    Code:
    @PayloadRoot(localPart = "myRequest", namespace = "http://example.com")
    @ResponsePayload
    public MyJaxb2Response handleMyRequest(@RequestPayload org.w3c.dom.Element myElement, 
                                           SoapHeader requestHeader,
                                           MessageContext messageContext) {
    
        // do something interesting here
    }
    Currently supported parameters/return types include:
    • DOM Elements (W3C DOM by default; JDOM, dom4j, XOM are enabled automatically if present on the classpath)
    • Types supported by an OXM Marshaller (requires an explicitely configured marshaller)
    • JAXB2 types, if JAXB2 is found on the classpath (this means you no longer have to configure a Jaxb2Marshaller explicitly)
    • javax.xml.transform.Source and subtypes


    For the above parameters/return types, you will have to use @RequestPayload/@ResponsePayload, as shown in the sample above.

    Supported parameters (not return types) include:
    • MessageContext
    • StAX readers
    • SoapHeader, SoapBody, SoapEvelope (of the request message)
    • @XPathParam parameters. Note that you can now use the @Namespace and @Namespaces annotations to specify any namespaces used in your XPath expressions, and no longer need to set them up in XML application contexts. For instance:


    Code:
    @Namespaces(@Namespace(prefix = "tns", uri = "http://springframework.org/spring-ws"))
    public void myEndpointMethod(@XPathParam("/tns:root")String s) {
    }
    These namespace annotations can be present on the method, class, or package level (i.e. package-info.java).

    In addition to the above, Spring-WS 2.0 M2 includes:
    • Support for Spring Security 3.0
    • XMPP transport


    Please see the changelog for more details. If you have any further requests/issues, please use JIRA or reply to this post.

    Spring Web Services 2.0 is due in the third quarter of 2010.

    For more information, see http://static.springframework.org/spring-ws/site/
    Last edited by Arjen Poutsma; May 25th, 2010 at 05:04 AM.
    Arjen Poutsma

    Spring Web Services Dev Lead
    Please read the FAQ

  2. #2

    Default

    Please be aware that starting from this version, Spring-WS is no longer compatible with Spring Security 2.0. This is because Spring Security 3.0 is not backward compatible with 2.0.

    This milestone also brings two WS-Security improvements worth mentioning:
    • XWSS dependency has been updated to 3.0.
    • It is now possible to skip security validation if no WS-Security header is present.
    Tareq Abedrabbo

    My Twitter
    My Blog

  3. #3
    Join Date
    Jul 2005
    Location
    Rotterdam, the Netherlands
    Posts
    1,562

    Default

    Note that this milestone will not be uploaded to Maven Central, but only to our own milestone repo:

    Code:
    <repository>
      <id>spring-maven-milestone</id>
      <name>Springframework Maven Repository</name>
      <url>http://maven.springframework.org/milestone</url>
    </repository>
    When 2.0 reaches GA, we will upload the jars to maven central as usual.
    Arjen Poutsma

    Spring Web Services Dev Lead
    Please read the FAQ

  4. #4
    Join Date
    Oct 2005
    Posts
    26

    Post download pb

    I get a 403 error when I tried to download the release zip from this link
    http://s3.amazonaws.com/dist.springf...pendencies.zip

    tareq, it seems to be really secure ;-)
    be happy :-)

  5. #5
    Join Date
    Oct 2005
    Posts
    26

    Default download pb

    the link is working now
    be happy :-)

  6. #6
    Join Date
    Mar 2010
    Location
    Rotterdam
    Posts
    21

    Default

    I love the new paramater mix/matching! Now I can easily access the messagecontext for soap attachments without using an interceptor to inject the context in some bean

    Keep up the good work!

  7. #7
    Join Date
    Jul 2005
    Location
    Rotterdam, the Netherlands
    Posts
    1,562

    Default

    Quote Originally Posted by evandongen View Post
    I love the new paramater mix/matching! Now I can easily access the messagecontext for soap attachments without using an interceptor to inject the context in some bean

    Keep up the good work!
    Thanks! You should also be able to simply add a SoapMessage parameter to your endpoint method, to get a reference to the request message.

    Let me know if you find any issues.
    Arjen Poutsma

    Spring Web Services Dev Lead
    Please read the FAQ

  8. #8
    Join Date
    Nov 2007
    Posts
    122

    Default

    Hi Arjen,
    Do you have any specific date when spring 2.0 final release will be released?


    Regards
    Harshi

  9. #9
    Join Date
    Jul 2005
    Location
    Rotterdam, the Netherlands
    Posts
    1,562

    Default

    Quote Originally Posted by harshi View Post
    Hi Arjen,
    Do you have any specific date when spring 2.0 final release will be released?
    We will release one more milestone before we enter the RC phase. Depending on the amount of bugs you find, we might have more RCs. The GA will be released after that.

    So I (currently) expect SWS 2.0 to be released somewhere around September.
    Arjen Poutsma

    Spring Web Services Dev Lead
    Please read the FAQ

  10. #10
    Join Date
    Nov 2007
    Posts
    122

    Default

    Hi Arjen,

    I am using CommonsXsdSchemaCollection where my sxd contains xs:import to another xsd , with inline option = true DefaultWsdl11Definition is genertaing wsdl fine but its not removing xs:import which is causing errors from using SOAP UI.

    I have seen similar issue in spring ws 1.5.8 and its fixed on 1.5.9 as per docs
    but I never upgraded to 1.5.9.


    Regards
    Harshi

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •