Jacob Kjome wrote:Have you looked at the ConfigurationServlet in the logging-log4j-sandbox?
http://cvs.apache.org/viewcvs.cgi/logging-log4j-sandbox/src/java/org/apache/log4j/servlet/ConfigurationServlet.java
Hadn't seen it actually... thanks!
No problem.
You might want to verify whether your implementation provides all the capabilities of the one above. If yours is more sophisticated, then it might be a candidate for the sandbox. You might also think about patching the existing ConfigurationServlet to provide it with the (assumed) enhanced functionality that yours provides.
Mine is almost certainly less sophisticated considering that I have about an hour into adapting it from the embeddable servlet like thing I found in the contribs directory by Rutger Mentzer or someone.
IMO, Some of this stuff might be better off being in a log4j-optional.jar so that the core log4j.jar is kept to a minimal size with only core logging functionality.
I kinda thought that too actually, although the servlet I have and the one above are both quite small. The chainsaw stuff seems to be more of a concern space wise I would think.
Both GUI log viewers will have their own separate jars, at least that was the consensus last I remember. Log4j-1.3.jar should be smaller than Log4j-1.2.8.jar. And depending on how much servlet and other non-core stuff like it gets written, it could add up, hence the need for a separate log4j-optional.jar.
Jake
-- Cheers, Derek
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
