• 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

Problem with JNDI lookup in WAS 4.02

 
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have encountered a strnage problem, please tell me what I have dome wrong:
in my Admin Console, I set up the following
Connectin pooling, jndi: jdbc/myDataSource
ejb, jndi: ejb/myEjb
and I tried the following:
when I install a WAR module alone, and WAR module did not use any EJB, and I did not specify the "Resource Reference", then to look up for the data-source, jdbc/myDataSource, it works
when I package my WAR module together with EJB module to an EAR file, what the folowing step:
if I specify that the WAR use the DataSource, by setting the "Reference Resource", then I can get the DataSource with the jndi look up string:
"jdbc/myDataSource" in my code, it worked fine
but if I also specified that my WAW module also use the EBJ, by setting the "EJB reference" in the WAR module, then I cannot obtain the Datasource anymore?
I dont know what shou;d do then?
thank you vey much
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic