Imagine the following scenario:
An application is started using an initial Log4J configuration file at
startup. Then the user opens a the GUI to create i.e. a new user. In the GUI
you can now create a new category (and appenders) for the new user. It
should also be possibly to change/delelete categories, appenders, kind-of
appenders and priorities via the GUI.
Now the question: if the change of configuration is done via a property
file, this would need the following steps:
1- read the config file
2- read the data entered in the GUI
3- parse the config file and add the changes coming from the GUI
4- call property configurator to take effect of the changes
5- write the changed property file to disk, using PropertyPrinter
isn' t there a shorter way, or is this workflow clever?
Thilo
IMPRESS SOFTWARE AG
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
