[
https://issues.jboss.org/browse/JBRULES-3514?page=com.atlassian.jira.plug...
]
Wolfgang Laun commented on JBRULES-3514:
----------------------------------------
(WL9) Section 6
I would have thought that picking (or "consuming") events from the event stream
according to some sequencing pattern would be the most natural processing of an event
stream. IMHO, the construct given below would be a very useful one, matching only the
first triplet, and not reusing any already matched event. Note the proposed keyword
"next"!
event Call as next
offHook: OffHook( $s: subscriber ) ->
dialing: Dialing( subscriber == $s ) ->
onHook: OnHook( subscriber == $s )
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