[
https://issues.apache.org/jira/browse/CAMEL-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044513#comment-13044513
]
Richard Kettelerij commented on CAMEL-4015:
-------------------------------------------
I think we're all on the same page here. Header-based configuration as
currently available is nice, but supporting both headers and URI parameters
would be even better. Most importantly because it's inline with other
components offered by Camel.
When one knows upfront what operation/id is required (as in Romain's use case)
then it's more convenient to specify this through a parameter in the URI. A
header on the other hand is more suitable when the operation/id is determined
dynamically by another component in the route (e.g. a custom processor or as
part of a web service request). In this case the header will override the URI
parameter if present.
Feel free to provide a patch if you wish this to be implemented.
> camel hazelcast uri format
> --------------------------
>
> Key: CAMEL-4015
> URL: https://issues.apache.org/jira/browse/CAMEL-4015
> Project: Camel
> Issue Type: Improvement
> Components: camel-hazelcast
> Reporter: Romain Manni-Bucau
> Priority: Trivial
>
> It could be nice to be able to specify type operation (and maybe the key for
> map) in the uri instead of headers:
> from("hazelcast:map:foo?operation=get&id=myStringId").to("log:display");
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
