ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Malin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OFBIZ-11040) Manage EECAs on delegator.removeBy
Date Fri, 17 May 2019 14:22:00 GMT

     [ https://issues.apache.org/jira/browse/OFBIZ-11040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Nicolas Malin updated OFBIZ-11040:
----------------------------------
    Description: 
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]

  was:
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.

 

 


> 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
>            Priority: Minor
>         Attachments: 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)

Mime
View raw message