This chapter contains solutions for various common problems you may encounter when using Metawidget.
The first step to troubleshooting is to enable DEBUG or TRACE logging. The exact procedure for doing this varies depending on your environment, but here are some suggestions:
If your application does not use Apache Commons Logging, Metawidget will default to java.util.Logging. Locate the logging.properties file (eg. <JAVA_HOME>/jre/lib/logging.properties) and edit it. Set .level=FINE and java.util.logging.ConsoleHandler.level=FINE.
If your application uses Apache Log4J (possibly underneath Apache Commons Logging) locate the log4j.xml file (eg. /jboss-5.1.0.GA/server/default/conf/jboss-log4j.xml) and edit it. Remove any reference to <param name="Threshold" ...>.
If your application uses JBoss Logging (ie. under JBoss AS 6) locate the jboss-logging.xml file (eg. /jboss-6.0.0.Final/server/default/deploy/jboss-logging.xml) and edit it. Under the <console-handler> section set <level name="DEBUG"/>. Under the <root-logger> section set <level name="DEBUG"/>.
If you are running Tomcat 7 under Eclipse, make sure you edit the server's launch configuration and include a VM argument of -Djava.util.logging.config.file=<tomcat path>/conf/logging.properties. Then edit <tomcat path>/conf/logging.properties as described above.
If you are running JBoss AS 7, you will need to edit the <subsystem xmlns="urn:jboss:domain:logging:1.1"> section of standalone.xml. Under the <console-handler> section set <level name="DEBUG"/>. Under the <root-logger> section set <level name="DEBUG"/>.