-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David,
On 7/14/2009 11:29 AM, David Smith wrote: > In the past, it's typically been caused by some misspell of the JNDI > name between the <Resource ..../> element and the > <resource-ref>...</resource-ref> in the WEB-INF/web.xml. I've never had to use a <resourcr-ref> element in web.xml for a <Resourcre> defined in META-INF/context.xml. I've even created incorrect <resource-ref> elements in web.xml and not had a problem. I /do/ have them in there, though, just in case :) > I'd have to go > back to the original post to tell if that's the case here or not. Tsk, tsk. It was only a few hours ago: META-INF/context.xml: > <Resource name="jdbc/AppDatabase" web.xml: > <resource-ref> > <description>DB Connection</description> > <res-ref-name>jdbc/AppDatabase</res-ref-name> > <res-type>javax.sql.DataSource</res-type> > <res-auth>Container</res-auth> > </resource-ref> Looks good to me. > Either that or the resource was declared as a global resource without > the requisite <ResourceLink /> in the context. Nope, it was done in the recommended way (from the Tomcat docs, and checked multiple times according to the OP). > Either way, it's > typically a disconnect between the <Resource .../> and it's use in the > jsp/servlet code. He didn't post his code. It would be good to see what is on line 208 in com.wirefast.wsam.service.WMSSubmissionService.getConnection. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkpcqD0ACgkQ9CaO5/Lv0PBSBACaA3d45tyyA7K62NtHS4NWZ7FA 9KcAn0xqAVHruti85qkheBztd25N/n0d =N63Z -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
