Re: javax.naming.NameNotFoundException

2024-10-25 Thread Christopher Schultz
Mark F, On 10/23/24 18:13, Mark Foley wrote: On Wed, 23 Oct 2024 19:13:44 Mark Thomas wrote: On 23/10/2024 18:57, Mark Foley wrote: I'm running Tomcat 8.5.11. I have a hopefully small problem. Tomcat 8.5.x is EOL and no longer supported. 8.5.11 is also rather old with quite a long list of

Re: javax.naming.NameNotFoundException

2024-10-24 Thread Mark Thomas
On 23/10/2024 23:13, Mark Foley wrote: On Wed, 23 Oct 2024 19:13:44 Mark Thomas wrote: That won't work. What will work is renaming: $CATALINA_HOME/webapps/myapp to $CATALINA_HOME/webapps/myapp#subapp/ Mark Hmmm ... what I was attempting was splitting many webapps into multiple directo

Re: javax.naming.NameNotFoundException

2024-10-23 Thread Mark Foley
On Wed, 23 Oct 2024 19:13:44 Mark Thomas wrote: > > On 23/10/2024 18:57, Mark Foley wrote: > > I'm running Tomcat 8.5.11. I have a hopefully small problem. > > Tomcat 8.5.x is EOL and no longer supported. > > 8.5.11 is also rather old with quite a long list of know security issues. Yeah, I know.

Re: javax.naming.NameNotFoundException

2024-10-23 Thread Mark Thomas
On 23/10/2024 18:57, Mark Foley wrote: I'm running Tomcat 8.5.11. I have a hopefully small problem. Tomcat 8.5.x is EOL and no longer supported. 8.5.11 is also rather old with quite a long list of know security issues. I have a webapp directory: $CATALINA_HOME/webapps/myapp/. In that directo

RE: javax.naming.NameNotFoundException with JAXWS RI 2.5 and Tomcat 6.0

2009-05-14 Thread Caldarale, Charles R
> From: Bharath R [mailto:bharath.mail.l...@gmail.com] > Subject: Re: javax.naming.NameNotFoundException with JAXWS RI 2.5 and > Tomcat 6.0 > > Do you suggest I put the 2.4 servlet spec version in web.xml? That would probably work; you could also remove the annotations, since the

RE: javax.naming.NameNotFoundException with JAXWS RI 2.5 and Tomcat 6.0

2009-05-14 Thread Martin Gainty
opie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu four

Re: javax.naming.NameNotFoundException with JAXWS RI 2.5 and Tomcat 6.0

2009-05-14 Thread Bharath R
>>Tomcat 6.0 supports version 2.5 of the servlet spec, whereas Tocmat 5.5 uses 2.4; the 2.5 spec includes resource >>annotations, whereas 2.4 doesn't. You didn't bother to specify a spec version in your web.xml. Do you suggest I put the 2.4 servlet spec version in web.xml? >>so Tomcat chose the

RE: javax.naming.NameNotFoundException with JAXWS RI 2.5 and Tomcat 6.0

2009-03-17 Thread Caldarale, Charles R
> From: Bharath R [mailto:bharath.mail.l...@gmail.com] > Subject: javax.naming.NameNotFoundException with JAXWS RI 2.5 > and Tomcat 6.0 > This problem occurs only with Tomcat 6.0.18. It is ok with Tomcat > 5.5.27. Tomcat 6.0 supports version 2.5 of the servlet spec, whereas Tocmat 5.5 uses 2.

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

2009-01-30 Thread Hamacher, Eric
9 2:43 PM To: Tomcat Users List Subject: Re: javax.naming.NameNotFoundException: Name jdbc is not bound in this Context 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 > Tha

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

2009-01-29 Thread Pid
> url="jdbc:oracle:thin:@uxsvr3.enetrix.msn:2224:STG9"/> > > And now I'm back to "javax.naming.NameNotFoundException: Name jdbc is not > bound in this Context"! > > -Original Message- > From: Hamacher, Eric [mailto

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

2009-01-29 Thread Hamacher, Eric
d in this Context"! -Original Message- From: Hamacher, Eric [mailto:eric_hamac...@gallup.com] Sent: Thursday, January 29, 2009 9:04 AM To: Tomcat Users List Subject: RE: javax.naming.NameNotFoundException: Name jdbc is not bound in this Context Tomcat's -Original Mes

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 ja

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 p

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

2009-01-29 Thread Hamacher, Eric
..@gmx.de] Sent: Wednesday, January 28, 2009 6:17 PM To: Tomcat Users List Subject: Re: javax.naming.NameNotFoundException: Name jdbc is not bound in this Context Hamacher, Eric schrieb am 28.01.2009 um 08:18:21 (-0600): > >type="javax.sql.DataSource"

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): > >type="javax.sql.DataSource" > maxActive="30" > maxIdle="2" > maxWait="1000" > username="username" > password="password" >

Re: javax.naming.NameNotFoundException: Name jdbc is not bound inthisContext

2008-04-16 Thread Mark Thomas
Caldarale, Charles R wrote: I'd certainly like to see a Tomcat config tag with a couple of settings that would log or optionally reject badly formed elements. Patches are always welcome ;) Mark - To start a new topic, e-mai

RE: javax.naming.NameNotFoundException: Name jdbc is not bound inthisContext

2008-04-16 Thread Caldarale, Charles R
> From: Christopher Schultz [mailto:[EMAIL PROTECTED] > Subject: Re: javax.naming.NameNotFoundException: Name jdbc is > not bound inthisContext > > Can you think of a reason not to have Tomcat simply > refuse to load a that specifies its own > path (unless it is in s

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

2008-04-16 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chuck, Caldarale, Charles R wrote: | Also note that for any Tomcat released in the last few | years, the only time a path attribute is allowed at all is when the | element is in server.xml (where it should never be). Can you think of a reason not t

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

2008-04-15 Thread Caldarale, Charles R
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Roger Keays > Subject: javax.naming.NameNotFoundException: Name jdbc is not > bound in thisContext > > The following configuration gives me a > javax.naming.NameNotFoundException: > > That path specification is incorrect, regardless of the v

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. http://tomcat.apache.org/tomcat

RE: javax.naming.NameNotFoundException: Name pool is not bound inthis Context

2006-11-28 Thread Macari McCorry, Gerardo
Yep I have defined as: DB Connection pool javax.sql.DataSource Container -Mensaje original- De: Mark Thomas [mailto:[EMAIL PROTECTED] Enviado el: martes, 28 de noviembre de 2006 13:48 Para: Tomcat Users List Asunto: Re

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

2006-11-28 Thread Martin Gainty
Gerardo- http://tomcat.apache.org/tomcat-6.0-doc/printer/jndi-datasource-examples-howto.html server.xml need to identify all of the attributes of the DataSource as in ... web.xml needs to identify resource-ref name of jdbc/TestDB as DataSource http://java.sun.com/xml/ns/j2ee"; xmln

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

2006-11-28 Thread Mark Thomas
Macari McCorry, Gerardo wrote: > Hi all, > > Problem: Trying to asociate a database pool to a local context > Error: "javax.naming.NameNotFoundException: Name pool is not bound in this > Context'" Have you defined a element in web.xml? Mark ---