[jboss-as7-dev] Standalone Server: Domain Model

[David M. Lloyd]

On 01/11/2011 04:44 AM, Heiko Braun wrote:
> Referring to:
> https://community.jboss.org/wiki/DomainManagementModelDesign
> [...]
> Creating two 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".

There is actually only one API.  The data organization changes to an 
extent in domain mode.

However in standalone mode there is no concept of a server group for 
example, nor a concept of domain-level deployments.  Instead, in the 
standalone sense, deployments encompass some features of both of these 
concepts.  The view *must* be different, I'm sorry.  But the good news 
is, a lot of it should be reusable.

In fact my feeling is that the view should be fully dynamic, but we 
shall see if that is even possible.

> What domain model concepts can you think of that don't match the
> standalone scenario?

Many operations simply don't make sense in a standalone situation, like 
anything involving deployment plans, server control, or multiple servers 
in one operation.

The data organization is fairly different too.  The management model 
hierarchy is more like this:

domain
+-- profiles
|   +-- web
|   |   +-- subsystems
|   |       +-- web
|   |       |   +-- connector...
|   |       +-- remoting
|   |           +-- blah blah
|   +-- another
|       +-- subsystems
|           +-- blah
+-- host foo
|   +-- server bar
|       +-- a bunch of other stuff
|   +-- server baz
+-- host bar
|   +--- server bar
|   +--- server bzt
+-- deployments
|   +--- foo.war
|   +--- bar.ear
+-- server group blah = profile web
|   +--- deployments
|        +-- foo.war
+-- server group blah = profile another
|   +--- deployments
|        +-- bar.ear
...

in standalone it's more like:
server
+-- profile
|   +-- subsystems
|       +-- web
|       |   +-- connector...
|       +-- remoting
|           +-- blah blah
+-- deployments
|   +-- foo.war
|   +-- bar.ear
...

So you see, the data is the same in many cases but the organization and 
addressing is different.  There is just one API, however you have to use 
more complex addressing in the domain case to distinguish between 
multiple items where in the standalone case there is just one, or none 
of that item.

Hope this clarifies things.
-- 
- DML