dev@glassfish.java.net

useless traces in the V3 TP2 (b10) server log:

From: Ludovic Champenois <Ludovic.Champenois_at_Sun.COM>
Date: Mon, 21 Apr 2008 21:33:44 -0700

Deploy a web app from the b10 v3 build, Log file contains:


INFO: AMXConfigLoader.sortAndDispatch: 2 events
Apr 21, 2008 9:29:14 PM com.sun.enterprise.web.WebApplication start
INFO: Loading application ttt-java at /ttt-java
Apr 21, 2008 9:29:14 PM com.sun.enterprise.v3.deployment.DeployCommand
execute
INFO: Deployment of ttt-java done is 60 ms
Apr 21, 2008 9:29:14 PM
INFO: AMXConfigLoader.sortAndDispatch: 14 events
Apr 21, 2008 9:29:14 PM
INFO: AMXConfigLoader.sortAndDispatch: process new ConfigBean:
com.sun.enterprise.config.serverbeans.Engine
Apr 21, 2008 9:29:14 PM
INFO: AMXConfigLoader.sortAndDispatch: process new ConfigBean:
com.sun.enterprise.config.serverbeans.Engine
Apr 21, 2008 9:29:14 PM
INFO: AMXConfigLoader.sortAndDispatch: process new ConfigBean:
com.sun.enterprise.config.serverbeans.ApplicationRef
Apr 21, 2008 9:29:14 PM
INFO: AMXConfigLoader.sortAndDispatch: process new ConfigBean:
com.sun.enterprise.config.serverbeans.Application

It seems to be traces for the V3 internal developer, not the V3 user...

Do we plan to do a log cleanup in the final TP2 bits?

Ludo