Comments on: What's New in Spring Web Services 1.5? http://blog.springsource.com/main/2008/03/28/whats-new-in-spring-web-services-15/ The voice of SpringSource Thu, 24 Jul 2008 02:55:13 +0000 http://wordpress.org/?v=2.0.11 by: Web Services Company http://blog.springsource.com/main/2008/03/28/whats-new-in-spring-web-services-15/#comment-104187 Thu, 24 Apr 2008 12:04:56 +0000 http://blog.springsource.com/main/2008/03/28/whats-new-in-spring-web-services-15/#comment-104187 Hey Isn't Hot news for the people. Now Spring Web Services has released Its 1.5.0 after being worked for six months. congrats to Arjen for this success.... Hey Isn't Hot news for the people. Now Spring Web Services has released Its 1.5.0 after being worked for six months. congrats to Arjen for this success….

]]> by: Arjen Poutsma http://blog.springsource.com/main/2008/03/28/whats-new-in-spring-web-services-15/#comment-103586 Fri, 18 Apr 2008 10:04:15 +0000 http://blog.springsource.com/main/2008/03/28/whats-new-in-spring-web-services-15/#comment-103586 @Dave: It might be best to move this discussion to the <a href="http://forum.springframework.org/forumdisplay.php?f=39" rel="nofollow">community forum</a>, because there are more people who can answer it. @Mario: Thanks! @Gavin: Wow, that's a lot of suggestions! :) Some of these are more related to <a href="http://springframework.org/spring-integration" rel="nofollow">Spring Integration</a> than Spring-WS. Spring Integration will have Spring-WS adapters soon, so they will nicely play together. As for implementing more specs: I am always a bit reluctant with them, because adding more WS-* specs doesn't necessarily increase interoperability. Finally, I am not entire clear why the WSDLs generated by DefaultWsdl11Definition are incomplete. I go through great lengths to tests these WSDLS for interoperability with all the major platforms (Axis, .NET, WIndows Communication Foundation, etc.). If it is not sufficient, than note that the XSD to WSDL generation is much more pluggable than it used to be: it's now quite easy to change a specific part of the WSDL by using the <a href="http://static.springframework.org/spring-ws/site/apidocs/org/springframework/ws/wsdl/wsdl11/provider/package-summary.html" rel="nofollow">*Provider</a> mechanism. The DefaultWsdl11Definition is just a convenient wrapper around these providers, for the common case. @Dave:

It might be best to move this discussion to the community forum, because there are more people who can answer it.

@Mario:

Thanks!

@Gavin:

Wow, that's a lot of suggestions! :) Some of these are more related to Spring Integration than Spring-WS. Spring Integration will have Spring-WS adapters soon, so they will nicely play together. As for implementing more specs: I am always a bit reluctant with them, because adding more WS-* specs doesn't necessarily increase interoperability.

Finally, I am not entire clear why the WSDLs generated by DefaultWsdl11Definition are incomplete. I go through great lengths to tests these WSDLS for interoperability with all the major platforms (Axis, .NET, WIndows Communication Foundation, etc.). If it is not sufficient, than note that the XSD to WSDL generation is much more pluggable than it used to be: it's now quite easy to change a specific part of the WSDL by using the *Provider mechanism. The DefaultWsdl11Definition is just a convenient wrapper around these providers, for the common case.

]]> by: Gavin Bayfield http://blog.springsource.com/main/2008/03/28/whats-new-in-spring-web-services-15/#comment-103581 Fri, 18 Apr 2008 09:33:41 +0000 http://blog.springsource.com/main/2008/03/28/whats-new-in-spring-web-services-15/#comment-103581 Hello ! One foundation stone of the propagation of web services has been the ability to take a WSDL file for any web service and generate the appropriate web service client painlessly (a classic case of web service standards facilitating, not constraining) the machinations of enterprise application integration. There are an army of web service client tools out there now of course, we're using SOAPUI just now to test document literal web services. In this context, the reason for this note is a plea to consider extending WSDL support to make spring-ws more useful in current (WS-I compliant) web service environments. Essentially I am a little confused at the Dynamic WSDL implementation (DefaultWsdl11Definition replacing DynamicWsdl11Definition) since the WSDL is incomplete in the sense it can not be used in web client generation tools here since there is no Message Exchange Pattern abstraction to support the message definition. I think this is by design but this ommission fundamentally constrains our usage of Spring-ws since I can not leverage any of the existing web service client mechanisms (in place from the WS-I/WSDL conventions) for standing applications, without having to change web service client implementations to accommodate the simple message (xsd schema) driven definition of the facade. So 'lightweight' becomes 'limited-use' in standing environments where Web Service industry standards in competing tools deployed today do facilitate simple deployment transparently incoporating the power of Web Service Standards based compliance. In this case a workaround could subclass the Spring type and introduce declarative support to add 'operations' (MEP) support to dynamically generate a meaningful WSDL (WS-I compliant) WSDL. Secondly, i'll completely leap out on a limb here and suggest briefly a list of ESB characteristics that a 'lightweight' extensible Message Bus would likely accommodate, (a screaming need for spring imho since the fundamental demand for facilitating mechanisms of enterprise business integration has not gone away :} 1 Viable definition of an SOA Architecture & Infrastructure for Web Services 2 Definition of ESB Platform technologies and standards (adopted) 3 Web Service Messaging (WS-Interoperability compliant SOAP/WSDL/HTTP/XML) 4 Web Service Registry & Repository (Web Service Metadata Lookup, Classification and Administration) 5 Reliable, consistent and uniform data exchange mechanisms and protocols 6 Support for asynchronous Message Exchange Patterns (MEP) facilitating Reliable Messaging Web Service standards (SOAP over JMS etc) 7 Dynamic and transparent content-based & rules-based message routing 8 Web Service location transparency (rules based) 9 Web Service Composition - transparent Business Service to implementation service(s) coordination and dynamic management 10 Protocol mediation and translation 11 Message data transformation capabilities (e.g. consistent with Common Data Model, Double Transformation Model etc) 12 Security connection and message level technologies, Access & SSO capabilities, Identity Management (SSL/TLS & XML Message Security/Ws-Security/SSO/SAML etc) 13 Web Service BAM /Monitoring /Metering /Configuration /Administration... 14 Event Model Support 15 Pluggable Validation and metadata abstraction technologies 16 Strategy for Business Process Modelling & Process Orchestration ... Thanks for yout time and keep up the great work !!! Regards Gavin Bayfield Spring Certified Professional Hello ! One foundation stone of the propagation of web services has been the ability to take a WSDL file for any web service and generate the appropriate web service client painlessly (a classic case of web service standards facilitating, not constraining) the machinations of enterprise application integration. There are an army of web service client tools out there now of course, we're using SOAPUI just now to test document literal web services. In this context, the reason for this note is a plea to consider extending WSDL support to make spring-ws more useful in current (WS-I compliant) web service environments. Essentially I am a little confused at the Dynamic WSDL implementation (DefaultWsdl11Definition replacing DynamicWsdl11Definition) since the WSDL is incomplete in the sense it can not be used in web client generation tools here since there is no Message Exchange Pattern abstraction to support the message definition. I think this is by design but this ommission fundamentally constrains our usage of Spring-ws since I can not leverage any of the existing web service client mechanisms (in place from the WS-I/WSDL conventions) for standing applications, without having to change web service client implementations to accommodate the simple message (xsd schema) driven definition of the facade. So 'lightweight' becomes 'limited-use' in standing environments where Web Service industry standards in competing tools deployed today do facilitate simple deployment transparently incoporating the power of Web Service Standards based compliance.
In this case a workaround could subclass the Spring type and introduce declarative support to add 'operations' (MEP) support to dynamically generate a meaningful WSDL (WS-I compliant) WSDL.

Secondly, i'll completely leap out on a limb here and suggest briefly a list of ESB characteristics that a 'lightweight' extensible Message Bus would likely accommodate, (a screaming need for spring imho since the fundamental demand for facilitating mechanisms of enterprise business integration has not gone away :}

1 Viable definition of an SOA Architecture & Infrastructure for Web Services
2 Definition of ESB Platform technologies and standards (adopted)
3 Web Service Messaging (WS-Interoperability compliant SOAP/WSDL/HTTP/XML)
4 Web Service Registry & Repository (Web Service Metadata Lookup, Classification and Administration)
5 Reliable, consistent and uniform data exchange mechanisms and protocols
6 Support for asynchronous Message Exchange Patterns (MEP) facilitating Reliable Messaging Web Service standards (SOAP over JMS etc)
7 Dynamic and transparent content-based & rules-based message routing
8 Web Service location transparency (rules based)
9 Web Service Composition - transparent Business Service to implementation service(s) coordination and dynamic management
10 Protocol mediation and translation
11 Message data transformation capabilities (e.g. consistent with Common Data Model, Double Transformation Model etc)
12 Security connection and message level technologies, Access & SSO capabilities, Identity Management (SSL/TLS & XML Message Security/Ws-Security/SSO/SAML etc)
13 Web Service BAM /Monitoring /Metering /Configuration /Administration…
14 Event Model Support
15 Pluggable Validation and metadata abstraction technologies
16 Strategy for Business Process Modelling & Process Orchestration
…

Thanks for yout time and keep up the great work !!!

Regards Gavin Bayfield
Spring Certified Professional

]]> by: Mario Gleichmann http://blog.springsource.com/main/2008/03/28/whats-new-in-spring-web-services-15/#comment-103577 Fri, 18 Apr 2008 08:33:31 +0000 http://blog.springsource.com/main/2008/03/28/whats-new-in-spring-web-services-15/#comment-103577 Hello Arjen, congratulations to the new release - we suppose to apply Spring-WS on a large financial transaction platform due to the new support of WS Security. So if you may are interested in user feedback (especially concerning WS Security) - would be no problem. Side Note: the documentation is very comprehensible. Well done! Greetings Mario Hello Arjen,

congratulations to the new release - we suppose to apply Spring-WS on a large financial transaction platform due to the new support of WS Security. So if you may are interested in user feedback (especially concerning WS Security) - would be no problem.

Side Note: the documentation is very comprehensible. Well done!

Greetings

Mario

]]> by: Dave Brosius http://blog.springsource.com/main/2008/03/28/whats-new-in-spring-web-services-15/#comment-103425 Wed, 16 Apr 2008 20:45:00 +0000 http://blog.springsource.com/main/2008/03/28/whats-new-in-spring-web-services-15/#comment-103425 Ok, thanks. So i unzipped all the spring-ws jars, and modified the manifest to say 2.0-2.6. I also created osgi bundles for activation, stax and wsdl4j. Now all the bundles start up fine, and jetty starts as well. I tried to take the echo sample and use that. But when i hit any page, say for instance http://mbfg:9999/spring-ws/echo.wsdl all i get on the browser is HTTP ERROR: 404 ProxyServlet: /spring-ws/echo.wsdl RequestURI=/spring-ws/echo.wsdl Powered by Jetty:// ---- How does one even begin to debug what is wrong? Ok, thanks. So i unzipped all the spring-ws jars, and modified the manifest to say 2.0-2.6. I also created osgi bundles for activation, stax and wsdl4j. Now all the bundles start up fine, and jetty starts as well. I tried to take the echo sample and use that. But when i hit any page, say for instance http://mbfg:9999/spring-ws/echo.wsdl

all i get on the browser is

HTTP ERROR: 404
ProxyServlet: /spring-ws/echo.wsdl
RequestURI=/spring-ws/echo.wsdl

Powered by Jetty://

—-

How does one even begin to debug what is wrong?

]]> by: Arjen Poutsma http://blog.springsource.com/main/2008/03/28/whats-new-in-spring-web-services-15/#comment-103287 Tue, 15 Apr 2008 20:08:55 +0000 http://blog.springsource.com/main/2008/03/28/whats-new-in-spring-web-services-15/#comment-103287 [quote post="304"]I'm trying to use spring-ws in an osgi environment. It would be great if a simple example could be given. But as i struggle to do it myself, spring-ws bundle org.springframework.bundle.ws.support expects framework bundles from 2.0.0 to 2.5.0, but i have 2.5.3 and so the dependencies aren't found.[/quote] Yeah, that's a <a href="http://jira.springframework.org/browse/SWS-325" rel="nofollow">known issue</a>. Will be fixed in 1.5.1. [quote post="304"]I'm trying to use spring-ws in an osgi environment. It would be great if a simple example could be given. But as i struggle to do it myself, spring-ws bundle org.springframework.bundle.ws.support expects framework bundles from 2.0.0 to 2.5.0, but i have 2.5.3 and so the dependencies aren't found.[/quote]

Yeah, that's a known issue. Will be fixed in 1.5.1.

]]> by: Dave Brosius http://blog.springsource.com/main/2008/03/28/whats-new-in-spring-web-services-15/#comment-103281 Tue, 15 Apr 2008 17:54:20 +0000 http://blog.springsource.com/main/2008/03/28/whats-new-in-spring-web-services-15/#comment-103281 I'm trying to use spring-ws in an osgi environment. It would be great if a simple example could be given. But as i struggle to do it myself, spring-ws bundle org.springframework.bundle.ws.support expects framework bundles from 2.0.0 to 2.5.0, but i have 2.5.3 and so the dependencies aren't found. I'm trying to use spring-ws in an osgi environment. It would be great if a simple example could be given. But as i struggle to do it myself, spring-ws bundle org.springframework.bundle.ws.support expects framework bundles from 2.0.0 to 2.5.0, but i have 2.5.3 and so the dependencies aren't found.

]]> by: Spring Web Services 1.5å?‘布啦 : Digeek-dig geek news http://blog.springsource.com/main/2008/03/28/whats-new-in-spring-web-services-15/#comment-103136 Mon, 14 Apr 2008 14:19:15 +0000 http://blog.springsource.com/main/2008/03/28/whats-new-in-spring-web-services-15/#comment-103136 [...] Arjen Poutsma详细论述了一些新特性的工作方å¼?，å?‘我们展现了这些新å?˜åŒ–是如何实现的。有一些例å­?æ??述了新的传é€?器是如何实现的并给出了该版本中其他特性的一个概览。Aljern还对Spring-WS的设计决策与未æ?¥çš„功能给出了å??馈。 [...] […] Arjen Poutsma详细论述了一些新特性的工作方å¼?，å?‘我们展现了这些新å?˜åŒ–是如何实现的。有一些例å­?æ??述了新的传é€?器是如何实现的并给出了该版本中其他特性的一个概览。Aljern还对Spring-WS的设计决策与未æ?¥çš„功能给出了å??馈。 […]

]]> by: Daily del.icio.us for March 27th through April 3rd — Vinny Carpenter’s blog http://blog.springsource.com/main/2008/03/28/whats-new-in-spring-web-services-15/#comment-102369 Sat, 05 Apr 2008 01:15:40 +0000 http://blog.springsource.com/main/2008/03/28/whats-new-in-spring-web-services-15/#comment-102369 [...] SpringSource Team Blog » What’s New in Spring Web Services 1.5? - Spring Web Services 1.5.0 has been released and itincludes two new transports: JMS and email. Using these new transports requires no Java code changes - some configuration, and you're off! The JMS integrates with Spring's Message-Driven POJO model [...] […] SpringSource Team Blog » What's New in Spring Web Services 1.5? - Spring Web Services 1.5.0 has been released and itincludes two new transports: JMS and email. Using these new transports requires no Java code changes - some configuration, and you're off! The JMS integrates with Spring's Message-Driven POJO model […]

]]> by: Arjen Poutsma http://blog.springsource.com/main/2008/03/28/whats-new-in-spring-web-services-15/#comment-102249 Thu, 03 Apr 2008 06:54:26 +0000 http://blog.springsource.com/main/2008/03/28/whats-new-in-spring-web-services-15/#comment-102249 @Camilo, Our REST efforts will not be part of Spring -WS, but of Spring-MVC. See http://jira.springframework.org/browse/SPR-4419. @Camilo,

Our REST efforts will not be part of Spring -WS, but of Spring-MVC. See http://jira.springframework.org/browse/SPR-4419.

]]>