On 3/18/11 7:03 AM, Heiko Braun wrote:
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.
{
"address" => [("host" => "local")],
"operation" => "read-resource"
}
outcome' : 'success',
'result' :
{
[...]
'server-config' :
{
'server-one' :
{
},
'server-two' :
{
},
'server-three' :
{
}
},
[...]
'server' :
{
}
},
'compensating-operation' :
{
}
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat