[
https://issues.jboss.org/browse/JBESB-3746?page=com.atlassian.jira.plugin...
]
Tom Cunningham resolved JBESB-3746.
-----------------------------------
Resolution: Done
Add aggregation details to fragments being routed by the fragment router. The UUID and the
message count are grabbed through the executionContext. Support for this has also been
added into the FileStreamSplitter, which will populate the executionContext with these
details.
These must be used with the new StreamingAggregator (not the old Aggregator) because the
StreamingAggregator is able to store messages without the final sequence count - which is
unavailable until Smooks finishes splitting the
source.
Also added a streaming_aggregator_smooks quickstart, which demonstrates this functionality
by splitting a file and then aggregating it.
Smooks Fragment Router (or elsewhere) to tie fragments back to
original message for tracking or aggregation purposes
--------------------------------------------------------------------------------------------------------------------
Key: JBESB-3746
URL:
https://issues.jboss.org/browse/JBESB-3746
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 4.11
Reporter: Tom Cunningham
Assignee: Tom Cunningham
Fix For: 4.11
Smooks Fragment Router (or elsewhere) to tie fragments back to original message for
tracking or aggregation purposes
--
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