You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Ben O'Day (JIRA)" <ji...@apache.org> on 2012/07/07 00:24:34 UTC

[jira] [Commented] (CAMEL-3211) Enrich and PollEnrich - Option to let it poll multiple messages

    [ https://issues.apache.org/jira/browse/CAMEL-3211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408400#comment-13408400 ] 

Ben O'Day commented on CAMEL-3211:
----------------------------------

r1358452: I added some basic support for polling multiple Exchanges from an endpoint a flag on pollEnrich().  This mode simply polls until empty (using either noWait or an explicit timeout) and creates a List of Exchanges to use as the body...  

That said, there are several different approaches to doing this.  For now, I just picked a basic use case to get the ball rolling.  If anyone has any other thoughts about other features they'd like to see implemented, let me know.


                
> Enrich and PollEnrich - Option to let it poll multiple messages
> ---------------------------------------------------------------
>
>                 Key: CAMEL-3211
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3211
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.4.0
>            Reporter: Claus Ibsen
>            Assignee: Ben O'Day
>            Priority: Minor
>             Fix For: 2.11
>
>
> Think about if we can enhance enrich and/or pollEnrich to be able to poll multiple messages.
> For example to drain a JMS queue, or a FTP site etc. Currently it polls only 1 message, and the continues.
> With some option to tell it to continue we can have it drain the queue until no more messages.
> Or maybe some expression to tell when to stop. Or have some option in the custom aggregator the end user can set/control if it should continue or poll more.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira