Shapira, Yoav wrote:
Howdy,
I definitely meant the -1 in an opinion way, there's no vote ;) And I
don't mean it to discourage your, or any other, discussion topics.
My appologies for reacting so strongly. I'll interpret these things much
more lightly in the future :-)
There are tools to represent configurations and their sources, and
composite them somewhat intelligently. I've contributed some relevant
code to the commons-configuration project (still in the sandbox,
although I have a partial commons-proper promotion proposal in thr
works) which you may find useful.
I'll look over the configurator in more detail this week.
There was also a suggestion to write more powerful configurators: while
this is possible, I would also point out that log4j can configure itself
from a URL. This should be sufficient for nearly every need, as the URL
can indicates a JNDI resource, a file resource, a remote http/https
resource, etc. I personally use all of the above URL schemes to
configure log4j in various production systems.
One could "stretch" the Hierarchical Config concept into here as well,
where multiple URL's could designate config and "add/replace" config
attribute in a specifc ordering.
So in conclusion: I don't think I misunderstood your request ;) As I
said above, the -1 is just an opinion. The XML inclusions Ceki
suggested are one way forward from here. Another one would be to write
a utility class that composites several log4j configuration files, use
it in your organization, and eventually contribute it to the log4j
sandbox for everyone else to try?
I would contribute it if I decide to go that route.
thanks,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
