[jbpm-issues] [JBoss JIRA] Updated: (JBPM-2422) investigate if logging abstraction should be removed

[ https://jira.jboss.org/jira/browse/JBPM-2422?page=com.atlassian.jira.plug... ] Tom Baeyens updated JBPM-2422: ------------------------------ Description: the current approach is to have a minimal log framework pluggability: ---------------------------------------------------------------------------------------------- 1) jdk logging because we want it to be possible to run pvm without external library dependencies 2) log4j as jboss doesn't include a jdklogging-to-log4j bridge. general links ------------------ http://www.jboss.org/community/wiki/Logging select between these options: ----------------------------------------- 1) always require a jbpm.logging.properties on the classpath. that configures the jdk logging. eithers completely, or with a delegation to log4j in that case our jbpm code can always use the jdk logging. 2) keep it as it is 3) similar solution to seam for facelets: === http://markmail.org/message/ywamc5yc7hejrlls ==================================================================== Subject: Facelets JDK Logging -> JBoss Log4j bridge Actions... From: Pete Muir (pmu...(a)bleepbleep.org.uk) Date: Feb 19, 2008 7:27:50 am List: net.java.dev.facelets.dev As has been discussed many times on the seam forum and facelets mailing list, JBoss AS doesn't have a jdk logger -> log4j generic bridge (I don't know why, and I don't really want to find out) so what Stan did for JSF RI was write a JDK logging filter that would bridge JUL to log4j. I have done the same for Facelets (included as part of jboss-seam-ui.jar, I can factor out the relevant code if anyone wants it) but hit a sight problem. Most logs in facelets are declared protected static final (so I can get at them using reflection) but in DefaultFacelet, CompositionHandler and DecorateHandler they are protected final (so I can't get at them easily as they aren't static). Any chance they could become static? Let me know and I'll file a bug. Code is here http://fisheye.jboss.org/browse/Seam/trunk/ui/src/main/java/org/jboss/sea... Thanks, Pete -- Pete Muir http://in.relation.to/Bloggers/Pete http://www.seamframework.org ============================================================================================================ was: the current approach is to have a minimal log framework pluggability: ---------------------------------------------------------------------------------------------- 1) jdk logging because we want it to be possible to run pvm without external library dependencies 2) log4j as jboss doesn't include a jdklogging-to-log4j bridge. general links ------------------ http://www.jboss.org/community/wiki/Logging select between these options: ----------------------------------------- 1) always require a jbpm.logging.properties on the classpath. that configures the jdk logging. eithers completely, or with a delegation to log4j in that case our jbpm code can always use the jdk logging. 2) keep it as it is 3) similar solution to seam for facelets: ===http://markmail.org/message/ywamc5yc7hejrlls==================================================================== Subject: Facelets JDK Logging -> JBoss Log4j bridge Actions... From: Pete Muir (pmu...(a)bleepbleep.org.uk) Date: Feb 19, 2008 7:27:50 am List: net.java.dev.facelets.dev As has been discussed many times on the seam forum and facelets mailing list, JBoss AS doesn't have a jdk logger -> log4j generic bridge (I don't know why, and I don't really want to find out) so what Stan did for JSF RI was write a JDK logging filter that would bridge JUL to log4j. I have done the same for Facelets (included as part of jboss-seam-ui.jar, I can factor out the relevant code if anyone wants it) but hit a sight problem. Most logs in facelets are declared protected static final (so I can get at them using reflection) but in DefaultFacelet, CompositionHandler and DecorateHandler they are protected final (so I can't get at them easily as they aren't static). Any chance they could become static? Let me know and I'll file a bug. Code is here http://fisheye.jboss.org/browse/Seam/trunk/ui/src/main/java/org/jboss/sea... Thanks, Pete -- Pete Muir http://in.relation.to/Bloggers/Pete http://www.seamframework.org ============================================================================================================ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira