• 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

Can we deploy Ejb3.0 as a EAR file.

 
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am deploying Ejb3.0 Stateless session bean as a EAR file into jboss4.2.2 server.Deployment is sucessfull but i cant able to access it.
//Lookup code
Hello hello = (Hello) ctx.lookup("HelloBean/remote");

Exception comes as "HelloBean not bound"

When i deploy bean as Ejb jar file its working fine, I can lookup bean, No exception and get correct output.

Please tell me If i deploy bean as a EAR file how to lookup.
 
Sheriff
Posts: 10445
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
When you deploy the EJB through an EAR, the default JNDI name for the bean is of the format "EARName/BeanClassName/remote" and "EARName/BeanClassName/local". You can even use the JNDIView from the jmx-console to see the jndi-name to which the bean is bound.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic