Is it worth consolidating all these into one xml format?

I would suggest we use the existing property format that we have for system properties: <foo-bar-properties> <property name="DEBUG" value="true"/> </foo-bar-properties> On May 18, 2011, at 1:10 PM, Heiko Braun wrote: > > > > On May 18, 2011, at 1:07 PM, Kabir Khan wrote: > >> Is it worth consolidating all these into one xml format? > > > definitely. > > > Ike > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

I didn't look at it yet, how does the addressable portion look like? Can you give me an example? Ike On May 18, 2011, at 1:17 PM, Kabir Khan wrote: > +1 > Related to this - they should probably be addressable in the same way as system properties are in Brian's commit for AS7-701? > http://github.com/jbossas/jboss-as/compare/45fe0a6...8c986cd > > On 18 May 2011, at 12:13, Heiko Braun wrote: > >> >> I would suggest we use the existing property format that we have for system properties: >> >> >> <foo-bar-properties> >> <property name="DEBUG" value="true"/> >> </foo-bar-properties> >> >> >> On May 18, 2011, at 1:10 PM, Heiko Braun wrote: >> >>> >>> >>> >>> On May 18, 2011, at 1:07 PM, Kabir Khan wrote: >>> >>>> Is it worth consolidating all these into one xml format? >>> >>> >>> definitely. >>> >>> >>> Ike >>> _______________________________________________ >>> jboss-as7-dev mailing list >>> jboss-as7-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >> >

"system-property" => { "foo" => {"value" => "bar"}, "key" => {"value" => "value"}

"system-property" => { "foo" =>"bar", "key" => "value" }

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 _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

It's a domain-mode thing (not part of the model for a server, just in the domain and host model). It controls whether the HostController passes the value to the server via the command line (-D) when it starts the server, or waits and passes it along with all the other management ops the server executes after boot to configure itself. Default is "true"; the "false" value exists to provide a way out in case the command line needed to start the server is too long. I expect it will be little used. On 5/18/11 7:50 AM, ssilvert(a)redhat.com wrote: > What does boot-time mean for this? > > Quoting Brian Stansberry&lt;brian.stansberry(a)redhat.com&gt;: > >> 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 >> _______________________________________________ >> 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 _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

It's a domain-mode thing (not part of the model for a server, just in the domain and host model). It controls whether the HostController passes the value to the server via the command line (-D) when it starts the server, or waits and passes it along with all the other management ops the server executes after boot to configure itself. Default is "true"; the "false" value exists to provide a way out in case the command line needed to start the server is too long. I expect it will be little used. On 5/18/11 7:50 AM, ssilvert(a)redhat.com wrote: > What does boot-time mean for this? > > Quoting Brian Stansberry&lt;brian.stansberry(a)redhat.com&gt;: > >> 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 >> _______________________________________________ >> 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

https://issues.jboss.org/browse/AS7-842 I've assigned it to myself for now but won't be able to get around to it for a while. If there are any other takers, feel free On 18 May 2011, at 15:59, David M. Lloyd wrote: > Glad to see this get in there... I was worried it got lost in the shuffle. > > On 05/18/2011 07:57 AM, Brian Stansberry wrote: >> It's a domain-mode thing (not part of the model for a server, just in >> the domain and host model). >> >> It controls whether the HostController passes the value to the server >> via the command line (-D) when it starts the server, or waits and passes >> it along with all the other management ops the server executes after >> boot to configure itself. >> >> Default is "true"; the "false" value exists to provide a way out in case >> the command line needed to start the server is too long. I expect it >> will be little used. >> >> On 5/18/11 7:50 AM, ssilvert(a)redhat.com wrote: >>> What does boot-time mean for this? >>> >>> Quoting Brian Stansberry&lt;brian.stansberry(a)redhat.com&gt;: >>> >>>> 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 >>>> _______________________________________________ >>>> 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 >> >> > > > -- > - DML > _______________________________________________ > 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

Am 18.05.2011 um 14:46 schrieb Brian Stansberry: > Because their full representation is: > 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 Standard operations are good.

Then there are several xsd's in the AS7 codebase that take properties whose formats I haven't checked. Is it worth consolidating all these into one xml format?