[
https://issues.apache.org/jira/browse/CAMEL-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039603#comment-13039603
]
Claus Straube commented on CAMEL-4015:
--------------------------------------
I'm pretty sure it'll no good idea to add the id (key) to the url, because this
value changes at every call. Other the operation. The reason why we've choosen
to set the operation into the header is the greater flexibility. Only if the
operation is a header variable you can change it on runtime. So you can do
something like this:
// keys are missing here
from("direct:insert").setHeader(HazelcastConstants.OPERATION,
constant(HazelcastConstants.PUT_OPERATION)).to("seda:x");
from("direct:get").setHeader(HazelcastConstants.OPERATION,
constant(HazelcastConstants.GET_OPERATION)).inOut("seda:x");
from("direct:delete").setHeader(HazelcastConstants.OPERATION,
constant(HazelcastConstants.DELETE_OPERATION)).to("seda:x");
from("seda:x").toF("hazelcast:%sfoo", HazelcastConstants.MAP_PREFIX);
> 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
