[EMAIL PROTECTED] wrote:
Man I hate this logging problem we are starting to see with Java, where everybody and his dog has a proprietary logging system.
Commons logging
Log4j
java.util.Logger
Avalon LogKit.
Please note that Commons Logging can wrap any of those - that's why it is preferred. It gives you freedom to choose any logger you want.
All have pretty much the exact same functionality.
Since it's now available, why doesn't everyone just use java.util.Logger now? When last did anyone need to support Java 1.3 for a beta delivery of Xindice?
Last beta, 1.1b3, is jdk1.3 built & compatible.
In addition, since xindice is now deployed as a war file embedded in Tomcat,
or Jetty - by default.
and by default has enough logging enabled to make a sailor blush, or at least to severaly impact performance, it seems a better solution to logging is required.
There is no way to specify env variables to a war deployment, unless you write your own deployment descriptor and do a custom servlet deployment, which is a real pain in the ...
Hint to Xindice gods: Tune logging to be a bit quieter in the deliveries, and if people require, they can manually set it a bit higher.
That's not a bad advice, I guess we can do this.
PS There are no gods here, everybody is free to patch and send a patch to -dev list.
Vadim
