Page History

...

• The API is intended to ONLY update the cluster or server-group's configuration saved by the locator(s). For example, when developer uses the api to add a region definition to the cache configuration, it should NOT be expected that the api will also create the regions for you on the existing servers. 
• The API should not be tied with XML. We should be able to change how we save cluster configuration internally without changing the api.
• Expose a clean Java API for retrieval and modification of the cluster configuration.

Anti-Goals

• This API is not to be confused with an API that app-developers can use from client to, say, create a region and update the cluster configuration at the same time. That API would entail a remote invocation of this lower-level api, but it's not the same.

Approach

• Define a no-op interfaces CacheElement and RegionElement to identify classes that may be saved to the cache and region XML entities, respectively.
• Leverage JAXB to generate an initial set of configuration objects.  
• Expose ClusterConfigurationService via the cache, provided a locator is managing that cache.

...