I killed the redundant property value stuff in Json awhile ago. Which version are you
running against?
Sent from my iPhone
On Apr 11, 2011, at 6:33 AM, Heiko Braun <hbraun(a)redhat.com> wrote:
Requesting a server group resource I get this:
{
[INFO] "PROPERTY_VALUE" : {
[INFO] "other-server-group" : {
[INFO] "profile" : "default",
[INFO] "jvm" : {"default" : {
[INFO] "type" : null,
[INFO] "agent-lib" : null,
[INFO] "agent-path" : null,
[INFO] "debug-enabled" : null,
[INFO] "debug-options" : null,
[INFO] "env-classpath-ignored" : null,
[INFO] "environment-variables" : null,
[INFO] "heap-size" : "64m",
[INFO] "max-heap-size" : "512m",
[INFO] "java-agent" : null,
[INFO] "java-home" : null,
[INFO] "jvm-options" : null,
[INFO] "permgen-size" : null,
[INFO] "max-permgen-size" : null,
[INFO] "stack-size" : null,
[INFO] "system-properties" : null
[INFO] }},
[INFO] "deployment" : {},
[INFO] "socket-binding-group" :
"standard-sockets"
[INFO] }
[INFO] }
[INFO] },
The pice that's causing me a headache is again the JVm property.
Can we agree that subresources like the JVM in this case are always referenced as
ModelNode's of type
property? Similar to the server-group itself? Currently it's returned as type Object,
with a property of name 'jvm'
This would simplify the way to get hold of the subresource name.
Ike
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev