• 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

J2EE Clients - Why deploy them with EAR?

 
Ranch Hand
Posts: 44
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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)?
 
Ariel Valentin
Ranch Hand
Posts: 44
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Never mind. I figured out I was the client side deployment descriptor and made all ejb-ref entries in there.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic