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

[Vladimir Kovalyuk (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBSEAM-2232?page=comments#action_12395965 ] 
            
Vladimir Kovalyuk commented on JBSEAM-2232:
-------------------------------------------

I have to skip the following messages:

1. related to Events component (too verbose :) )
2. seam component not found (before creating, a lot of unsuccessful attempts to concat some prefixes like org.jboss.seam.core.actions etc)
3. instantiating seam component
4. initializing new instance of
5. done initializing

I'll be fine with fine-prepared exception when seam can't create component.


> Reduce debug log level for events
> ---------------------------------
>
>                 Key: JBSEAM-2232
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2232
>             Project: JBoss Seam
>          Issue Type: Task
>          Components: Core
>            Reporter: Christian Bauer
>            Priority: Critical
>             Fix For: 2.1.0.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: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira