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 Summary: Composite configuration with JNDI logs failed access as ERROR Product: Commons Version: 1.1 Final Platform: All OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Configuration AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] CC: [email protected] This is a report from the Turbine developer list. Commons configuration 1.1 logs failed JNDI lookups at ERROR level. I use the composite configuration as follows <configuration> <jndi prefix="java:comp/env"/> <properties fileName="WEB-INF/conf/TurbineResources.properties"/> </configuration> This configuration is described in the configuration-howto of Turbine. The expected behaviour is that the entries in the JNDI context overwrite those in the properties file. That, in turn, means, that usually only a few configuration keys will exist in the JNDI context. In the current version of commons-configuration (1.1) this means an error entry in the log with every access to a not overridden configuration key (which are the majority). Could you please reduce the log level for this or return to the behaviour of version 1.0 not to log this at all? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
