是否可以覆盖Glassfish v3的默认日志记录？

Question

Related to this question . It appears that Glassfish is exporting slf4j into my application and overriding my logging solution. Is it possible for me to override Glassfish's logging and have my own logging solution take precedence? After searching, I have only found ways to modify the log using logging.properties.

I am not married to my current implementation, but I am interested in making it work.

thanks.

Answer 1

As suggested in the other answer , try to configure GlassFish to use firstly the child classloaders before to delegate. In the sun-web.xml :

 
 
 
  
  <sun-web-app> <class-loader delegate="false"/> </sun-web-app>
 
  

But if this works, this is more a workaround that a real solution , your application shouldn't be polluted by the SLF4J bindings of bean-validation.jar and weld-osgi-bundle.jar (at least I believe so). You should maybe raise an issue .

Update: For the archives, the suggested workaround doesn't work. But I couldn't reproduce the issue .

Answer 2

The short answer is, Glassfish does some nasty logger tweaking, redirecting System.out and System.err to its own log. I did not manage to stop it doing so, but I found a way to collect all server and application log messages in a single slf4j log by placing the slf4j libs early enough in the classpath and editing the logging.properties of Glassfish.

For the long answer, see this blog post .