This content has been marked as final.
Show 4 replies
-
1. Re: error handling on actionListener and tree.nodeSelectListener
ilya_shaikovsky Jul 28, 2010 9:47 AM (in response to flyinfish)if the messages should be reported to end-user - maybe it's more convenient to use faces messages?
B.t.w. this is not proper space for usage questons. Moving thread to RichFaces space.
-
2. Re: error handling on actionListener and tree.nodeSelectListener
flyinfish Jul 29, 2010 1:39 AM (in response to ilya_shaikovsky)i am talking fatal-error-handling.
i do not want to try-catch in every action- or listener method but havig a generic mechanism which catches and handles exceptions and showing an "oops-page" to the user.
-
3. Re: error handling on actionListener and tree.nodeSelectListener
ilya_shaikovsky Jul 29, 2010 3:23 AM (in response to flyinfish)1 of 1 people found this helpfulhttp://articles.alyssar.nl/2008/03/05/jsf-exception-handling/
http://santhoshjohn78.blogspot.com/2009/02/catch-all-exception-page-for-jsf-web.html
-
4. Re: error handling on actionListener and tree.nodeSelectListener
flyinfish Jul 30, 2010 8:57 AM (in response to ilya_shaikovsky)the whole point is:
if i use <rich:menuItem/h:commandLink action=".."/>, default ActionListener and javax.faces.context.ExceptionHandler are triggered
default-behaviour is fine for me, there is no need to do anything further
- if i use <rich:menuItem/h:commandLink actionListener=".."/> or tree.nodeSelectListener ExceptionHandler and com.sun.faces.application.ActionListenerImpl are not triggered and the fatal error is hidden from user