Announcement Announcement Module
Collapse
No announcement yet.
Spring Web Services 2.0.0 RC2 released Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Spring Web Services 2.0.0 RC2 released

    Dear Spring community,

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

    This is the second release candidate in the 2.0 release cycle. The most important new feature in this release is the update of the Spring-WS XML namespace, which now contains <sws:annotation-driven/> and <sws:interceptors/>elements (similar to the Spring-MVC namespace), and <sws:static-wsdl/> and <sws:dynamic-wsdl/> for exporting your WSDLs. All of these features are described in the updated reference documentation, which you can find here:

    http://static.springsource.org/sprin...eference/html/

    We consider this release (RC2) complete. If no major new issues are found, we will release 2.0.0-RELEASE in the first half of January 2011.

    While we did make some changes, Spring-WS 2.0 should be a drop-in replacement for 1.5. The one exception is the 2.0 version of the XSD namespace, where we removed <sws:marshalling-endpoints/> and <sws:xpath-endpoints/> in favor of <sws:anotation-driven/>. To keep using the two former elements, please make sure to use the 1.5 version of the XSD, like so:

    Code:
    <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
           xmlns:sws="http://www.springframework.org/schema/web-services" xsi:schemaLocation="
           http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
           http://www.springframework.org/schema/web-services http://www.springframework.org/schema/web-services/web-services-1.5.xsd">
    To upgrade to <sws:annotation-driven/>, use the 2.0 version of the XSD:

    Code:
    <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
           xmlns:sws="http://www.springframework.org/schema/web-services" xsi:schemaLocation="
           http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
           http://www.springframework.org/schema/web-services http://www.springframework.org/schema/web-services/web-services-2.0.xsd">
    Please file a JIRA issue if you find any other regressions in the 2.0 RC2 release.

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

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

    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>
    Code:
    <dependency>
        <groupId>org.springframework.ws</groupId>
        <artifactId>spring-ws-core</artifactId>
        <version>2.0.0-RC2</version>
    </dependency>
    When 2.0 reaches GA, we will upload the jars to maven central as usual.

  • #2
    Good one. I can't wait to try it. Thanks a lot

    Edit:
    I've uploaded a tutorial utilizing Spring WS 2.0.0 RC2 build.

    Here's the link: http://krams915.blogspot.com/2010/12...t-200-rc2.html

    Enjoy
    Last edited by skram; Dec 26th, 2010, 03:54 AM.

    Comment


    • #3
      I can not wait for a 2.0 release. I've integrated spring ws 1.5.9 with spring 3.0.5.Release, but not with good feeling

      Comment


      • #4
        This is so exciting.

        Comment


        • #5
          Hi Arjen,

          I have read lot of forums on this topic but no one has clear solution on this?

          Does anybody knows a way to integrate header information during the WSDL generation?
          --------------------------------------------------------------------------
          Do you have any plans to add this near future?


          I need to add custom soap Header to include tenant info to make webservices multi- tenant model?

          Regards
          Harshi

          Comment


          • #6
            2.0 namespace still points to 1.5

            Hi,

            Was working on upgrading the project to 2.0. I keep getting annotation-driven is not declared?
            Looked at STS namespaces, it only shows 1.5.xsd.

            How do i overcome this, my maven project just has 2.0.0.RC2 jars and nothing in the path
            Code:
            <beans:beans xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
            	xmlns:p="http://www.springframework.org/schema/p"
            	xmlns:beans="http://www.springframework.org/schema/beans"
            	xmlns:ws="http://www.springframework.org/schema/web-services"
            	xsi:schemaLocation="http://www.springframework.org/schema/web-services http://www.springframework.org/schema/web-services/web-services-2.0.xsd
            		http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd">
            Thanks
            Srinivas

            Comment


            • #7
              I have updarded to RC2 and I am getting the following error????


              <sws:interceptors>
              <bean id="wsSecurityInterceptor" class="org.springframework.ws.soap.security.xwss.X wsSecurityInterceptor">
              <description>
              This interceptor validates incoming messages according to the policy defined in
              'securityPolicy.xml'.
              The policy defines that all incoming requests must have a UsernameToken with a password digest
              in it.
              The actual authentication is performed by the Spring callback handler.
              </description>
              <property name="secureResponse" value="false"/>
              <property name="policyConfiguration"
              value="/WEB-INF/spring/securityPolicy.xml"/>
              <property name="callbackHandlers">
              <list>
              <bean class="org.springframework.ws.soap.security.xwss.c allback.SpringDigestPasswordValidationCallbackHand ler">
              <property name="userDetailsService" ref="securityService"/>
              <property name="userCache" ref="userCache"/>
              </bean>
              <bean class="com.xifin.security.UserValidationCallbackHa ndler">
              <property name="userCache" ref="userCache"/>
              </bean>
              </list>
              </property>
              </bean>

              </sws:interceptors>




              2010-12-30 16:35:37,699 DEBUG SoapMessageDispatcher[handleHeaders() line 120] - Handling MustUnderstand header {http://docs.oasis-open.org/wss/2004/01/oasis-200
              401-wss-wssecurity-secext-1.0.xsd}Security
              2010-12-30 16:35:37,702 WARN SoapMessageDispatcher[createMustUnderstandFault() line 162] - Could not handle mustUnderstand headers: {http://docs.oasis-open.org
              /wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security. Returning fault
              2010-12-30 16:35:37,704 DEBUG sent[receive() line 181] - Sent response [SaajSoapMessage {http://schemas.xmlsoap.org/soap/envelope/}Fault] for request [SaajSoapM

              Comment


              • #8
                Originally posted by srinivas_vsk View Post
                Hi,

                Was working on upgrading the project to 2.0. I keep getting annotation-driven is not declared?
                Looked at STS namespaces, it only shows 1.5.xsd.

                How do i overcome this, my maven project just has 2.0.0.RC2 jars and nothing in the path
                Code:
                <beans:beans xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                	xmlns:p="http://www.springframework.org/schema/p"
                	xmlns:beans="http://www.springframework.org/schema/beans"
                	xmlns:ws="http://www.springframework.org/schema/web-services"
                	xsi:schemaLocation="http://www.springframework.org/schema/web-services http://www.springframework.org/schema/web-services/web-services-2.0.xsd
                		http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd">
                That's strange, what is the exact error you get? Is it a STS error or a Spring error?

                Comment


                • #9
                  Originally posted by harshi View Post
                  I have updarded to RC2 and I am getting the following error????


                  <sws:interceptors>
                  <bean id="wsSecurityInterceptor" class="org.springframework.ws.soap.security.xwss.X wsSecurityInterceptor">
                  <description>
                  This interceptor validates incoming messages according to the policy defined in
                  'securityPolicy.xml'.
                  The policy defines that all incoming requests must have a UsernameToken with a password digest
                  in it.
                  The actual authentication is performed by the Spring callback handler.
                  </description>
                  <property name="secureResponse" value="false"/>
                  <property name="policyConfiguration"
                  value="/WEB-INF/spring/securityPolicy.xml"/>
                  <property name="callbackHandlers">
                  <list>
                  <bean class="org.springframework.ws.soap.security.xwss.c allback.SpringDigestPasswordValidationCallbackHand ler">
                  <property name="userDetailsService" ref="securityService"/>
                  <property name="userCache" ref="userCache"/>
                  </bean>
                  <bean class="com.xifin.security.UserValidationCallbackHa ndler">
                  <property name="userCache" ref="userCache"/>
                  </bean>
                  </list>
                  </property>
                  </bean>

                  </sws:interceptors>




                  2010-12-30 16:35:37,699 DEBUG SoapMessageDispatcher[handleHeaders() line 120] - Handling MustUnderstand header {http://docs.oasis-open.org/wss/2004/01/oasis-200
                  401-wss-wssecurity-secext-1.0.xsd}Security
                  2010-12-30 16:35:37,702 WARN SoapMessageDispatcher[createMustUnderstandFault() line 162] - Could not handle mustUnderstand headers: {http://docs.oasis-open.org
                  /wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security. Returning fault
                  2010-12-30 16:35:37,704 DEBUG sent[receive() line 181] - Sent response [SaajSoapMessage {http://schemas.xmlsoap.org/soap/envelope/}Fault] for request [SaajSoapM
                  I've created SWS-675 to investigate this.

                  Comment


                  • #10
                    Hi, Arjen, I noticed that Spring WS 2.0 will have support for streaming web services (StreamingPayload and StreamingWebServiceMessage). Will this support the streaming of MTOM responses as well?

                    Comment


                    • #11
                      Originally posted by Arjen Poutsma View Post
                      That's strange, what is the exact error you get? Is it a STS error or a Spring error?
                      Two things , within STS , if you open the Webservice configuration file where i have defined this annotations e.t.c and go to Namespace tab and click on the webservice name space, it will only show you 1.5 xsd as the default schema.
                      There is no "error" as such in STS.
                      Second thing is the deployment fails with below errors. Thanks for your time
                      Code:
                      WARN : org.springframework.beans.factory.xml.XmlBeanDefinitionReader - Ignored XML validation warning
                      org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'http://www.springframework.org/schema/web-services/web-services-2.0.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
                      	at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
                      	at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.warning(ErrorHandlerWrapper.java:96)
                      	at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:380)
                      	at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:318)
                      
                      ERROR: org.springframework.web.servlet.DispatcherServlet - Context initialization failed
                      org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Failed to import bean definitions from relative location [spring-ws.xml]
                      Offending resource: ServletContext resource [/WEB-INF/spring/appServlet/servlet-context.xml]; nested exception is org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 26 in XML document from ServletContext resource [/WEB-INF/spring/appServlet/spring-ws.xml] is invalid; nested exception is org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'ws:interceptors'.
                      	at org.springframework.beans.factory.parsing.FailFastProblemReporter.error(FailFastProblemReporter.java:68)
                      	at org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:85)

                      Comment


                      • #12
                        Originally posted by srinivas_vsk View Post
                        Hi,

                        Was working on upgrading the project to 2.0. I keep getting annotation-driven is not declared?
                        Looked at STS namespaces, it only shows 1.5.xsd.

                        How do i overcome this, my maven project just has 2.0.0.RC2 jars and nothing in the path
                        Code:
                        <beans:beans xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                        	xmlns:p="http://www.springframework.org/schema/p"
                        	xmlns:beans="http://www.springframework.org/schema/beans"
                        	xmlns:ws="http://www.springframework.org/schema/web-services"
                        	xsi:schemaLocation="http://www.springframework.org/schema/web-services http://www.springframework.org/schema/web-services/web-services-2.0.xsd
                        		http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd">
                        Thanks
                        Srinivas
                        I encountered this problem the other day. It turns out it's a Maven problem with this 2.0.0 RC. I had to go to my local repository. Clean up whatever version of spring-ws I have. Then update the dependencies again.

                        I tested this on my home computer and at the office with different Eclipse configuration. So I would say it's either a problem with the Maven or there's a conflict with this release.

                        Comment


                        • #13
                          Tried that too, didnt help when im behind proxy. it downloads the jars fine but same problem.

                          something strange.

                          Comment


                          • #14
                            Originally posted by srinivas_vsk View Post
                            Tried that too, didnt help when im behind proxy. it downloads the jars fine but same problem.

                            something strange.
                            I believe the namespace resolution issue was related to https://jira.springframework.org/browse/SWS-677, which has now been fixed.

                            Can you try a recent snapshot (as of tonight) and see if it works?

                            Comment


                            • #15
                              Ok that fixed it. Thanks

                              Comment

                              Working...
                              X