[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2891) Error logging on seam startup

[Pete Muir (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBSEAM-2891?page=comments#action_12408544 ] 
            
Pete Muir commented on JBSEAM-2891:
-----------------------------------

Please use your real name in JIRA

> Error logging on seam startup
> -----------------------------
>
>                 Key: JBSEAM-2891
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2891
>             Project: Seam
>          Issue Type: Feature Request
>    Affects Versions: 2.0.0.GA
>         Environment: Websphere
>            Reporter: Dupont Dupont
>
> SeamListener doesn't log when there's an error on startup.
> Seam just relies on appserver logging for that.
> On websphere, every error in a jvm is logged in one file SystemOut.log or SystemErr.log.
> This can be a problem for administrators when the same jvm host multiple seam enabled apps (from where did the log originated ?).
> It would be easier for WAS users if Seam logged the error with commons logging and propagated the exception (double logging, but at least we could configure log4j in each app to log to a different file).

-- 
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