Or should I be using custom actions to accomplish this sort of decoupling? But if I throw a ModelException for some processing error, how does the statemachine handle this? Can I route all ModelExceptions to a particular error state?
Thanks, Jon On 3/26/06, Jon Brule <[EMAIL PROTECTED]> wrote: > > Good Morning, > > I am attempting to decouple state action code from the state machine's > execution by using the SCXMLListener interface in non-inner classes (like > StopWatch example)... Now suppose within a listener implementation I > encounter a checked exception... Since the SCXMLListener interface does not > account for checked exceptions, how best can I communicate this back to the > state machine execution to alter the execution path, say to perform an > automatic transition to an error state? > > > -- > Jon Brule > tricolorcat-at-gmail.com -- Jon Brule tricolorcat-at-gmail.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
