thanks Paul, although why write another event-handler when an "exception" event- handler is already there for you to leverage? Couldn't I just style the existing exception handler and have it handle application defined and true exceptions (via results and the event object somehow...) when needed?
any thoughts? On Sep 12, 7:45 pm, "Paul Marcotte" <[EMAIL PROTECTED]> wrote: > Why not have an "error" event-handler that you can use with defined > results? For example, if a controller process in my app encounters an error > that is not a true exception, I'll add a "fail" or "error" result and then > in my event-handler results use: > > <results> > <result name="fail" do="error" /> > <result do="nexevent" /> > </results> > > In the error event handler, I might display a meaningful message to the > user, log the error, etc. > > Paul > > On Fri, Sep 12, 2008 at 11:14 AM, salomoko <[EMAIL PROTECTED]>wrote: > > > > > All, > > > how the heck do I intentionally add a custom message to my exception > > handler in MG. I'm trying to trigger the exception eventhandler from a > > result and add my own message... > > > :-( > > -- > Paul Marcotte > Fancy Bread - in the heart or in the head?http://www.fancybread.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "model-glue" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/model-glue?hl=en For more about Model-Glue, check http://www.model-glue.com . -~----------~----~----~----~------~----~------~--~---
