You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2006/01/22 14:18:08 UTC

DO NOT REPLY [Bug 38337] - GlobalNamingResource will not allow commercial DataSource drivers

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 gdoret@gmail.com  2006-01-22 14:18 -------
The tomact GlobalNamingResources documentation
(http://tomcat.apache.org/tomcat-5.5-doc/config/globalresources.html) says:

"The GlobalNamingResources element defines the global JNDI resources for the Server.
These resources are listed in the server's global JNDI resource context. This
context is distinct from the per-web-application JNDI contexts described in the
JNDI Resources HOW-TO. The resources defined in this element are not visible in
the per-web-application contexts unless you explicitly link them with
<ResourceLink> elements."

Try to add a ResourceLink in the context.xml file of each web application. For
example:

<ResourceLink name="jdbc/cabledslink"
            global="jdbc/cableds"
            type="com.jnetdirect.jsql.JSQLPoolingDataSource"



-- 
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