<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div><br></div><div>We got a lot of places where key/value pairs are used as part of the configuration:</div><div><br></div><div>- system properties</div><div>- xa data source properties</div><div>- resource adapter config properties</div><div>- (put your subsystem here)</div><div><br></div><div><br></div><div>The most reasonable way to represent these properties within the model </div><div>is to make them sub resources which can be addressed on their own, i.e:</div><div><br></div><div><br></div><div><div>[standalone@localhost:9999 /] /system-property=hostType:read-resource</div><div>{</div><div> "outcome" => "success",</div><div> "result" => {"value" => "staging"}</div><div>}</div></div><div><br></div><div>why? because if they are represented like sub resources, </div><div>the implicit add/remove operations automatically apply:</div><div><br></div><div><br></div><div><div>[standalone@localhost:9999 /] /system-property=newProperty:add(value=someValue)</div><div>{"outcome" => "success"}</div></div><div><br></div><div><br></div><div>The same is true for querying their value as shown above.</div><div><br></div><div><b>This is request to unify the usage key/value pair configuration options</b> like described above.</div><div>I'll go ahead and create JIRA's for the cases that I encounter and ask you kindly to change all occurrences</div><div>to the sub resource model representation.</div><div><br></div><div><br></div><div>Ike</div><div><br></div><div><br></div><div><br></div></body></html>