The status is in server-config, as is start/stop/restart:
[localhost:9999 /]
/host=local/server-config=server-one:read-attribute(name=status)
{
"outcome" => "success",
"result" => "STARTED",
"compensating-operation" => undefined
}
[localhost:9999 /]
/host=local/server-config=server-one:read-operation-names
{
"outcome" => "success",
"result" => [
"add",
"read-attribute",
"read-children-names",
"read-children-resources",
"read-children-types",
"read-operation-description",
"read-operation-names",
"read-resource",
"read-resource-description",
"remove",
"restart",
"start",
"stop",
"write-attribute"
],
"compensating-operation" => undefined
}
That's the thing I disliked that drove the thread leading to JBAS-9130.
Thanks for the JIRA! I didn't want to just do it without agreement from you.
I'll schedule JBAS-9130 tomorrow, when I get a chance to talk to
Emanuel. I want to give stuff you need highest priority; we'll see if we
can bump some Beta2 stuff into Beta3 to get this in.
On 3/24/11 8:33 AM, Heiko Braun wrote:
[localhost:9999 /] /host=local:read-children-resources(child-type=server,
recursive=true)
{
"outcome" => "success",
"result" => [],
"compensating-operation" => undefined
}
I would assume that there should a status element included.
At least until
https://issues.jboss.org/browse/JBAS-9130 is implemented, right?
Ike
On Mar 24, 2011, at 2:26 PM, Heiko Braun wrote:
> Looks like there is nothing at /host=local/sever=<XYZ>
>
> It is not implemented or am I missing something?
> I need to query the status of a server (started/stopped)
>
> Ike
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
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