10:06 a.m.
I tried adding this comment to the forum thread, but it won't accept it;
I'll try again later:
"I need to update that doc a bit to slightly loosen the statement that
add and remove should always be available. There are some resources that
are not directly created based on user action but are "runtime only",
i.e. they are exposing runtime stuff. An example would be the platform
mbean resources; they expose things provided by the JVM and a user can't
"add" or "remove" them.
But, as Kabir said, "add" and "remove" should be there for subsystems
and extensions.
Kabir, further to your comment, I've added
https://issues.jboss.org/browse/AS7-2424."
At this point, if you find a common operation not working against
something, please file a JIRA. If it's against a subsystem, please make
the primary component the subsystem, assigned to the subsystem lead.
Adding "Domain Management" as a secondary component is fine.
There are some cases where a common operation won't do the job; e.g.
"shutdown" -- we don't support "remove" on the root resource as a
way to
shut down a server or host. Many "runtime operations" are also custom,
e.g. messaging has some stuff "delete messages matching filter X from
queue Y", plus many other things of that nature.
There may be some cases where a custom operation is required to do
something related to the persistent configuration, but such things
should be few and far between and challenged if found to ensure there
isn't a better way.
On 10/28/11 6:47 AM, ssilvert(a)redhat.com wrote:
Forwarding to the dev list. I'm wondering to what extent we are
required
to support these common operations?
Like Dmitri, I'm finding lots of places where the common operations are
not supported or not working for all attributes.
Is it theoretically possible to do everything you need with the common ops?
Are custom ops needed or are they just for convenience?
Stan
----- Forwarded message from do-not-reply(a)jboss.com -----
Date: Fri, 28 Oct 2011 07:27:26 -0400
From: Dmitri Voronov <do-not-reply(a)jboss.com>
Reply-To: Dmitri Voronov <do-not-reply(a)jboss.com>
Subject: [AS7 Users] - Common management operations
To: Stan Silvert <ssilvert(a)jboss.com>
Dmitri Voronov [http://community.jboss.org/people/dimonv] created the
discussion
"Common management operations"
To view the discussion, visit:
http://community.jboss.org/message/634032#634032
--------------------------------------------------------------
Hi all,
the admin guide
https://docs.jboss.org/author/display/AS7/Management+Clients
https://docs.jboss.org/author/display/AS7/Management+Clients
says:
"... common operations that exist on any node... The common operations are:
* add
* remove
* read-attribute
* write-attribute
* read-children-names
* read-children-resources
* read-children-types
* read-operation-description
* read-operation-names
* read-resource
* read-resource-description"
Thus I can execute e.g.:
[standalone@localhost:9999 /] /extension=org.divo.hr:add
{"outcome" => "success"}
and
[standalone@localhost:9999 /] /subsystem=hr:add
{"outcome" => "success"}
but I cannot execute:
[standalone@localhost:9999 /] /subsystem=hr:remove
{
"outcome" => "failed",
"failure-description" => "No handler for operation remove at
address [(\"subsystem\" => \"hr\")]",
"rolled-back" => true
}
but I can:
[standalone@localhost:9999 /] /extension=org.divo.hr:remove
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
Are subsystems and extenssions an exception?
Anyway, in my opinion as an infrustructure responsible I should be able
to manage extensions and subsystems.
Regards
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/634032#634032]
Start a new discussion in AS7 Users at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
----- End forwarded message -----
JBoss Community <http://community.jboss.org/index.jspa>
Common management operations
created by Dmitri Voronov <http://community.jboss.org/people/dimonv> in
/AS7 Users/ - View the full discussion
<http://community.jboss.org/message/634032#634032>
------------------------------------------------------------------------
Hi all,
the admin guide
https://docs.jboss.org/author/display/AS7/Management+Clients
says:
"... common operations that exist on any node... The common operations are:
* add
* remove
* read-attribute
* write-attribute
* read-children-names
* read-children-resources
* read-children-types
* read-operation-description
* read-operation-names
* read-resource
* read-resource-description"
Thus I can execute e.g.:
|[standalone@localhost:9999 /] /extension=org.divo.hr:add
{"outcome" => "success"}
|
and
|[standalone@localhost:9999 /] /subsystem=hr:add
{"outcome" => "success"}
|
but I cannot execute:
|[standalone@localhost:9999 /] /subsystem=hr:remove
{
"outcome" => "failed",
"failure-description" => "No handler for operation remove at
address [(\"subsystem\" => \"hr\")]",
"rolled-back" => true
}
|
but I can:
|[standalone@localhost:9999 /] /extension=org.divo.hr:remove
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
|
Are subsystems and extenssions an exception?
Anyway, in my opinion as an infrustructure responsible I should be able
to manage extensions and subsystems.
Regards
Reply to this message by going to Community
<http://community.jboss.org/message/634032#634032>
Start a new discussion in AS7 Users at Community
<http://community.jboss.org/choose-container!input.jspa?contentType=1&...
_______________________________________________
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