Hi, A random thought, but I would endeavour to keep the internal representation of the configuration independent of the external representation. That way it is possible to support multiple external formats. You have mentioned XML and properties files.
I know that the Jalopy source code formatter comes with a nice configuration tool. That may be a source of inspiration (pun intended :-). It is at http://jalopy.sourceforge.net/. And yes - I think a tool like this would be useful. I base this on the number of tools I know use to edit Struts config files. You could also look at these tools for inspiration. Cheers, Oliver > -----Original Message----- > From: Richard Bair [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, 12 February 2003 04:59 > To: Log4J Developers List > Subject: Configuration GUI > > > Hey Folks, > > I'm gearing up to write a preliminary gui for editing log4j > configuration files. I don't know of any that currently exist(?). My > employer has need of a simple configuration gui (it won't be very > flexible in this first version). After writing that, I'll be more > familiar with the issues involved and will start tackling a more generic > setup on my own time. > > Initially I was planning on using DOM for parsing and modifying XML > config files. It seemed a natural fit. However, in the spirit of > logging.apache.org, and because one of our requirements at work is that > our app work for all of the log4j variants (perl and c++ in particular), > it looks like we'll have to use standard properties files. > > I'm wondering if anybody out there: > > 1) Has tried to build one of these before and has any ideas > 2) Knows of code that would be a good fit for parsing and saving the > properties files (log4j obviously has code for parsing the properties > file, but I don't know if it will be applicable or need reworking) > 3) Thinks this is a bad idea ;-) > > Ideally, we'd be able to provide plugin functionality so that no matter > what configuration file style users prefer, we'd be able to read/write > them. > > Thoughts? > Richard > > > --------------------------------------------------------------------- > 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]
