-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Walter,
walterw wrote:
> Here are the exact contents in the file after maven filters it.
>
> [code]
>
>
>
Could the double-XML processing instruction be causing a choke?
- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comm
> From: walterw [mailto:[EMAIL PROTECTED]
> Subject: RE: JNDI configuration in webapp/META-INF/context.xml
>
>
> WEB-INF/web.xml
>
> type="javax.sql.DataSource"
> driverClassName="${jdbc.driver}" u
> From: walterw [mailto:[EMAIL PROTECTED]
> Subject: RE: JNDI configuration in webapp/META-INF/context.xml
>
>
> WEB-INF/web.xml
>
> type="javax.sql.DataSource"
> driverClassName="${jdbc.driver}" u
Hi,
Thanks for your reply. I noticed my configuration in the Tomcat
installation directory did have a capital C in context. However, the files
are identical now, but I'm still not getting a JNDI connection.
[code]
WEB-INF/web.xml
[/code]
Thanks for your suggestio
> From: walterw [mailto:[EMAIL PROTECTED]
> Subject: JNDI configuration in webapp/META-INF/context.xml
>
> Here is the configuration I am using:
>
It's , not - case matters.
>
Ditto.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for
Hi,
Thanks for your reply, but I am still getting the same error.
[code]
Caused by: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create
JDBC driver of class '' for connect URL 'null'
at
org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1150)
Walter:
check your META-INF/context.xml attribute useNaming="true"
http://tomcat.apache.org/tomcat-5.5-doc/config/context.html
HTH
Martin
__
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official b