Mailing-List: contact log4j-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@jakarta.apache.org>
Message-Id: <5.2.0.9.2.20030212075355.028e03f0@shell.visi.com>
Date: Wed, 12 Feb 2003 08:00:30 -0600
To: "Log4J Developers List" <log4j-dev@jakarta.apache.org>
From: Jacob Kjome <hoju@visi.com>
Subject: Re: SV: Configuration GUI
In-Reply-To: <C15076D7FE61D211A37A0001FAF86A177F9FA9@s31ap001.sandsli.dn
 b.no>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_47123875==.ALT"

--=====================_47123875==.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed


Hi Hermod,

JAXB would be somewhat undesirable, IMHO, because the JAXB libraries would 
be required at runtime in order for the generated classes to work.  If a 
DTD is all that is required, then a much better solution is Zeus.
http://zeus.enhydra.org/index.html

The generated classes are totally standalone.  No special runtime libraries 
are required.

If you require XSD then, unfortunately, Zeus will not fit-the-bill because 
it, currently, does not support XML Schema.  Actually, I'd rather have it 
support RelaxNG which is far more straightforward and elegant than XML 
Schema is, but that is another topic.

Jake

At 12:14 PM 2/12/2003 +0100, you wrote:
>Hi
>
>Make it open ended - Meaning that the actual
>serialization/deserialization of the properties is plugable. If someone
>could send me the DTD/XSD for the XML configuration file, I'll be happy
>to create the java stuff (using JAXB).
>
>regards
>HErmod
>
>-----Opprinnelig melding-----
>Fra: Richard Bair [mailto:rbair@dtint.com]
>Sendt: 11. februar 2003 18:59
>Til: Log4J Developers List
>Emne: 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: log4j-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: log4j-dev-help@jakarta.apache.org
>
>
>* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>
>This email with attachments is solely for the use of the individual or
>entity to whom it is addressed. Please also be aware that DnB cannot
>accept any payment orders or other legally binding correspondence with
>customers as a part of an email.
>
>This email message has been virus checked by the virus programs used
>in the DnB Group.
>
>* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: log4j-dev-help@jakarta.apache.org

--=====================_47123875==.ALT--