• 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 ...
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • paul wheaton
  • Devaka Cooray
  • Jeanne Boyarsky
  • Tim Cooke
  • Liutauras Vilda
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Piet Souris
  • salvin francis
  • Mikalai Zaikin
  • Himai Minh

Do JNDI Lookups Remove Portability?

Ranch Hand
Posts: 205
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I deployed my first EJB the other day, and noticed there wasn't a JNDI entry in the ejb-jar.xml file for the EJB I deployed. Yet my java client can look up this bean through JNDI. Then I noticed that the JNDI name was specified in the file sun-j2ee-ri.xml...which obviously isn't part of the specification.

So is every JNDI name registered differently depending on the vendor?

If I write an application with JSP's/Servlets and EJBs and throw them in an EAR, does this mean if I change app servers I am going to have to re-register all the JNDI names with the new app server?

What does <ejb-ref> have to do with all of this?

Normally trees don't drive trucks. Does this tiny ad have a license?
Thread Boost feature
    Bookmark Topic Watch Topic
  • New Topic