[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1835) Improve debug logging
Pete Muir (JIRA)
jira-events at lists.jboss.org
Thu Aug 23 08:30:18 EDT 2007
[ http://jira.jboss.com/jira/browse/JBSEAM-1835?page=comments#action_12373492 ]
Pete Muir commented on JBSEAM-1835:
-----------------------------------
Can we also consider reducing the amount of stuff we spew out at INFO level and putting it at DEBUG (as that is when it is *actually* useful):
* Which jars are being scanned
* Which namespaces are available (why is this even useful at all?)
* That seam.properties has been read (it doesn't even say *which* jar its been read from).
> Improve debug logging
> ---------------------
>
> Key: JBSEAM-1835
> URL: http://jira.jboss.com/jira/browse/JBSEAM-1835
> Project: JBoss Seam
> Issue Type: Task
> Reporter: Christian Bauer
> Priority: Blocker
>
> This should be logged at TRACE level:
> (http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG [Events] Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.core.manager
> (http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG [Component] instantiating Seam component: org.jboss.seam.core.events
> (http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG [Component] initializing new instance of: org.jboss.seam.core.events
> (http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG [Component] done initializing: org.jboss.seam.core.events
> I have thousands of lines of these making DEBUG completely useless. I still want to see all other instantiations etc. from Component though.
--
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
More information about the seam-issues
mailing list