6:45 a.m.
It seems a bit arbitrary as to whether a subsystems content is
addressable or not. What I see for the logging subsystem vs the
transactions is that I can ls the logging subsystem and individually
read the children while transactions has no children, hence nothing to
ls, but there no obvious reason why one or more of the transactions
attributes could not be addressable resources. What goes into that choice?
[standalone@localhost:9999 /] ls subsystem=logging
periodic-rotating-file-handler size-rotating-file-handler
logger file-handler
async-handler console-handler
[standalone@localhost:9999 /]
./subsystem=logging/console-handler=CONSOLE:read-resource
{
"outcome" => "success",
"result" => {
"autoflush" => true,
"encoding" => undefined,
"formatter" => "%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n",
"level" => "INFO",
"queue-length" => undefined
},
"compensating-operation" => undefined
}
[standalone@localhost:9999 /] ls subsystem=transactions
[standalone@localhost:9999 /]
[standalone@localhost:9999 /] ./subsystem=transactions:read-resource
{
"outcome" => "success",
"result" => {
"core-environment" => {
"process-id" => {"uuid" => "uuid"},
"node-identifier" => undefined
},
"recovery-environment" => {
"socket-binding" => "txn-recovery-environment",
"status-socket-binding" => "txn-status-manager"
},
"coordinator-environment" => {
"enable-statistics" => undefined,
"default-timeout" => undefined
},
"object-store" => {
"relative-to" => undefined,
"path" => undefined
}
},
"compensating-operation" => undefined
}
On 5/21/11 2:10 PM, Brian Stansberry wrote:
CHILDREN is used for describing the relationship of a parent resource
to
a child resource. A resource is addressable, has attributes and
operations, and may have children.
ATTRIBUTE is used for describing attributes. Attributes don't have to be
simple types; they can be complex, which is the case with the attributes
in the transactions subsystem. But attributes aren't directly
addressable; e.g. if you want to read some detail of the
CORE_ENVIRONMENT you'd have to read the entire attribute and then access
the detail.
This is discussed in more detail on
http://community.jboss.org/docs/DOC-16317
On 5/21/11 12:48 PM, Scott Stark wrote:
> I see that some subsystems use CHILDREN as the model key to describe the
> subsystem root children, while others are using ATTRIBUTES. It does not
> appear to make a different right now, but I assume it will at some point?
>
> Logging:
> subsystem.get(CHILDREN, CommonAttributes.ROOT_LOGGER,
> DESCRIPTION).set(bundle.getString("root.logger"));
>
> Transactions:
> subsystem.get(ATTRIBUTES, CORE_ENVIRONMENT,
> DESCRIPTION).set(bundle.getString("core-environment"));
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev