• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

doubts regarding jax-ws and web service broker pattern

 
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.

 
Ranch Hand
Posts: 1183
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

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
 
Deriko Prata
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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?
 
When it is used for evil, then watch out! When it is used for good, then things are much nicer. Like this tiny ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic