This discussion is archived
0 Replies Latest reply: Nov 5, 2012 8:31 AM by GuillaumeMenguy RSS

Stateless EJB Webservices vs Endpoint.publish() API for a production system

GuillaumeMenguy Newbie
Currently Being Moderated

I am currently designing an SOA JEE application using JAX-WS Webservices for the synchronous calls and JMS (MDB) for asynchronous access.
It is packaged in a EAR containing one EJB module (no WAR), so I decided first to publish the Webservices using the method via the Spring org.springframework.remoting.jaxws.SimpleJaxWsServiceExporter. It's working very well and I can inject easily spring beans into my JAX-WS webservice, .. but :
- I cannot see the published webservices in the Weblogic console
- I have no idea on how the webservices instances are handled (just one ? )
- Is it robust enough to be used in production in a critical financial application ?

On the other hand, I just have to add a @Statless annotation to turn my JAX-WS classes into real EJB-Webservice aware, but it probably adds overhead in the Weblogic server and it's a bit more complicated to inject Spring resources.

Any advice will help.


  • Correct Answers - 10 points
  • Helpful Answers - 5 points