camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-7563) Allow passing HazelcastInstance as a query parameter of a Hazelcast component endpoint.
Date Tue, 08 Jul 2014 06:33:35 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054567#comment-14054567
] 

Willem Jiang commented on CAMEL-7563:
-------------------------------------

We camel context look up the component, it always lookup the component from the registry (which
holds reference of blueprint beans or spring beans) first.  Please change the below bean id
to "hazelcast", in this way camel can use this configured component directly.

{code}
<bean id="hazelcastComponent" class="org.apache.camel.component.hazelcast.HazelcastComponent">
<argument index="0" ref="OpcoMediatorCtx" type="org.apache.camel.CamelContext" />
<property name="hazelcastInstance" ref="hazelcastInstance" />
</bean>
{code}

> Allow passing HazelcastInstance as a query parameter of a Hazelcast component endpoint.
> ---------------------------------------------------------------------------------------
>
>                 Key: CAMEL-7563
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7563
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-hazelcast
>            Reporter: Alexander Lomov
>            Assignee: Willem Jiang
>            Priority: Minor
>             Fix For: 2.14.0
>
>
> It is impossible now to pass an existing HazelcastInstance to a HazelcastEndpoint as
a bean from Registry. It complicates Hazelcast Endpoint usage in any DI environment.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message