[
https://issues.apache.org/jira/browse/CAMEL-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109597#comment-13109597
]
Claus Ibsen commented on CAMEL-4397:
------------------------------------
Sergey sounds good. And possible make it possible for end users to provide a
3rd option, some may want to look at load on servers, and allow the server with
the lowest load to favor the lock. And whatnot. But that is just a wish. Having
1 and 2 is good.
> add route support for Hazelcast distributed locking/unlocking
> -------------------------------------------------------------
>
> Key: CAMEL-4397
> URL: https://issues.apache.org/jira/browse/CAMEL-4397
> Project: Camel
> Issue Type: Improvement
> Components: camel-hazelcast
> Reporter: Ben O'Day
> Assignee: Ben O'Day
> Priority: Minor
> Fix For: 2.9.0
>
> Attachments: CAMEL-4397.patch
>
>
> add support for Hazelcast distributed locking/unlocking APIs in a route...see
> http://www.hazelcast.com/documentation.jsp#Lock
> something like this...
> {code}
> from("seda:lockTest")
> .doTry()
> .setHeader(HazelcastConstants.LOCK_OBJECT, simple("ID-${header.id}"))
> .to("hazelcast:lock")
> .setBody(simple("processed[${body}]"))
> .to("mock:mock")
> .doFinally()
> .to("hazelcast:unlock");
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
