Mar 22nd, 2011, 02:41 PM
First off, I would like to say how much I and our organization enjoy spring-ws. We have most of our services in house build on this framework. The problem that we are having is how the weblogic container handles spring-ws services. We are trying to use SAML authentication from our Oracle Service Bus (weblogic) down to webservice container (weblogic) . We set up the relationship from the bus to the webservice container and the bus generates the token but our webservice container cannot use this token because the relationship is based up the service being an endpoint that the webservice container recognizes. If I write a simple JAX-WS service, I can get weblogic webservice container to see the endpoint but not with spring-ws. I had thought spring-ws was based upon JAX-WS?? Is it not? Either way, do you know how I can get the weblogic webservice container to recognize the spring-ws endpoints? We would like to continue to use spring-ws but cannot unless this issue is resolved.
Aug 24th, 2011, 10:40 PM
We're having the same issue. Weblogic 10.3.5 does not want to recognize spring-ws annotated services... I'm not sure if its related to the MessageDispatcherServlet as the servlet class, rather than the annotated endpoint (following what jax-ws does).
Did you ever find a solution that would allow weblogic to see the services *as* web services?
Aug 25th, 2011, 03:14 PM
No, we never found a solution. Our organization was using spring-ws, but since we didn't receive and answer from the community, we have started down the path of jax-ws. Our organization bought the Oracle SOA suite and require services to identified by the weblogic container for SAML federation.
Aug 25th, 2011, 03:34 PM
We were looking at this a while back and also never found an answer. In the end, we moved over to JAX-WS. We are getting ready to start on a new project and would like to use spring-ws but require container services (or an ugly workaround) so am looking into spring again. I will be watching this thread to see if it gets any traction.
Aug 28th, 2011, 06:04 AM
To answer the original question, Spring WS is not based on JAX-WS, which IMHO allows for much more flexibility and is probably one of the reasons you like it. If you need JAX-WS compliance and you need your endpoints dependency-injected / AOP-intercepted, you may consider Spring Remoting support for JAX-WS. Otherwise, your use case seems to be specific to WebLogic, so maybe someone on WebLogic forums could give you more ideas.