[ 
https://issues.apache.org/jira/browse/CAMEL-23414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino resolved CAMEL-23414.
--------------------------------------
    Resolution: Fixed

> camel-hazelcast: Allow customization of SerializationConfig on managed 
> Hazelcast instances
> ------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-23414
>                 URL: https://issues.apache.org/jira/browse/CAMEL-23414
>             Project: Camel
>          Issue Type: Task
>          Components: camel-hazelcast
>            Reporter: Andrea Cosentino
>            Assignee: Andrea Cosentino
>            Priority: Major
>             Fix For: 4.14.8, 4.18.3, 4.21.0
>
>
> camel-hazelcast constructs a Hazelcast Config via {{new 
> XmlConfigBuilder().build()}} in:
> - 
> {{org.apache.camel.component.hazelcast.HazelcastDefaultComponent#getOrCreateHzInstance}}
> - {{org.apache.camel.component.hazelcast.HazelcastUtil#newInstance}}
> - 
> {{org.apache.camel.processor.aggregate.hazelcast.HazelcastAggregationRepository#doStart}}
> - 
> {{org.apache.camel.processor.idempotent.hazelcast.HazelcastIdempotentRepository#doStart}}
> There is currently no way for users to customize the SerializationConfig of 
> these Camel-managed instances except by supplying a fully pre-built Config 
> externally.
> Proposed change:
> # Provide endpoint and repository options that allow users to customize 
> SerializationConfig aspects on the Camel-built Config, applied before calling 
> {{Hazelcast.newHazelcastInstance(config)}}.
> # Where the user supplies their own Config (the {{HAZELCAST_CONFIGU_PARAM}} / 
> {{HAZELCAST_CONFIGU_URI_PARAM}} paths in {{HazelcastDefaultComponent}}), 
> respect that configuration without overwriting.
> # Update documentation describing the new options and default behavior.
> # Add tests covering the new options and the behavior of user-supplied 
> Configs.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to