camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Straube (JIRA)" <>
Subject [jira] [Commented] (CAMEL-4015) camel hazelcast uri format
Date Thu, 26 May 2011 09:18:47 GMT


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:
>             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:

View raw message