IntelliJ Java IDE
The moose likes JBoss and the fly likes J2EE Clients - Why deploy them with EAR? Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login
JavaRanch » Java Forums » Products » JBoss
Reply Bookmark "J2EE Clients - Why deploy them with EAR?" Watch "J2EE Clients - Why deploy them with EAR?" New topic
Author

J2EE Clients - Why deploy them with EAR?

Ariel Valentin
Ranch Hand

Joined: Jan 30, 2004
Posts: 44
I am a JBoss/Distributed Java newbie and there is something I do not quite understand about j2ee clients. In the cmp example provided, one packages the Client application (roster-app-client.jar) into the EAR file in order to be able to run it externally.
I tried it a second time omitting the roster-app-client from the EAR but when attempting to run the client, a javax.naming.NameNotFoundException is thrown with this error "RosterClient not bound"
Why do we have to bind the client to the server? I understand that we need to use the JBoss JNDI implementation to look up the SessionBeans but why do we need an entry for the Client? Isn't the client independant of the remote application it is invoking (In this case a SessionBean)?


A. Valentin
Ariel Valentin
Ranch Hand

Joined: Jan 30, 2004
Posts: 44
Never mind. I figured out I was the client side deployment descriptor and made all ejb-ref entries in there.
 
IntelliJ Java IDE
 
subject: J2EE Clients - Why deploy them with EAR?
 
Threads others viewed
J2SE client or J2EE client ?
Using Java client to call EJB in JBOSS
J2ee Application client module
The ceoncept of application-client
About using JBoss
MyEclipse, The Clear Choice