>     I've only been using log4j for a few months now, and while reading
> this mailing list, a question has been forming in my mind.  It looks
> like most people use an XML formatted configuration file.  I am not
> currently doing that, but I got wondering.

Currently I'm using property files, too.

>     It looks like there is a limit to what I can do with the
> property-list style configuration file.  Is this true?  Even 
> if I'm not doing something fancy now, would it be better to 
> switch to using an XML
> configuration file so that, if I needed to, I could enable the more
> complex features (without changing my source code)?  Or can I do
> everything in the property-list style file?

There are things you can't do with property files, such as using an
AsyncAppender. I think they tend to be nested configurations, basically.
I do wonder whether this is just a problem with the current property
configurator, however, and one which could be overcome with a bit of
ingenuity.

>     I have an off topic question which people can choose to 
> ignore.  If
> you have an answer/suggestion, feel free to email directly if 
> you don't
> want to pollute the list.
>     Since I program in Perl as well as java, I know all about CPAN. 
> I've been looking for a web site similar to CPAN, but for java jars. 
> I've looked at jars.com, but the descriptions aren't rich 
> enough and the
> categories aren't specific enough (at least for what I was recently
> looking for.)  Basically, I'm just spoiled with CPAN.  I can usually
> find something related quickly when I look around CPAN... and I think
> java would benefit from this too.
>     Are there any well organized, well indexed web sites for 
> java jars?

I rarely want a library which isn't either provided by Sun on
java.sun.com, Jakarta at jakarta.apache.org, Apache XML at
xml.apache.org, or which a quick web search can't find, personally.

Jon

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to