[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-2232) Full review of Seam's log levels
[
https://jira.jboss.org/jira/browse/JBSEAM-2232?page=com.atlassian.jira.pl...
]
Norman Richards closed JBSEAM-2232.
-----------------------------------
Resolution: Done
I've taken a second pass at this with an eye on keeping everything INFO or higher as
consistent and useful as possible. There is still a lot of debug level logging that would
probably be better as trace, but overall it looks like a healthy place to be.
Full review of Seam's log levels
--------------------------------
Key: JBSEAM-2232
URL: https://jira.jboss.org/jira/browse/JBSEAM-2232
Project: Seam
Issue Type: Task
Components: Core
Reporter: Christian Bauer
Assignee: Norman Richards
Priority: Blocker
Fix For: 2.1.2
Debug logging with Seam 2.x is completely useless. The most critical information in the
debug log is the instantiation and lookup of components, however, if you enable DEBUG for
org.jboss.seam.Component, you get thousands of these:
12:26:06,282 DEBUG [Component] instantiating Seam component: org.jboss.seam.core.events
12:26:06,282 DEBUG [Component] initializing new instance of: org.jboss.seam.core.events
12:26:06,282 DEBUG [Component] done initializing: org.jboss.seam.core.events
We need to exclude the event firing from debug logging, even if we hardcode it. And, are
these events really useful? I have no idea why and when I'd want to listen to
"context variable initialized" events.
--
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