aspose file tools*
The moose likes Web Services Certification (SCDJWS/OCEJWSD) and the fly likes doubts regarding jax-ws and web service broker pattern Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Certification » Web Services Certification (SCDJWS/OCEJWSD)
Bookmark "doubts regarding jax-ws and web service broker pattern" Watch "doubts regarding jax-ws and web service broker pattern" New topic
Author

doubts regarding jax-ws and web service broker pattern

Deriko Prata
Greenhorn

Joined: Dec 16, 2010
Posts: 21
Hello here,
As I progress studying for OCPJWSD I think I'm having some misunderstandings, here are my doubts:

1)I understand that both EJB and POJO SIBs are wrapped into servlets when deployed into a JEE app server, does the same happens when I publish the services only using JSE 6 Endpoint class in a standalone application ? If so, does that means that JSE 6 comes with a light weigth http server?

2)Are these servlet wrappers by any chance the same as the servlet endpoint processor of the webservice broker class diagram?

3)I had two interpretations on the web service broker pattern:

I) JAX-WS uses web service broker pattern internally, that way , the servlet endpoint processor would be the servlet that wrappes the SIB, and the SIB would be the web service broker being implemented by a POJO or and EJB.

II) Web service broker is a pattern to use when you have legacy services that needed to be exposed as web services. That said, the endpoint processor would work as a front controller, receving first the request and routing it to these legacy services by a facade( the web service broker).

Are any of these assumptions correct?

Please someone enlighten me.

Thanks.

Dan Drillich
Ranch Hand

Joined: Jul 09, 2001
Posts: 1164
Deriko Prata wrote:
II) Web service broker is a pattern to use when you have legacy services that needed to be exposed as web services. That said, the endpoint processor would work as a front controller, receving first the request and routing it to these legacy services by a facade( the web service broker).




We had recently a thread about this at Is Webservice Broker pattern analogous to SessionFacade paired with Business Delegate?

Regards,
Dan


William Butler Yeats: All life is a preparation for something that probably will never happen. Unless you make it happen.
Deriko Prata
Greenhorn

Joined: Dec 16, 2010
Posts: 21
Hi, thanks for the reply. What about 1 and 2 ? I want to know if the mechanics behind the scenes are the same in a web service(Using pojo SIB) deployed in a app server and in standalone app using JSE 6. Also what are the disadvantages using only JSE 6 besides the obvious loose of scalabiblity and JEE services?
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: doubts regarding jax-ws and web service broker pattern
 
Similar Threads
communicate non java client with java server side components ?
Clarification on servlet based web service end point.
service interface in both web.xml and webservices.xml?
Apache Axis JSE
JEE 1.5 Servlet Endpoint Webservice?