[
https://issues.apache.org/jira/browse/SMX4NMR-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated SMX4NMR-195:
-----------------------------------------
Fix Version/s: (was: 1.3.0)
1.4.0
> Dynamically enable/disable cluster engine when ConnectionFactory available in
> registry
> --------------------------------------------------------------------------------------
>
> Key: SMX4NMR-195
> URL: https://issues.apache.org/jira/browse/SMX4NMR-195
> Project: ServiceMix NMR
> Issue Type: Improvement
> Affects Versions: 1.2.0
> Reporter: Gert Vanthienen
> Fix For: 1.4.0
>
>
> Currently, the Cluster engine is configured with a Blueprint proxy to the
> ConnectionFactory that's available in the OSGi Service Registry. This way,
> the Cluster Engine isn't aware of changes in the registry (e.g. the
> ConnectionFactory is being removed or a new one is registered).
> We should improve the engine to dynamically enable/disable clustering
> depending on the availability of a suitable ConnectionFactory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
