tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 38337] - GlobalNamingResource will not allow commercial DataSource drivers
Date Tue, 24 Jan 2006 14:03:32 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38337>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38337





------- Additional Comments From bloritsch@apache.org  2006-01-24 15:02 -------
The original issue I had was that a global naming resource appeared as if it
would not allow me to use the driver when the resource was declared in
<GlobalNamingResource/> and not <Context/>.  Thanks to Geoffery's input I found
I needed to use a <ResourceLink/> in the context because the app's context and
global context were isolated.

The problem is that if they _are_ isolated then resource names bound in the
<GlobalNamingResource/> should not be recognized in your application <Context/>.
 They are being recognized and instead of the expected
javax.naming.NameNotFoundException I got the NullPointerException.  The
NullPointerException is completely understandable because I never provide the
driver class in the <Resource/> definition because I am not using DBCP.  It is
troubling that the local app context is trying to resolve the name that should
_not_ exist.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message