jQuery in Action, 2nd edition*
The moose likes Web Services and the fly likes Exposing EJBs as WebServices... WHY  ? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "Exposing EJBs as WebServices... WHY  ?" Watch "Exposing EJBs as WebServices... WHY  ?" New topic
Author

Exposing EJBs as WebServices... WHY ?

Sudeep Agrawal
Ranch Hand

Joined: May 31, 2006
Posts: 34
Hi :
Could some one tell me what is the purpose of exposing EJBs as webservices ?
I have read much about RPC way of implementing Webservices in Weblogic.

What I donot understand is why epose EJBs as webservices, when you can make a JNDI lookup with the EJB and call it as usual?

I know interoperability is one good reason, but then are there any other PROs for this approach.
Ulf Dittmer
Marshal

Joined: Mar 22, 2005
Posts: 42282
    
  64
Using JNDI will only work for Java clients, as you point out. But is also uses some non-standard ports which you may not want to open up to the world. Web Services require only port 80 (and/or 443), which are usually open already.


Ping & DNS - my free Android networking tools app
 
wood burning stoves
 
subject: Exposing EJBs as WebServices... WHY ?