Quantcast

Seca run-on-error help

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Seca run-on-error help

Marlowe Inoferio
Hi,

Need help on understanding the seca run-on-error ="true" or = "false".

Does it mean if i define an item in the seca with run-on-error="true" the seca definition will still run regardless if it encounters an error during execution ?

Example:

    <eca service="changeOrderStatus" event="commit" run-on-error="false">
        <condition field-name="statusId" operator="equals" value="ORDER_CANCELLED"/>
        <action service="releaseOrderPayments" mode="sync"/>
    </eca>


Or will the above definition only run when the changeOrderStatus returns an error during execution and then run the releaseOrderPayments  service ?

Need help

Thanks

Marlowe



     
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Seca run-on-error help

Chirag Manocha
Hello Marlowe
Comments Inline

On Fri, Jun 20, 2008 at 7:22 AM, Marlowe Inoferio <[hidden email]>
wrote:

> Hi,
>
> Need help on understanding the seca run-on-error ="true" or = "false".
>
> Does it mean if i define an item in the seca with run-on-error="true" the
> seca definition will still run regardless if it encounters an error during
> execution ?
>
> Example:
>
>    <eca service="changeOrderStatus" event="commit" run-on-error="false">
>        <condition field-name="statusId" operator="equals"
> value="ORDER_CANCELLED"/>
>        <action service="releaseOrderPayments" mode="sync"/>
>    </eca>


In the above  example run-on-error is false
So when the service("changeOrderStatus") successfully runs and the condition
satisfies then only this action will be performed.
This action will not be performed when service("changeOrderStatus") return
error.


>
> Or will the above definition only run when the changeOrderStatus returns an
> error during execution and then run the releaseOrderPayments  service ?
>
> Need help
>
> Thanks
>
> Marlowe
>
>
>
>


Here is the example of run-on-error="true"

    <eca service="finAccountWithdraw" event="return" run-on-error="true">
        <condition field-name="productStoreId" operator="is-not-empty"/>
        <action service="finAccountReplenish" mode="async" persist="true"
run-as-user="system"/>
    </eca>

When the service(finAccountWithdraw) return error or success and the
conditon of productStoreId, satisfies then this action will be performed.
Notice when the run-on-error is true, action will be performed every time
when this service(finAccountWithdraw) will called and condition satisfies.



--
Regards
Chirag Manocha
Hotwax Media Inc.
(M) +91-982-631-9099
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Seca run-on-error help

Marlowe Inoferio
In reply to this post by Marlowe Inoferio
Ok now i understand.

Thanks  Chirag


----- Original Message ----
From: Chirag Manocha <[hidden email]>
To: [hidden email]
Sent: Friday, June 20, 2008 1:42:40 PM
Subject: Re: Seca run-on-error help

Hello Marlowe
Comments Inline

On Fri, Jun 20, 2008 at 7:22 AM, Marlowe Inoferio <[hidden email]>
wrote:

> Hi,
>
> Need help on understanding the seca run-on-error ="true" or = "false".
>
> Does it mean if i define an item in the seca with run-on-error="true" the
> seca definition will still run regardless if it encounters an error during
> execution ?
>
> Example:
>
>    <eca service="changeOrderStatus" event="commit" run-on-error="false">
>        <condition field-name="statusId" operator="equals"
> value="ORDER_CANCELLED"/>
>        <action service="releaseOrderPayments" mode="sync"/>
>    </eca>


In the above  example run-on-error is false
So when the service("changeOrderStatus") successfully runs and the condition
satisfies then only this action will be performed.
This action will not be performed when service("changeOrderStatus") return
error.


>
> Or will the above definition only run when the changeOrderStatus returns an
> error during execution and then run the releaseOrderPayments  service ?
>
> Need help
>
> Thanks
>
> Marlowe
>
>
>
>


Here is the example of run-on-error="true"

    <eca service="finAccountWithdraw" event="return" run-on-error="true">
        <condition field-name="productStoreId" operator="is-not-empty"/>
        <action service="finAccountReplenish" mode="async" persist="true"
run-as-user="system"/>
    </eca>

When the service(finAccountWithdraw) return error or success and the
conditon of productStoreId, satisfies then this action will be performed.
Notice when the run-on-error is true, action will be performed every time
when this service(finAccountWithdraw) will called and condition satisfies.



--
Regards
Chirag Manocha
Hotwax Media Inc.
(M) +91-982-631-9099



     
Loading...