1:16 p.m.
JDK logging levels don't match our standard levels
--------------------------------------------------
Key: JBAS-4907
URL: http://jira.jboss.com/jira/browse/JBAS-4907
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Logging
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: David Lloyd
Assigned To: Scott M Stark
Fix For: JBossAS-5.0.0.Beta3
The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels. It
should use levels that reflect the existing standard for JBossAS, since this is what users
are used to, and to simplify the parsing of the logging XML config.
Attached it a patch that does so.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:18 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-4907) JDK logging levels don't match our standard levels
[ http://jira.jboss.com/jira/browse/JBAS-4907?page=all ]
David Lloyd updated JBAS-4907:
------------------------------
Attachment: JBAS-4907.patch
JDK logging levels don't match our standard levels
--------------------------------------------------
Key: JBAS-4907
URL: http://jira.jboss.com/jira/browse/JBAS-4907
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Logging
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: David Lloyd
Assigned To: Scott M Stark
Fix For: JBossAS-5.0.0.Beta3
Attachments: JBAS-4907.patch
The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels. It
should use levels that reflect the existing standard for JBossAS, since this is what users
are used to, and to simplify the parsing of the logging XML config.
Attached it a patch that does so.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:04 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-4907) JDK logging levels don't match our standard levels
[ http://jira.jboss.com/jira/browse/JBAS-4907?page=comments#action_12384202 ]
David Lloyd commented on JBAS-4907:
-----------------------------------
Forgot to add - if you want me to NOT apply this, say so in the next day or two.
Otherwise I'll do it.
JDK logging levels don't match our standard levels
--------------------------------------------------
Key: JBAS-4907
URL: http://jira.jboss.com/jira/browse/JBAS-4907
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Logging
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: David Lloyd
Assigned To: Scott M Stark
Fix For: JBossAS-5.0.0.Beta3
Attachments: JBAS-4907.patch
The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels. It
should use levels that reflect the existing standard for JBossAS, since this is what users
are used to, and to simplify the parsing of the logging XML config.
Attached it a patch that does so.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:10 p.m.
New subject: [JBoss JIRA] Moved: (JBCOMMON-39) JDK logging levels don't match our standard levels
[ http://jira.jboss.com/jira/browse/JBCOMMON-39?page=all ]
Scott M Stark moved JBAS-4907 to JBCOMMON-39:
---------------------------------------------
Project: JBoss Common (was: JBoss Application Server)
Key: JBCOMMON-39 (was: JBAS-4907)
Component/s: common-logging-jdk
(was: Logging)
Fix Version/s: 2.2.3.GA
(was: JBossAS-5.0.0.Beta3)
Affects Version/s: 2.2.2.GA
(was: JBossAS-5.0.0.Beta2)
JDK logging levels don't match our standard levels
--------------------------------------------------
Key: JBCOMMON-39
URL: http://jira.jboss.com/jira/browse/JBCOMMON-39
Project: JBoss Common
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: common-logging-jdk
Affects Versions: 2.2.2.GA
Reporter: David Lloyd
Assigned To: Scott M Stark
Fix For: 2.2.3.GA
Attachments: JBAS-4907.patch
The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels. It
should use levels that reflect the existing standard for JBossAS, since this is what users
are used to, and to simplify the parsing of the logging XML config.
Attached it a patch that does so.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:10 p.m.
New subject: [JBoss JIRA] Assigned: (JBCOMMON-39) JDK logging levels don't match our standard levels
[ http://jira.jboss.com/jira/browse/JBCOMMON-39?page=all ]
Scott M Stark reassigned JBCOMMON-39:
-------------------------------------
Assignee: David Lloyd (was: Scott M Stark)
JDK logging levels don't match our standard levels
--------------------------------------------------
Key: JBCOMMON-39
URL: http://jira.jboss.com/jira/browse/JBCOMMON-39
Project: JBoss Common
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: common-logging-jdk
Affects Versions: 2.2.2.GA
Reporter: David Lloyd
Assigned To: David Lloyd
Fix For: 2.2.3.GA
Attachments: JBAS-4907.patch
The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels. It
should use levels that reflect the existing standard for JBossAS, since this is what users
are used to, and to simplify the parsing of the logging XML config.
Attached it a patch that does so.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:55 a.m.
New subject: [JBoss JIRA] Commented: (JBCOMMON-39) JDK logging levels don't match our standard levels
[ http://jira.jboss.com/jira/browse/JBCOMMON-39?page=comments#action_12384266 ]
Dimitris Andreadis commented on JBCOMMON-39:
--------------------------------------------
Can you explain again what the problem is? Is there a forum thread discussing it?
JDK logging levels don't match our standard levels
--------------------------------------------------
Key: JBCOMMON-39
URL: http://jira.jboss.com/jira/browse/JBCOMMON-39
Project: JBoss Common
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: common-logging-jdk
Affects Versions: 2.2.2.GA
Reporter: David Lloyd
Assigned To: David Lloyd
Fix For: 2.2.3.GA
Attachments: JBAS-4907.patch
The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels. It
should use levels that reflect the existing standard for JBossAS, since this is what users
are used to, and to simplify the parsing of the logging XML config.
Attached it a patch that does so.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:16 a.m.
New subject: [JBoss JIRA] Commented: (JBCOMMON-39) JDK logging levels don't match our standard levels
[ http://jira.jboss.com/jira/browse/JBCOMMON-39?page=comments#action_12384324 ]
David Lloyd commented on JBCOMMON-39:
-------------------------------------
The problem is that if you use the JDK14LoggerPlugin, and you log a message at, say,
TRACE, it shows up as FINER in the log. And the DOMConfigurator for the JDK plugin has to
map the "old" log4j names to the (roughly) equivalent JUL name. I propose that
we just create a subclass of java.util.logging.Level, and an instance for each of the log
levels that WE use, e.g. TRACE, DEBUG, etc. Then not only will the old, familiar levels
be printed in the log, but then JUL will parse the log level names for us, so we don't
need to map them.
No forum thread because honestly I don't know what forum is relevant for this
project.
JDK logging levels don't match our standard levels
--------------------------------------------------
Key: JBCOMMON-39
URL: http://jira.jboss.com/jira/browse/JBCOMMON-39
Project: JBoss Common
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: common-logging-jdk
Affects Versions: 2.2.2.GA
Reporter: David Lloyd
Assigned To: David Lloyd
Fix For: 2.2.3.GA
Attachments: JBAS-4907.patch
The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels. It
should use levels that reflect the existing standard for JBossAS, since this is what users
are used to, and to simplify the parsing of the logging XML config.
Attached it a patch that does so.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:22 a.m.
New subject: [JBoss JIRA] Updated: (JBCOMMON-39) JDK logging levels don't match our standard levels
[ http://jira.jboss.com/jira/browse/JBCOMMON-39?page=all ]
David Lloyd updated JBCOMMON-39:
--------------------------------
Attachment: JBCOMMON-39.patch
Updated patch.
JDK logging levels don't match our standard levels
--------------------------------------------------
Key: JBCOMMON-39
URL: http://jira.jboss.com/jira/browse/JBCOMMON-39
Project: JBoss Common
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: common-logging-jdk
Affects Versions: 2.2.2.GA
Reporter: David Lloyd
Assigned To: David Lloyd
Fix For: 2.2.3.GA
Attachments: JBCOMMON-39.patch
The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels. It
should use levels that reflect the existing standard for JBossAS, since this is what users
are used to, and to simplify the parsing of the logging XML config.
Attached it a patch that does so.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:22 a.m.
New subject: [JBoss JIRA] Updated: (JBCOMMON-39) JDK logging levels don't match our standard levels
[ http://jira.jboss.com/jira/browse/JBCOMMON-39?page=all ]
David Lloyd updated JBCOMMON-39:
--------------------------------
Attachment: (was: JBAS-4907.patch)
JDK logging levels don't match our standard levels
--------------------------------------------------
Key: JBCOMMON-39
URL: http://jira.jboss.com/jira/browse/JBCOMMON-39
Project: JBoss Common
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: common-logging-jdk
Affects Versions: 2.2.2.GA
Reporter: David Lloyd
Assigned To: David Lloyd
Fix For: 2.2.3.GA
Attachments: JBCOMMON-39.patch
The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels. It
should use levels that reflect the existing standard for JBossAS, since this is what users
are used to, and to simplify the parsing of the logging XML config.
Attached it a patch that does so.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:53 a.m.
New subject: [JBoss JIRA] Closed: (JBCOMMON-39) JDK logging levels don't match our standard levels
[ http://jira.jboss.com/jira/browse/JBCOMMON-39?page=all ]
David Lloyd closed JBCOMMON-39.
-------------------------------
Resolution: Done
Committed in rev. 2661 of trunk.
JDK logging levels don't match our standard levels
--------------------------------------------------
Key: JBCOMMON-39
URL: http://jira.jboss.com/jira/browse/JBCOMMON-39
Project: JBoss Common
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: common-logging-jdk
Affects Versions: 2.2.2.GA
Reporter: David Lloyd
Assigned To: David Lloyd
Fix For: 2.2.3.GA
Attachments: JBCOMMON-39.patch
The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels. It
should use levels that reflect the existing standard for JBossAS, since this is what users
are used to, and to simplify the parsing of the logging XML config.
Attached it a patch that does so.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6548
days inactive
6553
days old
9 comments
3 participants
participants (3)
-
David Lloyd (JIRA) -
Dimitris Andreadis (JIRA)
-
Scott M Stark (JIRA)