Brian Stansberry [
http://community.jboss.org/people/bstansberry%40jboss.com] replied to
the discussion
"Domain model work in AS 6.0.0"
To view the discussion, visit:
http://community.jboss.org/message/536672#536672
--------------------------------------------------------------
Scott Stark wrote:
For the YES, this is my quick overview. Again my concern is having suffucient structure
to be able to evolve the domain model, but a sufficiently limited scope in terms of
content to be able to have an implementation.
bindingservice.beans - All of the containers/services intersected by this need associated
entries in the domain model such that this configuration can be dropped.
Yep. This will probably mean some other stuff (iiop, snmp) get pulled in, at least the
socket configurations.
The SBM does provide two other nice benefits:
1. The easy-to-specify "for this server offset base port numbers by XX". Which
can be a server-level property in a domain model.
2. A central view to all the port configurations. Which is just a view on the domain
model; doesn't mean they all need to be configured in the same place.
mod_cluster.sar,
jboss-cache-manager.sar,
jgroups-channel-factory.sar,
deploy-hasingleton-jboss-beans.xml,
farm-deployment-j-b.xml,
hajndi-j-b.xml,
hapartition-jboss-beans.xml, - Need a cluster domain metadata model
mod_cluster is a bit of an outlier, as it doesn't require any sort of intra-cluster
communication; can be applied to a server-group.
jbossweb.sar/server.xml,
ejb3-connectors-j-b.xml,
remoting3-j-b.xml,
remoting-j-b.xml,
xnio-provider.jar - Need a connector/transport domain metadata model
Leave other server.xml stuff (e.g. valves) out of scope?
--------------------------------------------------------------
Reply to this message by going to Community
[
http://community.jboss.org/message/536672#536672]
Start a new discussion in Management Development at Community
[
http://community.jboss.org/choose-container!input.jspa?contentType=1&...]