Because their full representation is:
"system-property" => {
"foo" => {
"value" => "bar",
"boot-time" => true
},
"key" => {
"value" => "value",
"boot-time" => false
}
}
They are also proper resources in the model now rather than being an
attribute of some parent of type LIST. So they are manipulated via the
standard "add", "remove", "write-attribute" operations
instead of
requiring custom operations "add-system-property"
"remove-system-property". Resources are always represented in the model
a ModelType.OBJECT, not just a simple primitive value.
On 5/18/11 6:30 AM, Heiko W.Rupp wrote:
Am 18.05.2011 um 13:24 schrieb Kabir Khan:
> "system-property" => {
> "foo" => {"value" => "bar"},
> "key" => {"value" => "value"}
Why the extra "value=>" ? They are already grouped below
"system-property" and would directly be a map
> "system-property" => {
> "foo" =>"bar",
> "key" => "value"
> }
_______________________________________________
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