File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Web Services Certification (SCDJWS/OCEJWSD) and the fly likes WSDL on EJB endpoints Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Certification » Web Services Certification (SCDJWS/OCEJWSD)
Bookmark "WSDL on EJB endpoints" Watch "WSDL on EJB endpoints" New topic

WSDL on EJB endpoints

Karthik Jayaprakasham

Joined: Jan 15, 2004
Posts: 21
Had a small design question.

EJBs are never accessed by non-J2EE clients right? For example, if I tried to lookup a bean that is outside the scope of a container, for example from an another JVM, I will not reach it.

So isnt exposing it as a webservice, bypass this whole concept. I would simply be able to find a WSDL location and call methods on the EJB. (ofcourse I could put security on to the methods and let only authenticated clients access it). But exposing a EJB to a non-J2EE client is a change in design. Not that I have anything against it, just trying to clarify it.
Xie Ruchang
Ranch Hand

Joined: Dec 25, 2003
Posts: 160

EJBs are never accessed by non-J2EE clients right?

Wrong! J2SE applications could access EJBs directly. In EJB, there are two kind of interfaces REMOTE and LOCAL. REMOTE interfaces are for those clients calling the beans from other VM. If the clients and the beans are in the same VM, LOCAL interface is used for performance.

I agree. Here's the link:
subject: WSDL on EJB endpoints
jQuery in Action, 3rd edition