There is already a JDK logger plugin available: "org.jboss.logging.jdk.JDK14LoggerPlugin". If you want to use the JDK logging plugin, pass in the "--log=jdk" argument to the run script. Be aware that JDK logging won't be fully functional though. In 5.1.0 we've introduced a log bridge component and improved JDK LogManager that allows JDK logging and log4j messages to be forwarded to the same log.
I need to use the JDK logger that my plugin provides as it sets up the log levels and log handlers required by my applications. But if some of the component services in JBoss need a log4j instance instead of the logger plugin then the plugin model is not viable for me.
Besides the three parameters (name of the plugin class, implementation JAR and the logging.properties file) is there anything else that the" --log=jdk" setup that I need to do get my logger plugin to work with all component services?