Message handlers and error handling
Tom Zeller
tzeller at dragonacea.biz
Tue Apr 15 11:37:59 EDT 2014
>> event = EventResolver.lookup(String eventID)
>
> No. I don't have an event at all, just a generic MessageHandler exception.
Right, should have been
event = EventResolver.lookup(Exception)
but that is just another abstraction to a map. Must have been the lunar eclipse.
>>Maybe inject a map instead of a String ?
>>
>> handler.setExceptionToEventIDMap(Map<Exception, String>
>>exceptionToEventIDMap)
>
> We don't have anything but one exception type in the handlers, so there's
> nothing to map. And I don't really want to create a big exception
> hierarchy either.
Okay.
> I'm really suggesting just dumping that capability and treating
> exceptions from Actions as a rare, fatal occurrence and let it be handled
> by an MVC-mapped exception handler, same as if we have a Spring exception
> like a bad web flow definition.
+1
More information about the dev
mailing list