]
Mark Little closed JBESB-1906.
------------------------------
Resolution: Won't Fix
The stateful wokring memory should be unique per message correlation
number
---------------------------------------------------------------------------
Key: JBESB-1906
URL:
https://jira.jboss.org/jira/browse/JBESB-1906
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Content Based Routing
Affects Versions: 4.4
Reporter: Jiri Pechanec
For me it seems probably much more useful to provide also option to have stateful rule
service organized on different basis.
Each message should contain correlation identifier and the stateful session will be
created per the correlation identifier.
It will server much better the intent that is described in excerpt from Service
documentation
----- These can be added directly by an ESB aware client. A non-ESB aware client
would have to communicate the position of the message (first, ongoing, last) in the data,
and an action class would need to be added to the pipeline to add the properties to the
ESB message (see quickstarts/business_ruleservice_stateful for an example of this type of
service).
Moreover there can be service thread that will periodically dispose unused working
memories - last meesage did not arrived
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: