(a stand-alone main), it returns the expected value jdbc/mypool.
Why is my resource name ignored or otherwise not used when running under
the container?
Thanks.
--
Scott Dudley | Senior Developer
Telesoft | 1661 E. Camelback Road, Suite 300 | Phoenix, AZ 85016
P: 602.308.1115 | F: 602.308.1300
-name
url-pattern/webdav/*/url-pattern
/web-resource-collection
auth-constraint
role-nametomcat/role-name
/auth-constraint
/security-constraint
login-config
auth-methodBASIC/auth-method
realm-namedefault/realm-name
/login-config
security-role
role-nametomcat/role-name
/security-role
--
Scott Dudley
Caldarale, Charles R wrote:
From: Scott Dudley [mailto:sc...@telesoft.com]
Subject: Tomcat 5 vs 6 Context useNaming Behavior
We have a legacy application that's been running on the 5.5.X versions
for several years.
Under what JVM? And platform?
I've tested under both
We have a legacy application that's been running on the 5.5.X versions
for several years. This application manipulates the JNDI context in
such a manner that would now be considered unusual. In a nutshell,
it's because the application framework was written concurrent with and
prior to
.
Many thanks.
--
Regards,
Scott Dudley
