[
https://issues.apache.org/activemq/browse/SMXCOMP-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Simms updated SMXCOMP-603:
-------------------------------
Attachment: concurrent-exchange.txt
> Option for synchronous sending of message exchanges for the servicemix-vfs
> polling endpoint
> -------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-603
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-603
> Project: ServiceMix Components
> Issue Type: New Feature
> Components: servicemix-vfs
> Affects Versions: servicemix-vfs-2009.02
> Environment: Windows XP, service pack 3
> Servicemix 4.0, Kernel 1.1.0
> Reporter: Bill Simms
> Priority: Trivial
> Fix For: servicemix-vfs-2009.02
>
> Attachments: concurrent-exchange.txt
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> Under certain conditions a user of the VFSPollingEndpoint may need to
> guarantee that the endpoint will only send one message exchange at a time,
> regardless of how many files it has polled, or the number of threads that the
> ExecutorImpl instance has been configured with. An example of this is when
> the polling endpoint must deliver files in a specific order, and there cannot
> be any risk of out-of-order exchanges being sent. The user of the endpoint
> should be allowed to set the option of having exchanges sent in a concurrent
> or sequential fashion by the normal setter methods.
> I've modified and tested the servicemix-vfs-2009.02-SNAPSHOT to support
> asynchronous(concurrent) or synchronous exchange sending. I have performed
> minor testing of these changes and they appear to work as expected. The
> patch is included. By default exchanges are sent asynchronously as before.
> If these changes are acceptable the xml schema for servicemix-vfs should
> probably also be changed to expose the new setter.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
