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 23950] - [PATCH] Context.listBindings(...) broken?
Date Wed, 04 Jan 2006 13:41:33 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=23950>.
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=23950





------- Additional Comments From emiller@planalytics.com  2006-01-04 14:41 -------
Upon further investigation it seems like the resolution from Reference to 
Object should always be handled by NamingContext.  This allows NamingContext to 
replace its internally stored Reference with the resolved Object, which would 
not happen if resolution was managed directly by 
NamingContextBindingsEnumeration (including my patch).  If it is not 
implemented this way then Objects with the same name returned from listBindings
(...) may not equal those returned by lookup(...).  I don't know if this is 
contractually required by the JNDI SPI but it seems safer to ensure equality.

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