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 |
- swalled exception Iordanov, Borislav \(GIC\)
- Re: swalled exception Adam Brod
- RE: swalled exception Iordanov, Borislav \(GIC\)
- tree2: update treeModel on the server Jiang, Jane \(NIH/NCI\) [C]
- Re: tree2: update treeModel on th... Andrew Robinson
- RE: tree2: update treeModel o... Jiang, Jane \(NIH/NCI\) [C]
- Re: tree2: update treeMo... Andrew Robinson
- Re: tree2: update treeModel on th... Mr Arvind Pandey
- Re: swalled exception Mike Kienenberger
- RE: swalled exception L Frohman
- Re: swalled exception Mike Kienenberger