May 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBLOGGING-94) JBoss Logging does not detect log4j 2.0

by Nicholas Williams (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-94?page=com.atlassian.jira.plug... ] Nicholas Williams commented on JBLOGGING-94: -------------------------------------------- I didn't realize JBoss Logging was on GitHub. I have submitted a pull request. > JBoss Logging does not detect log4j 2.0 > --------------------------------------- > > Key: JBLOGGING-94 > URL: https://issues.jboss.org/browse/JBLOGGING-94 > Project: JBoss Logging > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jboss-logging-log4j > Affects Versions: 3.1.2.GA > Environment: Hibernate > Reporter: Henry Clout > Assignee: James Perkins > > The class org.jboss.logging.LoggerProviders checks for the presence of log4j using the code: > {code} > private static LoggerProvider tryLog4j(final ClassLoader cl) throws ClassNotFoundException { > Class.forName("org.apache.log4j.LogManager", true, cl); > // JBLOGGING-65 - slf4j can disguise itself as log4j. Test for a class that slf4j doesn't provide. > Class.forName("org.apache.log4j.Hierarchy", true, cl); > return new Log4jLoggerProvider(); > } > {code} > However, despite having the log4j-1.2-api-2.0.jar bridge included, this fails as the class org.apache.log4j.Hierarchy is not present in log4j 2.0. > I worked around this by forcing JBoss logging to use slf4j (which is then proxied to log4j) by setting the -Dorg.jboss.logging.provider=slf4j option. > As a proper fix, however, how about checking for a class that is included in log4j 1.2, 2.0 but not slf4j? org.apache.log4j.config.PropertySetter seems to tick the box. > I tested changing the afore mentioned method to: > {code} > private static LoggerProvider tryLog4j(final ClassLoader cl) throws ClassNotFoundException { > Class.forName("org.apache.log4j.LogManager", true, cl); > // JBLOGGING-65 - slf4j can disguise itself as log4j. Test for a class that slf4j doesn't provide. > Class.forName("org.apache.log4j.config.PropertySetter", true, cl); > return new Log4jLoggerProvider(); > } > {code} > And indeed I started receiving logging messages from Hibernate (via JBoss logging.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-94) JBoss Logging does not detect log4j 2.0

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-94?page=com.atlassian.jira.plug... ] James Perkins commented on JBLOGGING-94: ---------------------------------------- I have not looked much at log4j2 yet. We don't have much of a road map as JBoss Logging really does change all that much. A high level overview of it is it's just a logging facade that works with the major log managers. > JBoss Logging does not detect log4j 2.0 > --------------------------------------- > > Key: JBLOGGING-94 > URL: https://issues.jboss.org/browse/JBLOGGING-94 > Project: JBoss Logging > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jboss-logging-log4j > Affects Versions: 3.1.2.GA > Environment: Hibernate > Reporter: Henry Clout > Assignee: James Perkins > > The class org.jboss.logging.LoggerProviders checks for the presence of log4j using the code: > {code} > private static LoggerProvider tryLog4j(final ClassLoader cl) throws ClassNotFoundException { > Class.forName("org.apache.log4j.LogManager", true, cl); > // JBLOGGING-65 - slf4j can disguise itself as log4j. Test for a class that slf4j doesn't provide. > Class.forName("org.apache.log4j.Hierarchy", true, cl); > return new Log4jLoggerProvider(); > } > {code} > However, despite having the log4j-1.2-api-2.0.jar bridge included, this fails as the class org.apache.log4j.Hierarchy is not present in log4j 2.0. > I worked around this by forcing JBoss logging to use slf4j (which is then proxied to log4j) by setting the -Dorg.jboss.logging.provider=slf4j option. > As a proper fix, however, how about checking for a class that is included in log4j 1.2, 2.0 but not slf4j? org.apache.log4j.config.PropertySetter seems to tick the box. > I tested changing the afore mentioned method to: > {code} > private static LoggerProvider tryLog4j(final ClassLoader cl) throws ClassNotFoundException { > Class.forName("org.apache.log4j.LogManager", true, cl); > // JBLOGGING-65 - slf4j can disguise itself as log4j. Test for a class that slf4j doesn't provide. > Class.forName("org.apache.log4j.config.PropertySetter", true, cl); > return new Log4jLoggerProvider(); > } > {code} > And indeed I started receiving logging messages from Hibernate (via JBoss logging.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-94) JBoss Logging does not detect log4j 2.0

by Nicholas Williams (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-94?page=com.atlassian.jira.plug... ] Nicholas Williams commented on JBLOGGING-94: -------------------------------------------- Actually I see now, while browsing through Maven Central, that 3.1.3.GA was released in March. Why has JIRA not been updated to reflect this? What's the next version going to be? > JBoss Logging does not detect log4j 2.0 > --------------------------------------- > > Key: JBLOGGING-94 > URL: https://issues.jboss.org/browse/JBLOGGING-94 > Project: JBoss Logging > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jboss-logging-log4j > Affects Versions: 3.1.2.GA > Environment: Hibernate > Reporter: Henry Clout > Assignee: James Perkins > > The class org.jboss.logging.LoggerProviders checks for the presence of log4j using the code: > {code} > private static LoggerProvider tryLog4j(final ClassLoader cl) throws ClassNotFoundException { > Class.forName("org.apache.log4j.LogManager", true, cl); > // JBLOGGING-65 - slf4j can disguise itself as log4j. Test for a class that slf4j doesn't provide. > Class.forName("org.apache.log4j.Hierarchy", true, cl); > return new Log4jLoggerProvider(); > } > {code} > However, despite having the log4j-1.2-api-2.0.jar bridge included, this fails as the class org.apache.log4j.Hierarchy is not present in log4j 2.0. > I worked around this by forcing JBoss logging to use slf4j (which is then proxied to log4j) by setting the -Dorg.jboss.logging.provider=slf4j option. > As a proper fix, however, how about checking for a class that is included in log4j 1.2, 2.0 but not slf4j? org.apache.log4j.config.PropertySetter seems to tick the box. > I tested changing the afore mentioned method to: > {code} > private static LoggerProvider tryLog4j(final ClassLoader cl) throws ClassNotFoundException { > Class.forName("org.apache.log4j.LogManager", true, cl); > // JBLOGGING-65 - slf4j can disguise itself as log4j. Test for a class that slf4j doesn't provide. > Class.forName("org.apache.log4j.config.PropertySetter", true, cl); > return new Log4jLoggerProvider(); > } > {code} > And indeed I started receiving logging messages from Hibernate (via JBoss logging.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-94) JBoss Logging does not detect log4j 2.0

by Nicholas Williams (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-94?page=com.atlassian.jira.plug... ] Nicholas Williams edited comment on JBLOGGING-94 at 5/31/13 7:29 PM: --------------------------------------------------------------------- Can we get an update on this? I'd really like to see this fixed for 3.1.3. For that matter, what is the roadmap for 3.1.3? It has been almost a year since 3.1.2. It'd be nice to see this fixed and 3.1.3 released soon. Finally, I don't know much about JBoss logging (other than that it's used by Hibernate and thus my applications use it), but would it make sense to add support in 3.2.0 for Log4j 2? The API is greatly extended, and thus there might be improvements/streamlines that can be made to the JBoss Logging/Log4j integration if Log4j 2 is used. was (Author: beamerblvd): Can we get an update on this? I'd really like to see this fixed for 3.1.3. For that matter, what is the roadmap for 3.1.3? It has been almost a year since 3.1.2. It'd be nice to see this fixed and 3.1.3 released soon. > JBoss Logging does not detect log4j 2.0 > --------------------------------------- > > Key: JBLOGGING-94 > URL: https://issues.jboss.org/browse/JBLOGGING-94 > Project: JBoss Logging > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jboss-logging-log4j > Affects Versions: 3.1.2.GA > Environment: Hibernate > Reporter: Henry Clout > Assignee: James Perkins > > The class org.jboss.logging.LoggerProviders checks for the presence of log4j using the code: > {code} > private static LoggerProvider tryLog4j(final ClassLoader cl) throws ClassNotFoundException { > Class.forName("org.apache.log4j.LogManager", true, cl); > // JBLOGGING-65 - slf4j can disguise itself as log4j. Test for a class that slf4j doesn't provide. > Class.forName("org.apache.log4j.Hierarchy", true, cl); > return new Log4jLoggerProvider(); > } > {code} > However, despite having the log4j-1.2-api-2.0.jar bridge included, this fails as the class org.apache.log4j.Hierarchy is not present in log4j 2.0. > I worked around this by forcing JBoss logging to use slf4j (which is then proxied to log4j) by setting the -Dorg.jboss.logging.provider=slf4j option. > As a proper fix, however, how about checking for a class that is included in log4j 1.2, 2.0 but not slf4j? org.apache.log4j.config.PropertySetter seems to tick the box. > I tested changing the afore mentioned method to: > {code} > private static LoggerProvider tryLog4j(final ClassLoader cl) throws ClassNotFoundException { > Class.forName("org.apache.log4j.LogManager", true, cl); > // JBLOGGING-65 - slf4j can disguise itself as log4j. Test for a class that slf4j doesn't provide. > Class.forName("org.apache.log4j.config.PropertySetter", true, cl); > return new Log4jLoggerProvider(); > } > {code} > And indeed I started receiving logging messages from Hibernate (via JBoss logging.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-94) JBoss Logging does not detect log4j 2.0

by Nicholas Williams (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-94?page=com.atlassian.jira.plug... ] Nicholas Williams commented on JBLOGGING-94: -------------------------------------------- Can we get an update on this? I'd really like to see this fixed for 3.1.3. For that matter, what is the roadmap for 3.1.3? It has been almost a year since 3.1.2. It'd be nice to see this fixed and 3.1.3 released soon. > JBoss Logging does not detect log4j 2.0 > --------------------------------------- > > Key: JBLOGGING-94 > URL: https://issues.jboss.org/browse/JBLOGGING-94 > Project: JBoss Logging > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jboss-logging-log4j > Affects Versions: 3.1.2.GA > Environment: Hibernate > Reporter: Henry Clout > Assignee: James Perkins > > The class org.jboss.logging.LoggerProviders checks for the presence of log4j using the code: > {code} > private static LoggerProvider tryLog4j(final ClassLoader cl) throws ClassNotFoundException { > Class.forName("org.apache.log4j.LogManager", true, cl); > // JBLOGGING-65 - slf4j can disguise itself as log4j. Test for a class that slf4j doesn't provide. > Class.forName("org.apache.log4j.Hierarchy", true, cl); > return new Log4jLoggerProvider(); > } > {code} > However, despite having the log4j-1.2-api-2.0.jar bridge included, this fails as the class org.apache.log4j.Hierarchy is not present in log4j 2.0. > I worked around this by forcing JBoss logging to use slf4j (which is then proxied to log4j) by setting the -Dorg.jboss.logging.provider=slf4j option. > As a proper fix, however, how about checking for a class that is included in log4j 1.2, 2.0 but not slf4j? org.apache.log4j.config.PropertySetter seems to tick the box. > I tested changing the afore mentioned method to: > {code} > private static LoggerProvider tryLog4j(final ClassLoader cl) throws ClassNotFoundException { > Class.forName("org.apache.log4j.LogManager", true, cl); > // JBLOGGING-65 - slf4j can disguise itself as log4j. Test for a class that slf4j doesn't provide. > Class.forName("org.apache.log4j.config.PropertySetter", true, cl); > return new Log4jLoggerProvider(); > } > {code} > And indeed I started receiving logging messages from Hibernate (via JBoss logging.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-23) Debugging rules impossible

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-23?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on DROOLS-23: ----------------------------------------------- Kris Verlaenen <kverlaen(a)redhat.com> changed the Status of [bug 958381|https://bugzilla.redhat.com/show_bug.cgi?id=958381] from NEW to MODIFIED > Debugging rules impossible > -------------------------- > > Key: DROOLS-23 > URL: https://issues.jboss.org/browse/DROOLS-23 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Environment: Eclipse Juno, Windows 8 > Reporter: Marc Dzaebel > Assignee: Mark Proctor > > Create Drools Project, set breakpoint, debug as Drools Application > --> No debug -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-23) Debugging rules impossible

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-23?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on DROOLS-23: ----------------------------------------------- Kris Verlaenen <kverlaen(a)redhat.com> made a comment on [bug 958381|https://bugzilla.redhat.com/show_bug.cgi?id=958381] This works again in the latest Drools6 version of the Eclipse plugin > Debugging rules impossible > -------------------------- > > Key: DROOLS-23 > URL: https://issues.jboss.org/browse/DROOLS-23 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Environment: Eclipse Juno, Windows 8 > Reporter: Marc Dzaebel > Assignee: Mark Proctor > > Create Drools Project, set breakpoint, debug as Drools Application > --> No debug -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3676) drl cann't debuging in Eclipse IDE

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3676?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on JBRULES-3676: -------------------------------------------------- Kris Verlaenen <kverlaen(a)redhat.com> made a comment on [bug 958381|https://bugzilla.redhat.com/show_bug.cgi?id=958381] This works again in the latest Drools6 version of the Eclipse plugin > drl cann't debuging in Eclipse IDE > ---------------------------------- > > Key: JBRULES-3676 > URL: https://issues.jboss.org/browse/JBRULES-3676 > Project: JBRULES > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools-core (expert) > Affects Versions: 5.5.0.CR1 > Environment: Eclipse 4.2，JDK1.7，Drools5.5CR1 > Reporter: hongkun an > Assignee: Mark Proctor > > i follow url content > http://docs.jboss.org/drools/release/5.2.0.Final/drools-expert-docs/html/... > I want debug drl example（HelloWord）in eclipse ide，but，only debug java file，cann't debug drl，why？ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3676) drl cann't debuging in Eclipse IDE

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3676?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on JBRULES-3676: -------------------------------------------------- Kris Verlaenen <kverlaen(a)redhat.com> changed the Status of [bug 958381|https://bugzilla.redhat.com/show_bug.cgi?id=958381] from NEW to MODIFIED > drl cann't debuging in Eclipse IDE > ---------------------------------- > > Key: JBRULES-3676 > URL: https://issues.jboss.org/browse/JBRULES-3676 > Project: JBRULES > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools-core (expert) > Affects Versions: 5.5.0.CR1 > Environment: Eclipse 4.2，JDK1.7，Drools5.5CR1 > Reporter: hongkun an > Assignee: Mark Proctor > > i follow url content > http://docs.jboss.org/drools/release/5.2.0.Final/drools-expert-docs/html/... > I want debug drl example（HelloWord）in eclipse ide，but，only debug java file，cann't debug drl，why？ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-202) Set line number for newly created Methods

by John Doe (JIRA)

[ https://issues.jboss.org/browse/JASSIST-202?page=com.atlassian.jira.plugi... ] John Doe commented on JASSIST-202: ---------------------------------- If there is indeed a way to provide such metadata, this issue will automatically transform into a request for better documentation of the requested functionality :-) > Set line number for newly created Methods > ----------------------------------------- > > Key: JASSIST-202 > URL: https://issues.jboss.org/browse/JASSIST-202 > Project: Javassist > Issue Type: Feature Request > Affects Versions: 3.17.1-GA > Reporter: John Doe > Assignee: Shigeru Chiba > Priority: Minor > Labels: javassist > > As far as I could figure out, there is no way to provide line number information for newly created Methods. It would be nice if one could provide an start line at which the body starts, and Javassist would increment the line number at every line break in the body string. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2013