[jboss-jira] [JBoss JIRA] Updated: (JBAS-9130) Create a unified server-config resource that includes the actual instance operations

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/JBAS-9130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated JBAS-9130:
-----------------------------------

    Fix Version/s: 7.0.0.Beta3
      Description: 
is the 'server' node the element that contains server instances?

Yes; that's where you access the actual running server.

The operations to actually start/stop/restart the server and check their
status are under "server-config" which I'm not happy about. Not
intuitive. It's that way because of a kind of chicken-and-egg problem.

Emanuel, WDYT about a more sophisticated ProxyController for the
servers? Installed by the ServerAddHandler. It handles the lifecycle and
status ops directly; proxies the rest. Where it gets complicated is
things like read-resource, read-resource-description, read-attribute,
all of which would require custom handling. It also make a server
resource an odd duck, since it's resource description varies depending
on whether the server is started.


Yes, we could think of doing something like that - maybe we should just
create a ManagedServer for all configured servers and make it the proxy.
It should be aware of the lifecyle/state of the server anyway and also
holds the associated managed connection.


Yes, that sounds like the right way to implement it.

Heiko/Ike/Emanuel/anyone -- any concerns about the "resource description 
varies" issue?

What I mean is, for all other resources, read-resource-description will 
return fixed content. For host=x,server=y it will vary depending on 
whether the server is actually started. If not running, it will just 
provide the operation to start the server and a "status" attribute, 
which will tell you it's stopped. Once you start the server, then 
read-resource-description will provide that, plus ops to stop and 
restart the server, plus all the normal attributes and operations 
exposed by the root resource of a server.


  was:

is the 'server' node the element that contains server instances?

Yes; that's where you access the actual running server.

The operations to actually start/stop/restart the server and check their
status are under "server-config" which I'm not happy about. Not
intuitive. It's that way because of a kind of chicken-and-egg problem.

Emanuel, WDYT about a more sophisticated ProxyController for the
servers? Installed by the ServerAddHandler. It handles the lifecycle and
status ops directly; proxies the rest. Where it gets complicated is
things like read-resource, read-resource-description, read-attribute,
all of which would require custom handling. It also make a server
resource an odd duck, since it's resource description varies depending
on whether the server is started.


Yes, we could think of doing something like that - maybe we should just
create a ManagedServer for all configured servers and make it the proxy.
It should be aware of the lifecyle/state of the server anyway and also
holds the associated managed connection.


Yes, that sounds like the right way to implement it.

Heiko/Ike/Emanuel/anyone -- any concerns about the "resource description 
varies" issue?

What I mean is, for all other resources, read-resource-description will 
return fixed content. For host=x,server=y it will vary depending on 
whether the server is actually started. If not running, it will just 
provide the operation to start the server and a "status" attribute, 
which will tell you it's stopped. Once you start the server, then 
read-resource-description will provide that, plus ops to stop and 
restart the server, plus all the normal attributes and operations 
exposed by the root resource of a server.




Scheduled for Beta3 for now; Emanuel lets chat about the Beta2/3 roadmap and see if it makes sense to reshuffle.

> Create a unified server-config resource that includes the actual instance operations
> ------------------------------------------------------------------------------------
>
>                 Key: JBAS-9130
>                 URL: https://issues.jboss.org/browse/JBAS-9130
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Domain Management
>            Reporter: Heiko Braun
>            Assignee: Emanuel Muckenhuber
>             Fix For: 7.0.0.Beta3
>
>
> is the 'server' node the element that contains server instances?
> Yes; that's where you access the actual running server.
> The operations to actually start/stop/restart the server and check their
> status are under "server-config" which I'm not happy about. Not
> intuitive. It's that way because of a kind of chicken-and-egg problem.
> Emanuel, WDYT about a more sophisticated ProxyController for the
> servers? Installed by the ServerAddHandler. It handles the lifecycle and
> status ops directly; proxies the rest. Where it gets complicated is
> things like read-resource, read-resource-description, read-attribute,
> all of which would require custom handling. It also make a server
> resource an odd duck, since it's resource description varies depending
> on whether the server is started.
> Yes, we could think of doing something like that - maybe we should just
> create a ManagedServer for all configured servers and make it the proxy.
> It should be aware of the lifecyle/state of the server anyway and also
> holds the associated managed connection.
> Yes, that sounds like the right way to implement it.
> Heiko/Ike/Emanuel/anyone -- any concerns about the "resource description 
> varies" issue?
> What I mean is, for all other resources, read-resource-description will 
> return fixed content. For host=x,server=y it will vary depending on 
> whether the server is actually started. If not running, it will just 
> provide the operation to start the server and a "status" attribute, 
> which will tell you it's stopped. Once you start the server, then 
> read-resource-description will provide that, plus ops to stop and 
> restart the server, plus all the normal attributes and operations 
> exposed by the root resource of a server.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira