On Tue, 26 Aug 2003 09:04, Madere, Colin wrote: > Well then it may be something else. I'm essentially doing what you are > with a JNDI datasource defined in the DefaultContext with nothing in the > web.xml (except to pass along the JNDI name so it's not hard-coded). It > breaks for me (and a bunch of other people posting recently using 4.1.x) > when I try to move that to GlobalNamingResources and use a ResourceLink.
I have tried various configurations. If there is nothing in the web.xml you get a different error, and the error occurs earlier, ie in init phase. If there is a reference in the web.xml the init of the connection pool appears to work, but fails with the "null" exception when you try to obtain a connection. Bottom line is the same problem has two different sets of errors depending on the configuration. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
