[jboss-as7-dev] Adding more trace level logging

[Scott Stark]

One example location is in the 
org.jboss.as.server.Bootstrap.Configuration inner class, which has no 
logger. I need to know what the absolute path to the standalone.xml file 
is that the server is trying to load. So, is there a pattern to where we 
are allowing loggers vs Stdout?

It looks like the logger categories are more along the lines of 
subsystem names rather than simply using the class name which is 
embedding the logger. Any usage guidelines to follow for that?

         public synchronized ExtensibleConfigurationPersister 
getConfigurationPersister() {
             if (configurationPersister == null) {
                 if (serverEnvironment == null) {
                     configurationPersister = new 
NullConfigurationPersister(new StandaloneXml(moduleLoader));
                 }
                 else {
                     QName rootElement = new 
QName(Namespace.CURRENT.getUriString(), "server");
                     StandaloneXml parser = new 
StandaloneXml(Module.getBootModuleLoader());
                     File xmlFile = new 
File(serverEnvironment.getServerConfigurationDir(), "standalone.xml");
*                    System.out.printf("Using standalone configuration: 
%s", xmlFile.getAbsolutePath());
*                    configurationPersister = new 
BackupXmlConfigurationPersister(xmlFile, rootElement, parser, parser);
                 }
             }
             return configurationPersister;
         }

On 3/23/11 2:03 PM, Scott Stark wrote:
> With the problems with the debugger crashing the server vm, I'm finding
> I need to add a lot of trace level statements to both the AS and
> components to try to figure out why things don't work. What is the best
> way to get these additions back into the AS codebase at least?
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-as7-dev/attachments/20110323/ad39caf5/attachment.html