If you need to catch a wide range of Exceptions in an error page, i suggest you use a generic error page. The error page has access to the Exception Object and can then include other JSP that show specific errors.
As for informations in logs file, Exceptions thrown during process of JSF outputed using common-logging. Most people i think configure common-logging to output using log4j, which itself is easy to configure. to get up to debug level, filter on classes, have Some specific error messages sent by email, etc. Last but not least, a common beginner mistake with JSF is to forget to use <h:message/> in pages, which display effective components errors occured during last request. SiSi'mon a écrit : > I am having extremely severe problems with MyFaces right now. The biggest > problem is that when MyFaces breaks (throws an exception), you never know > about it sometimes. There is no information in the log files etc. > > What I would like to do is to somehow print out a stack trace in the browser > window if tomcat encounters any kind of exception thrown by > "org.apache.myfaces.*" but I do not know how to use wildcards in the > web.xml file for error pages. > > It seems like the error-page tag needs a fully qualified exception class and > the following will not work. > any ideas? > > <error-page> > <exception-type>org.apache.myfaces.*</exception-type> > <location>/web/error/Faces.jsf</location> > </error-page> > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
