Referring to:
https://community.jboss.org/wiki/DomainManagementModelDesign
"Internally, the object model representing the domain configuration for a standalone
server may be quite similar to that shown above. However, the XML configuration schema and
perhaps the management API will be simplified to remove extraneous concepts like the
ServerGroup. (Whether creating a distinct management API for this use case is appropriate
needs discussion. A separate API means clients like JON and the embedded console need to
be coded against two APIs in order to cover all use cases.)"
Creating to API's doesn't make sense at all. Instead we should try to collapse the
concepts when used standalone. I.e. by referencing a default server group
"standalone".
What domain model concepts can you think of that don't match the standalone
scenario?
Ike