Danny, Robert has tried with the Spring 2.0 jars and it worked for him. So please try upgrading the spring jars If you do have any problems, please report on the list and we will be happy to fix them. We only use basic spring functionality to do the wiring so it should work w/o a problem.
The idea behind the axis2 spring integration is to expose Spring beans as Web Services (or to let spring manage your web services if u look at it from another angle). This way you get the best of both worlds. Axis2 has several advantages over Spring framework-WS. Taking a cursory glance on Spring WS u can see that they only have support for WS-Security. But Axis2 supports (by far the leading WS stack) several key specs like WS-Addressing, WS-RelaibleMessaging, WS-SecureConversation, WS-Trust ...etc We also have AXIOM a high performance Object model built on top of the StAX parser API. Multiple transport support and attachment support with MTOM (SwA if u want) ..etc We also have various other Bells and Wistles that are very appealing to a Web Services developers Hope this helps, Rajith On 12/15/06, Danny Lin <[EMAIL PROTECTED]> wrote:
We are new to Web Services and we want to follow certain design pattern or framework. framework. It was decided to use Axis2 and I wonder if it worth the trouble to look into Spring framework and Spring framework-WS. I also noticed that Axis2 has Spring extension (axis2-spring-1.1.jar). The Axis2 stand-alone installation uses Spring 1.2.8. Our organization has standardized on Spring 2.0. So, my question is that will it be ok to replace the Spring jars with version 2.0/2.0.1? Thanks for any comments. Danny
