[
https://issues.jboss.org/browse/JBRULES-3514?page=com.atlassian.jira.plug...
]
Wolfgang Laun commented on JBRULES-3514:
----------------------------------------
(WL7) Subection 6.1, re every
(a) I think that it is evil to have "every" as the default (even though it's
of the same quality as "and", i.e., resulting in all possible fact
combinations). However, the inclusion of an event into a complex event (normally) means
that it has been dealt with. Again, consider call handling: With "S1, E1, S2, E2, S3,
E3", there is simply no point in creating all S-E combinations.
(b) This should be the only way to request all event combinations of some A preceding some
C:
"event X as every A() -> C() end"
Add support to event sequencing
-------------------------------
Key: JBRULES-3514
URL:
https://issues.jboss.org/browse/JBRULES-3514
Project: Drools
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: drools-api, drools-compiler, drools-core
Reporter: Edson Tirelli
Assignee: Edson Tirelli
Fix For: 5.5.0.Beta1
The purpose of this ticket is to centralize the discussions regarding the implementation
of event sequencing as detailed in the wiki page at:
https://community.jboss.org/wiki/EventSequencing
The highlevel discussions can be added to this ticket while individual sub-tickets will
be created for the implementation of each sub-feature.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira