You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "vassilis spiliopoulos (JIRA)" <ji...@apache.org> on 2015/04/07 19:35:14 UTC
[jira] [Commented] (CAMEL-4596) enrich and pollEnrich should accept
an expression for dynamic uris
[ https://issues.apache.org/jira/browse/CAMEL-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14483583#comment-14483583 ]
vassilis spiliopoulos commented on CAMEL-4596:
----------------------------------------------
Any updates for this one?
Actually this will be a great Camel improvement, as it will allow consumption in the middle of a route without restrictions.. Any updates on this?
> enrich and pollEnrich should accept an expression for dynamic uris
> ------------------------------------------------------------------
>
> Key: CAMEL-4596
> URL: https://issues.apache.org/jira/browse/CAMEL-4596
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 3.0.0
>
>
> We should consider using an expression for uri's for the enrich and pollEnrich EIP's so we can poll from a dynamic computed endpoint.
> However it will break API as currently the uri is mandatory.
> It's a bit the same problem with to EIP which is also static uri. However for to EIP we have recipientList which is the dynamic to.
> So we need a similar dynamic for enrich and pollEnrich.
> This also solves the problem with that people wan't to provide details from the current exchange in the endpoint uri. We have a ticket for that.
> eg enrich("file:inbox?fileName=${header.nameToPickUp}")
> So if we can do it using an expression it could be
> .enrich().simple("file:inbox?fileName=${header.nameToPickUp}")
> See nabble
> http://camel.465427.n5.nabble.com/pollEnrich-consumer-with-selector-tp4939908p4939908.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)