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=35648>. 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=35648 ------- Additional Comments From [EMAIL PROTECTED] 2005-08-03 14:48 ------- (In reply to comment #2) > My point of reporting this issue was for usage outside of Tomcat and using > Anonymous loggers. You could tel me that is is unsupported. > > With the release of juli that comes with 5.5.9 the error I reported allways happens. > > I have tested with the new release 5.5.10-alpha and this is solved, so > something > was changed. > > You could considering having JULI as a jakarta-commons sub-project, or as a > subroject of logging.apache.org. java.util.logging is designed to be pluggable by replacing the the sigleton LogManager, and providing one which is tuned for your application/container/etc. So the (only) LogManager provided is tuned for the Tomcat classloading hierarchy. For other usages, there's of course the possibility of reusing portions of the code, but it would likely be better to use another LogManager with a different behavior. A JULI project elsewhere would be fine, as a collection of: - various LogManager implementations - Handler implementations - also implementations of other accessory components like formatters -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
