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/17 14:02:00 UTC
[jira] [Created] (OFBIZ-11040) Manage EECAs on delegator.removeBy
Nicolas Malin created OFBIZ-11040:
-------------------------------------
Summary: Manage EECAs on delegator.removeBy
Key: OFBIZ-11040
URL: https://issues.apache.org/jira/browse/OFBIZ-11040
Project: OFBiz
Issue Type: Improvement
Components: framework
Affects Versions: Trunk
Reporter: Nicolas Malin
Assignee: Nicolas Malin
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 is call removeValue for each element hen an eeca is present otherwise call the standard helper.removeByCondition.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)