I agree. This was a huge problem for me. I lost many hours because MyFaces was logging errors that I couldn't find. For what it's worth, if you have log4j.jar in WEB-INF/lib and log4j.properties in WEB-INF/classes with these values, you'll see the errors.
log4j.rootLogger=WARN, stdout
log4j.logger.org.apache.myfaces = INFO
log4j.logger.javax.faces = INFO
#***************************************
# Appender "stdout"
#***************************************
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%d{ISO8601} %-5p %c - %m%n
Adam Brod
Product Development Team
| "Iordanov, Borislav
\(GIC\)" <[EMAIL PROTECTED]>
07/17/2006 01:22 PM
|
|
Hi guys,
I’m sure there is a way to configure logging so that this doesn’t happen, but by default I notice tons of swallowed exceptions in MyFaces. The resulting behavior obviously is that something doesn’t work and there’s no indication why. Regardless of logging the error and of my not having spent a few hours figuring out how to configure MyFaces logs, I think it is unacceptable behavior for the application to continue to run after a fatal error. An example of a fatal error is an NPE thrown from a property setter during the “update model values” request processing phase. Such errors should be propagated to the servlet container so that I can eventually see a stack trace on my browser – very convenient during development.
Regards,
Bolerio
Disclaimer: This electronic mail and any attachments are confidential and may be privileged. If you are not the intended recipient, please notify the sender immediately by replying to this email, and destroy all copies of this email and any attachments. Thank you.
