You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Divesh Dutta (JIRA)" <ji...@apache.org> on 2015/01/03 13:11:34 UTC
[jira] [Updated] (OFBIZ-3554) Delegator removeByXXX do not trigger
remove ECA
[ https://issues.apache.org/jira/browse/OFBIZ-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Divesh Dutta updated OFBIZ-3554:
--------------------------------
Attachment: OFBIZ-3554.patch
If this is concluded as a bug, then I am providing a patch to fix this issue, because I have already worked on this ticket. Also tested the patch by writing custom service and its working fine.
This patch will trigger ECA rules for removeByAnd, removeByCondition and removeAll , removeRelated methods.
For storeAll and storeByCondition, we can create separate jira issue and fix that as well.
> Delegator removeByXXX do not trigger remove ECA
> -----------------------------------------------
>
> Key: OFBIZ-3554
> URL: https://issues.apache.org/jira/browse/OFBIZ-3554
> Project: OFBiz
> Issue Type: Bug
> Components: framework
> Affects Versions: Release Branch 09.04, Trunk
> Reporter: Wickersheimer Jeremy
> Assignee: Adam Heath
> Attachments: OFBIZ-3554.patch
>
>
> The removeByAnd / removeByCondition and by extension i think the removeAll methods do not trigger the remove ECA on the entities.
> So for example:
> {code:title=No trigger|borderStyle=solid}
> removeByAnd("FooBar", map);
> {code}
> Compared to:
> {code:title=With trigger|borderStyle=solid}
> List entities = delegator.findByAnd("FooBar", map);
> for (GenericValue v : entities) {
> delegator.removeValue(v);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)