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 2011/04/13 00:23:48 UTC

DO NOT REPLY [Bug 47396] Ability to load & bind an external naming context

https://issues.apache.org/bugzilla/show_bug.cgi?id=47396

Mark Thomas <ma...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #1 from Mark Thomas <ma...@apache.org> 2011-04-12 18:23:43 EDT ---
I think it would be better to address the root cause of this issue, that Tomcat
was returning the same object from a JNDI lookup rather than a new one. That
issue was reported (and fixed) as bug 49994. However, that in turn caused big
problems (bug 50159) for JNDI DataSources where apps expect the same connection
pool to be used for each lookup.

Tomcat 7 has addressed this by introducing the singleton attribute for
resources. There are no plans to back-port the singleton feature to Tomcat 6
but if it is required please re-open bug 50159 and request a back-port to
Tomcat 6.

I am closing this as won't fix since it addresses the symptom rather than the
root casue.

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

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