[
https://issues.apache.org/jira/browse/OFBIZ-11040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16845607#comment-16845607 ]
Nicolas Malin commented on OFBIZ-11040:
---------------------------------------
{quote}Hè Leila are you really too shy to not provide it yourself, or do you prefer to not be too much involved in contributions? {quote}
:) I destack from nereide pool correction
https://labs.nereide.fr/10031/Communautaire/issues and most of them a realize by her
{quote}BTW should this not be considered a bug? What could be the reasons it was not implemented before, any ideas?{quote}
I hesitated, missing functionnality or bug process, if you think it's more a bug I can backport it
[~mthl] I corrected the patch [^OFBIZ-11040.patch] with your remarks
> 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, 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)
Locked
