[
https://issues.jboss.org/browse/DROOLS-644?page=com.atlassian.jira.plugin...
]
Mario Fusco resolved DROOLS-644.
--------------------------------
Resolution: Rejected
The no-loop attribute works on a consequence basis. This means that annotating a rule with
no-loop causes that a consequence cannot reactive itself but nothing prevent it to
activate a different consequence of the same rule.
The test case I pushed here
https://github.com/droolsjbpm/drools/commit/bc29b6653
demonstrates this behavior.
If you have a use case where what I am saying doesn't apply, feel free to reopen this
ticket and add a small reproducer for the issue you found.
no-loop attribute and named consequences
----------------------------------------
Key: DROOLS-644
URL:
https://issues.jboss.org/browse/DROOLS-644
Project: Drools
Issue Type: Bug
Affects Versions: 6.1.0.Final
Reporter: Pedro Martins
Assignee: Mario Fusco
Labels: named_consequence, no-loop
I wrote a rule that modifies a fact from within a named consequence. The no-loop
attribute failed to prevent the rule from reactivating.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)