IIRC some releases back, if an attribute in a domain model resource, allowed a certain set of values, then a read-resource-description via the CLI would show the allowed values. But checking against the latest upstream, I don't see it available any more. For example the timeout-unit attribute of the strict-max-bean-instance-pool resource no longer shows the allowed values: [standalone@localhost:9999 /] /subsystem=ejb3/strict-max-bean-instance-pool=slsb-strict-max-pool:read-resource-description { "outcome" => "success", "result" => { "description" => "A bean instance pool with a strict upper limit", "attributes" => { "timeout-unit" => { "type" => STRING, "description" => "The instance acquisition timeout unit", "expressions-allowed" => false, "nillable" => true, "default" => "MINUTES", "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }, ... Was this change intentional? It would be nice to be able to know what values are allowed for certain attributes. By the way, is it just the CLI that would need a change for this or does this involve much more? -Jaikiran _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

Has anybody filed a jira on this? "Allowed" is used in console to get the list of log levels. So it needs to be there if at all possible. On 4/16/2012 8:16 AM, Alexey Loubyansky wrote: > It's not a CLI issue. It only shows what's available in the model. > > On 04/16/2012 01:20 PM, Jaikiran Pai wrote: >> IIRC some releases back, if an attribute in a domain model resource, >> allowed a certain set of values, then a read-resource-description via >> the CLI would show the allowed values. But checking against the latest >> upstream, I don't see it available any more. For example the >> timeout-unit attribute of the strict-max-bean-instance-pool resource no >> longer shows the allowed values: >> >> [standalone@localhost:9999 /] >> /subsystem=ejb3/strict-max-bean-instance-pool=slsb-strict-max-pool:read-resource-description >> { >> "outcome" => "success", >> "result" => { >> "description" => "A bean instance pool with a strict upper limit", >> "attributes" => { >> "timeout-unit" => { >> "type" => STRING, >> "description" => "The instance acquisition timeout unit", >> "expressions-allowed" => false, >> "nillable" => true, >> "default" => "MINUTES", >> "access-type" => "read-write", >> "storage" => "configuration", >> "restart-required" => "no-services" >> }, >> ... >> >> Was this change intentional? It would be nice to be able to know what >> values are allowed for certain attributes. By the way, is it just the >> CLI that would need a change for this or does this involve much more? >> >> -Jaikiran >> _______________________________________________ >> 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 _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev