[
https://jira.jboss.org/jira/browse/JBSEAM-2232?page=com.atlassian.jira.pl...
]
Pete Muir commented on JBSEAM-2232:
-----------------------------------
On 15 Apr 2009, at 12:46, Dimitris Andreadis wrote:
Pete Muir wrote:
Hi Dimitris,
Not quite sure how you would do it I'm afraid - the obvious way would be to allow the
application to bundle it's own log4j.xml file which overrides the AS one, but that
doesn't seem to work in the current code base. Want me to file a feature request?
But I do believe Seam is using log levels consistently with JBoss AS.
AFAICT, Seam is very noisy. Most of the info I'm trying to avoid should be logged at
DEBUG level.
Right, but I need to know *what* you want to avoid to actually do anything about it - I
think this is quite subjective - one person's useful info is another noise ;-)
To summarize:
* version info is fine
* the namespace lines are probably ok for you (but I don't like them so will DEBUG
them)
* component discovery and startup should go to DEBUG (both for Seam and EJB)
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: Pete Muir
Priority: Blocker
Fix For: 2.1.2.GA
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