This reminds me, I made changes to the Log4jAdmin page that I didn't get round to
making public yet - I replaced the dropdown box with a set of radio boxes next to each
logger, making it much easier (I think) to update the configuration. I also added an
"INHERITED" level (just sets the threshold back to null).
There's a small bug - if you try to set the level to INHERITED when it's specifically
defined to be something else in the log4j.properties file, it won't work - instead,
you have to change to something else (eg change from DEBUG -> WARN), hit apply, then
try again with the inherited, and second time round it works. I have an idea of where
the problem is but haven't had time to fix it yet.
I'll attach the source, in case anyone's interested.
(See attached file: ConfigurationServlet.java)
Cheers,
Stephen
Nathan Coast
<[EMAIL PROTECTED] To: Log4J Users List <[EMAIL
PROTECTED]>
com> cc:
Subject: Re: generating log4j.xml
20/08/2004 13:01
Please respond to
"Log4J Users
List"
I'm about to push out a new version of the Log4J admin web app. With the webapp, you
can
modify the in-memory configuration but once you reboot, you're back to where you
started
from. I'd like to add a feature to write the modifications back to the config file.
To
do this I'll need something to generate a config file from the current runtime
configuration.
Shapira, Yoav wrote:
> Hi,
> I'm not that gung-ho about configuration-file-generation tools. We've
> had some bitter experiences in the Tomcat area related to this. The
> problem is that the code tends to develop faster than the
> configuration-file-generation tool and so the configuration file
> generator outputs either incomplete or invalid configuration files (at
> worst), or just doesn't expose all the functionality of the code (which
> is not that bad a scenario).
>
> If someone wants to develop and maintain it, good for them. I'm not
> sure it belongs in the log4j core, at least initially. If it stands the
> test of tiem (as a contrib module perhaps, or a sandbox one), and gets
> significant usage, then maybe.
>
> Yoav Shapira
> Millennium Research Informatics
>
>
>
>>-----Original Message-----
>>From: Paul Smith [mailto:[EMAIL PROTECTED]
>>Sent: Tuesday, August 17, 2004 11:42 PM
>>To: 'Log4J Users List'
>>Subject: RE: generating log4j.xml
>>
>>
>>>I'd be glad to volunteer as I need it for the project I'm working on.
>>>My concern is that any xml generator would become obsolete with log4j
>>>1.3. From the docs, I see that 1.3 xml configuration is achieved
>
> using
>
>>>something called the joran configurator
>>>http://www.qos.ch/logging/JoranConfigurator.html
>>>
>>>would it make more sense to develop something like a
>
> JoranConfigWriter?
>
>>Well, you could call it that, but the reading and configuring is done
>
> by
>
>>JoranConfigurator, but one could think that once a LoggerRepository is
>>configured, it's configuration could be output in any form (properties,
>>XML,
>>whatever). If we have a class that walks the LoggerRepository loggers,
>>appenders, and plugins, and outputs the configuration file in some
>
> format
>
>>(obviously XML in the format JoranConfigurator can read would be the
>
> most
>
>>useful first version) that would be perfect.
>>It should be straightforward from a Junit point of view too. Given an
>
> XML
>
>>configuration file, use JoranConfigurator to configure, then use
>>NathansCoolConfigWriter to write the xml file back out, and then
>
> compare
>
>>the
>>2 xml files together for success/failure.
>>
>>
>>>I know this has probably been asked a thousand times.... how far off
>
> is
>
>>>1.3? a week, a month, a year?
>>
>>echo "how far off is 1.3?" > /dev/idontknow/
>>cheers,
>>Paul Smith
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
>
> This e-mail, including any attachments, is a confidential business communication,
> and may contain information that is confidential, proprietary and/or privileged.
> This e-mail is intended only for the individual(s) to whom it is addressed, and may
> not be saved, copied, printed, disclosed or used by anyone else. If you are not
> the(an) intended recipient, please immediately delete this e-mail from your computer
> system and notify the sender. Thank you.
>
>
> ---------------------------------------------------------------------
> 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]
--
This e-mail may contain confidential and/or privileged information. If you are not the
intended recipient (or have received this e-mail in error) please notify the sender
immediately and destroy this e-mail. Any unauthorized copying, disclosure or
distribution of the material in this e-mail is strictly forbidden.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
