Hi,

How do I use exception handling for "call rules" shape in orchestration. The
scope for call rules shape is atomic hence I cannot use the exception handle
r
shape in orchestration for the call rules shape.

There is no exception handling in rule definitions itself. How do I handle
exception in rules then???

Thanks,
Sukesh.

[ Post a follow-up to this message ]

Sukesh,

I have not tried this, but can't you
place(nest)  your Atomic Scope inside a Long Running
Scope? The Long Running Scope should catch any errors
that occur in the Atomic scope.

Matt


"Sukesh Shetty" wrote:

> Hi,
>
> How do I use exception handling for "call rules" shape in orchestration. T
he
> scope for call rules shape is atomic hence I cannot use the exception hand
ler
> shape in orchestration for the call rules shape.
>
> There is no exception handling in rule definitions itself. How do I handle
> exception in rules then???
>
> Thanks,
> Sukesh.

[ Post a follow-up to this message ]

The approach that MM suggests does not work. I tried below, and errors in th
e
Rules Engine would never be trapped by the orchestration exception handler. 
I
attempted to trap in the outer scope the specific eception type by adding th
e
Microsoft.RulesEngine refference as well as the System.Exception type. In
either case the error from the inner atomic CallRules scope would always sho
w
up in the event loag and bypass my handler.

Does anyone know how to trap these rule engine exceptions?

trackley

"Matt Meleski" wrote:
[vbcol=seagreen]
> Sukesh,
>
> I have not tried this, but can't you
> place(nest)  your Atomic Scope inside a Long Running
> Scope? The Long Running Scope should catch any errors
> that occur in the Atomic scope.
>
> Matt
>
>
> "Sukesh Shetty" wrote:
> 

[ Post a follow-up to this message ]