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

[David M. Lloyd]

On 01/12/2011 04:52 AM, Heiko W.Rupp wrote:
>
> Am 11.01.2011 um 11:44 schrieb Heiko Braun:
>> 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".
>
> +1 - I thought we had this already in Antwerp?
>
> For the standalone case just use some "defaults" for domain and
> profile. Parts of the tree that don't make sense, will return "an
> empty collection" which the API user would not need to display. And
> if standalone as some API methods enabled that aren't for domain
> mode, just expose them in both modes and return some "wrong mode"
> exception if they are called in wrong mode.

Why, when it's just a question of asking the server "what operations are
available"?  Very little of the tree is actually the same between domain
and standalone - applying this kind of logic is just going to create
lots of places where things can be broken.

> Aside from admin console/RHQ, other users will also like to have only
> one api to code against.

Of course there is only one API...

> Especially when writing CLI scripts against the standalone mode
> (don't want to fire n instances) and then later want to port them
> over to a domain.

What kind of API unification do you think we can do here?  If they run a 
standalone script against a domain and want to modify some server 
parameter directly, they have to specify which server they want to talk 
to.  No amount of unification will change that.  And some things just 
aren't going to work - if you want to add a deployment in domain mode, 
the steps are just not quite the same, no matter what.

I think you should make an effort to understand the API a bit more 
before you criticize how it is organized.

-- 
- DML