You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by Rupert Howell <ru...@provolve.com> on 2014/01/06 14:48:15 UTC
Disabling ECAs from custom code.
Has anybody got any good ideas for a way to disable ECAS from triggering
without commenting them out from the core code?
Like overriding the service definitions in hot-deploy it would be handy to
be able to clear any ECAs that are listening on a particular service call
or entity update from within the custom code.
Any thoughts?
--
Rupert Howell
Provolve Ltd
Front Office, Deale House, 16 Lavant Street, Petersfield, GU32 3EW, UK
t: 01730 267868 / m: 079 0968 5308
e: ruperthowell@provolve.com
w: http://www.provolve.com
Re: Disabling ECAs from custom code.
Posted by Rupert Howell <ru...@provolve.com>.
Hey Nicolas - long time no speak.
Not a blanket switch off - a targetted one.
For Example I dont want :
<eca service="changeOrderItemStatus" event="commit">
<condition field-name="statusId" operator="equals"
value="ITEM_APPROVED"/>
<action service="checkDigitalItemFulfillment" mode="sync"/>
</eca>
to run, but I want all the others.
On 6 January 2014 14:09, Nicolas Malin <ma...@librenberry.net>wrote:
> Hello Rupert,
>
> You need to switch on delegator name default-no-eca like this :
> Delegator delegator-no-eca = GenericDelegator.
> getGenericDelegator("default-no-eca");
>
> Nicolas
>
> Le 06/01/2014 14:48, Rupert Howell a écrit :
>
>> Has anybody got any good ideas for a way to disable ECAS from triggering
>> without commenting them out from the core code?
>>
>> Like overriding the service definitions in hot-deploy it would be handy to
>> be able to clear any ECAs that are listening on a particular service call
>> or entity update from within the custom code.
>>
>> Any thoughts?
>>
>>
>
> --
> Nicolas MALIN
> Consultant
> Tél : 06.17.66.40.06
> Site projet : http://www.neogia.org/
> -------
> Société LibrenBerry
> Tél : 02.48.02.56.12
> Site : http://www.librenberry.net/
>
>
--
Rupert Howell
Provolve Ltd
Front Office, Deale House, 16 Lavant Street, Petersfield, GU32 3EW, UK
t: 01730 267868 / m: 079 0968 5308
e: ruperthowell@provolve.com
w: http://www.provolve.com
Re: Disabling ECAs from custom code.
Posted by Nicolas Malin <ma...@librenberry.net>.
Hello Rupert,
You need to switch on delegator name default-no-eca like this :
Delegator delegator-no-eca =
GenericDelegator.getGenericDelegator("default-no-eca");
Nicolas
Le 06/01/2014 14:48, Rupert Howell a écrit :
> Has anybody got any good ideas for a way to disable ECAS from triggering
> without commenting them out from the core code?
>
> Like overriding the service definitions in hot-deploy it would be handy to
> be able to clear any ECAs that are listening on a particular service call
> or entity update from within the custom code.
>
> Any thoughts?
>
--
Nicolas MALIN
Consultant
Tél : 06.17.66.40.06
Site projet : http://www.neogia.org/
-------
Société LibrenBerry
Tél : 02.48.02.56.12
Site : http://www.librenberry.net/
Re: Disabling ECAs from custom code.
Posted by Ruth Hoffman <rh...@aesolves.com>.
Hi Rupert:
This would indeed be a really nice feature.
Wish I knew how to do it.
Regards,
Ruth Hoffman
http://www.ruthhoffman.com
rhoffman@aesolves.com
On 1/6/14 8:48 AM, Rupert Howell wrote:
> Has anybody got any good ideas for a way to disable ECAS from triggering
> without commenting them out from the core code?
>
> Like overriding the service definitions in hot-deploy it would be handy to
> be able to clear any ECAs that are listening on a particular service call
> or entity update from within the custom code.
>
> Any thoughts?
>