commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 36664] - [configuration] Composite configuration with JNDI logs failed access as ERROR
Date Thu, 15 Sep 2005 08:02:01 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=36664>.
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=36664





------- Additional Comments From ebourg@apache.org  2005-09-15 10:02 -------
Good point, missing properties in the JNDI context shouldn't be logged as
errors, but it is desirable to log the other errors. What exception is really
thrown by Context.lookup ? Is it a NameNotFoundException, or just a
NamingException as documented in the javadoc ? If the implementation throws a
NameNotFoundException we could remove the logging for this case and keep it for
the other errors.

-- 
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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message