From a management perspective I think people want to see all the
service configurations together. The important part of a domain is its use as a logical
model and the ability to organize the configurations of its parts. Its fine to target
certain services to a subset of the nodes in a domain (a sub-domain), but I think the most
convenient definition would be that every node in domain shares all configuration data.
I can target session replication to ReplicationGroupA and entities to ReplicationGroupB,
but both should be part of the overall domain config. The only difference between nodes
should be their identity and membership in these sub-domain/replication groups. I want to
be able to define that replication group and then add any node in my domain to it in the
tool.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118854#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...