You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Nicolas Malin (JIRA)" <ji...@apache.org> on 2019/05/24 15:20:00 UTC
[jira] [Closed] (OFBIZ-11040) Manage EECAs on delegator.removeBy
[ https://issues.apache.org/jira/browse/OFBIZ-11040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas Malin closed OFBIZ-11040.
---------------------------------
Resolution: Fixed
Commited at :
* trunk: r1859887
* 18.12: r1859888
* 17.12: r1859889 (with partiel revert, bad forating, on r1859890)
Thanks all for the sharing
> Manage EECAs on delegator.removeBy
> ----------------------------------
>
> Key: OFBIZ-11040
> URL: https://issues.apache.org/jira/browse/OFBIZ-11040
> Project: OFBiz
> Issue Type: Bug
> Components: framework
> Affects Versions: Trunk
> Reporter: Nicolas Malin
> Assignee: Nicolas Malin
> Priority: Minor
> Attachments: OFBIZ-11040.patch, OFBIZ-11040.patch
>
>
> Currently, when you delete some entities through removeByAnd or removeByCondition, eeca aren't enable and the remove is quite as regard implemented rules.
> With
> {code:java}
> <eca entity="GoodIndentification" operation="create-store-remove" event="return">
> <action service="indexProduct" mode="sync"/>
> </eca>
> {code}
> And
> {code:java}
> delegator.removeByAnd('GoodIdentification', [productId: 'WG-1111'])
> {code}
> The service indexProduct wasn't call for the productId WG-1111
> To solve this situation, the idea would be delegator.removeValue for each element to delete when an eeca is present otherwise call the standard helper.removeByCondition.
> This patch [^OFBIZ-11040.patch] provided by [~mleila]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)