Brian Stansberry wrote:
This was what I meant by the cluster-service tag, a way to specify how a group would cluster a particular service (maybe not all services should be clustered). Although it was just something I through out there as an example. A better way likely exists
Currently how we cluster a particular service is defined in that service's configuration, it's not something applied externally. And the details of what needs to be configured are often disparate between different services, so I'm not sure those configs can profitably be externalized into some common configuration element.
Ah, or are you talking about "clustered-service" as a wrapper to describe how to manage the service, e.g. how to (re)deploy across cluster?
But this is something that needs to change in the sense that basic things like what stack the ejb/web/jms/cluster aware container is using has to be a domain level setting that admins control as well as these stacks in terms of an admin clustering DSL. That config is then mapped onto the container metadata that controls the clustering behavior.