File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes EJB and other Java EE Technologies and the fly likes JNDI lookup problem, this is a nightmare.... Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "JNDI lookup problem, this is a nightmare...." Watch "JNDI lookup problem, this is a nightmare...." New topic
Author

JNDI lookup problem, this is a nightmare....

Cristiano Fontes
Greenhorn

Joined: Oct 20, 2008
Posts: 5
Hello i am new to JNDI so i am really dadly confused about it.

I am using WebSphere 6.0(local running in Rational Software Architect), to test a Oracle 10g DB(Remote) connection. to do that I made a servlet that when i start it try to connect and send an insert and a select to the DB

my problem.

I configured the DS in WebSphere in

JDBC providers > Oracle JDBC Driver > Data sources

This is my DS
Name JNDI name Description
TEST_DS jdbc/TEST_DS New JDBC Datasource

it's working because I tested with the built-in WebSphere AS tester.

but I can't get my Servlet to Lookup this DS, I have been trying for more than 10 hours, i would really like some help, I've read every Tutorial online but nothing can help me.

Deployment descriptor.


this is the last attemp to make it work.
Code of Servlet


my error



Is there anything else to config to make this thing work ?
I am going mad here, because there is no way to make it work...

[ November 17, 2008: Message edited by: Cristiano Fontes ]

[ November 17, 2008: Message edited by: Cristiano Fontes ]

[ November 17, 2008: Message edited by: Cristiano Fontes ]
[ November 17, 2008: Message edited by: Cristiano Fontes ]
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10100
    
164



I think you are missing a (WebSphere) specific deployment descriptor where you map the resource TEST_DS with an object in the JNDI tree using a jndi-name.

Try looking it up directly from the global JNDI instead of the web-application's ENC. Try this:



[My Blog] [JavaRanch Journal]
Anand Bansal
Greenhorn

Joined: Oct 15, 2012
Posts: 10
I could solve this issue by just writing "TESTDS" as my data source and the runtime data source claases were appending the java:conv/env by itself.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: JNDI lookup problem, this is a nightmare....