Can this be for 1.2? Is there an urgent reason for it to be in 1.1? My vision of 1.2 is to release it fairly soon after 1.1 with a few key enhancements so this feature would make it out soon anyways.For 1.1, it makes sense to me that we declare a couple of specific exceptions that can then be caught and managed using the exception mapping technology.
> I came across this issue while looking at the different ways
> LookupDispatchAction and DispatchAction handle errors.
>
> Would it be backwards incompatible to change what the actions do when they
> encounter an error?
>
I suspect that the current behavior w.r.t. errors is so unusable that
anyone concerned about it has already subclassed the thing anyway.
+1 for defining appropriate exceptions that can be thrown for this use
case.
> Thanks,
> Dave
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
