[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2232) Reduce debug log level for events

Pete Muir (JIRA) jira-events at lists.jboss.org
Sat Aug 30 08:48:38 EDT 2008

     [ https://jira.jboss.org/jira/browse/JBSEAM-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir updated JBSEAM-2232:

    Fix Version/s: 2.1.1.CR1
                       (was: 2.1.0.CR1)

> Reduce debug log level for events
> ---------------------------------
>                 Key: JBSEAM-2232
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-2232
>             Project: Seam
>          Issue Type: Task
>          Components: Core
>            Reporter: Christian Bauer
>            Priority: Critical
>             Fix For: 2.1.1.CR1
> 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


More information about the seam-issues mailing list