On 6/4/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Rahul, some times ago Craig told me that the onException is the correct way to catch and manage this exception: http://www.mail-archive.com/user@shale.apache.org/msg01111.html
<snip/> The code will throw an IllegalStateException (as you've posted in the top post in this thread), but won't result in an onException callback in this scenario (I'm sort of interested in knowing what the scenarios are -- other than developer error). Obviously, I can't speak for Craig or anyone else, but I think his response in this thread overrides that one by virtue of being more recent. -Rahul
Mario -----Original Message----- From: Rahul Akolkar [mailto:[EMAIL PROTECTED] Sent: 30 maggio 2007 18.20 To: user@shale.apache.org Subject: Re: No onException called On 5/30/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hi, I have configure a my dialogContextListener but If I receive the > onEntry method call back (for example) but I don't receive any > onException in case I call a transition not setted in dialog config > file. In the log I found: > <snip/> The DialogContextListeners are notified on certain type of application errors such as: * Exception while executing the method binding expression associated with an action state * Exception while trying to instantiate dialog data but are not notified on exceptions that have to do with either the completeness of the dialog's "model" (such as the case here, an unknown transition) or dialog lifecycle error conditions. I suspect it might have to do with the latter being perceived as fatal. Craig will know. -Rahul
