• 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Bear Bibeault
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Jj Roberts
  • Carey Brown
Bartenders:
  • salvin francis
  • Frits Walraven
  • Piet Souris

ejb-ref

 
Ranch Hand
Posts: 187
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The lookupNameForCode specified by ejb-jar/enterprise-beans/<entity|session|message-driven>/ejb-ref/ejb-ref-name will have to be mapped to
==> the actual JNDI name in a vendorspecific fashion.
Or
==> is it actual bean using <ejb-link> tag.
 
Ranch Hand
Posts: 1258
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Actually, it can refer to another EJB name, even relative to another JAR in your EAR. If you need to link it to an EJB in a different EAR, or who-knows-where, then you would have to do it in a vendor-specific way (in JBoss, for example, you would leave the ejb-link blank, and include the JNDI lookup name in their JBoss-equivalent ejb-jar.xml file.
reply
    Bookmark Topic Watch Topic
  • New Topic