RE: javax.naming.NameNotFoundException: Name jdbc is not bound in this Context

2009-01-30 Thread Hamacher, Eric
DataSource pds = null; pds = (DataSource)context.lookup(name); name had to be java:/comp/jdbc/GFDataSource and then I moved on to my next problem. -Original Message- From: Pid [mailto:p...@pidster.com] Sent: Thursday, January 29, 2009 2:43 PM To: Tomcat Users

RE: javax.naming.NameNotFoundException: Name jdbc is not bound in this Context

2009-01-29 Thread Hamacher, Eric
Thanks Michael for the reply. No dice. Same error message with url. I forgot to mention that this is a fresh installation of Tomcat 6 so I haven't changed anything except for trying to insert this element. Eric -Original Message- From: Michael Ludwig [mailto:mil...@gmx.de] Sent:

Re: javax.naming.NameNotFoundException: Name jdbc is not bound in this Context

2009-01-29 Thread Stephen Souness
Which lib did you put your jars in? The web app's or Tomcat's? -- Stephen Souness Hamacher, Eric wrote: Hello: This has been a truly frustrating problem. Here is what I did: Tomcat 6.0.18 JDK 1.5 u 16 Eclipse w/ WTP 3.4.1 Ojdbc14dms.jar Dms.jar I placed my drivers in lib. In web.xml, I

RE: javax.naming.NameNotFoundException: Name jdbc is not bound in this Context

2009-01-29 Thread Hamacher, Eric
Tomcat's -Original Message- From: news [mailto:n...@ger.gmane.org] On Behalf Of Stephen Souness Sent: Thursday, January 29, 2009 9:02 AM To: users@tomcat.apache.org Subject: Re: javax.naming.NameNotFoundException: Name jdbc is not bound in this Context Which lib did you put your jars

RE: javax.naming.NameNotFoundException: Name jdbc is not bound in this Context

2009-01-29 Thread Hamacher, Eric
I solved the problem by putting java:/comp/env in the JNDI lookup in the code. That led me to an exception when I tried to use an ArrayDescriptor. So I tried to change my pooling form dbcp to oracle with: Resource name=jdbc/GFDataSource auth=Container

Re: javax.naming.NameNotFoundException: Name jdbc is not bound in this Context

2009-01-29 Thread Pid
Hamacher, Eric wrote: I solved the problem by putting java:/comp/env in the JNDI lookup in the code. So you're not putting: java:/comp/jdbc/GFDataSource? p That led me to an exception when I tried to use an ArrayDescriptor. So I tried to change my pooling form dbcp to oracle with:

javax.naming.NameNotFoundException: Name jdbc is not bound in this Context

2009-01-28 Thread Hamacher, Eric
Hello: This has been a truly frustrating problem. Here is what I did: Tomcat 6.0.18 JDK 1.5 u 16 Eclipse w/ WTP 3.4.1 Ojdbc14dms.jar Dms.jar I placed my drivers in lib. In web.xml, I put resource-ref res-ref-namejdbc/GFDataSource/res-ref-name

Re: javax.naming.NameNotFoundException: Name jdbc is not bound in this Context

2009-01-28 Thread Michael Ludwig
Hamacher, Eric schrieb am 28.01.2009 um 08:18:21 (-0600): Resource name=jdbc/GFDataSource auth=Container type=javax.sql.DataSource maxActive=30 maxIdle=2 maxWait=1000 username=username

javax.naming.NameNotFoundException: Name jdbc is not bound in this Context

2008-04-15 Thread Roger Keays
The following configuration gives me a javax.naming.NameNotFoundException: Context path=/ !-- connection pool for database -- Resource name=jdbc/data auth=Container type=javax.sql.DataSource driverClassName=org.postgresql.Driver url=jdbc:postgresql://localhost/test

Re: javax.naming.NameNotFoundException: Name jdbc is not bound in this Context

2008-04-15 Thread Mark Thomas
Roger Keays wrote: Is that the intended behaviour? Yes. If you want a realm to use a context defined datasource rather than a global one you need to set: localDataSource=true on the realm It is documented in the howto but not the realm docs. I'll fix that now.