[ https://issues.apache.org/jira/browse/CAMEL-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ben O'Day updated CAMEL-4397: ----------------------------- Priority: Major (was: Minor) Fix Version/s: (was: 2.9.0) 2.10 I'd like to revisit this and either move forward (in 2.10) or close it. From my perspective, I still see a use case and my patch (with a bit of cleanup) appears to address it w/o conflicting with related issues (CAMEL-4454, etc). Either way, if you feel strongly about this one way or another, let me know...thanks > 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 > Fix For: 2.10 > > 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} > see this > discussion...http://camel.465427.n5.nabble.com/discuss-implementing-Locks-in-Camel-td4775904.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira