@Thomas,
That is exactly what I mean. Have a default "language" exception
handling mechanism, by which all unmapped exceptions would be converted to
"ProcessRuntimeException" and will go to the "Fault" with type,
let's say,
UnknownProcessExceptionFault. And have an option to turn this behaviour off,
if needed, of course.
And have an option to map other exceptions to Fault nodes as simple as:
<util:map id="processExceptions">
<entry key="SomeBusinessException"
value="SomeBusinessProcessExceptionFault"/>
<entry key="SomeOtherBusinessException"
value="SomeOtherBusinessProcessExceptionFault"/>
<entry key="SomeCoreJavaException"
value="SomeCoreJavaExceptionFault"/>
... ... ...
</util:map>
( this is a Spring map, but you can look at it as a regular Java Map<K,
V> )
/Anatoly
--
View this message in context:
http://n3.nabble.com/How-to-do-Exception-Handling-tp689387p714053.html
Sent from the Drools - User mailing list archive at
Nabble.com.