[
https://issues.apache.org/jira/browse/CAMEL-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053594#comment-14053594
]
Alexander Lomov commented on CAMEL-7563:
----------------------------------------
Hi Willem,
Could we please continue the conversation on the last fix?
I've just tried to create a HazelcastComponent with a Blueprint container and
pass a Hazelcast instance to a property setter. The results are as follows:
doStart in being invoked before the property setter is being called, the
component checks the this.hazelcastInstance == null, creates the default one,
and then assigns the setHazelcastInstance parameter to the hazelcastInstance
field.
I believe we should either add an overloaded constructor that accepts a
HazelcastInstance parameter or create the default HazelcastInstance not in the
doStart method.
What do you think?
> 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)
