So, how do you feel about extending property description in the model to include optional info such as: - value set, i.e. an enum of allowed values, e.g. for transaction isolation, etc; - dependency on another property, e.g. exception-sorter-properties assumes that exception-sorter-class-name is specified; - properties choice, e.g. driver-class and driver-name, one excludes the other; - property value set restricted by the existing values of some other properties, e.g. driver-name can take values from the registered jdbc drivers. I actually did a simple prototype which includes all of the above except the last one https://github.com/aloubyansky/jboss-as/commit/833934db69bec304ff37b29188... It's obviously not the best way of doing it but just to give an idea. This will help with tab-completion in cli and perhaps other tools too. Thanks, Alexey _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

So, how do you feel about extending property description in the model to include optional info such as: - value set, i.e. an enum of allowed values, e.g. for transaction isolation, etc; - dependency on another property, e.g. exception-sorter-properties assumes that exception-sorter-class-name is specified; - properties choice, e.g. driver-class and driver-name, one excludes the other; - property value set restricted by the existing values of some other properties, e.g. driver-name can take values from the registered jdbc drivers. I actually did a simple prototype which includes all of the above except the last one https://github.com/aloubyansky/jboss-as/commit/833934db69bec304ff37b29188... It's obviously not the best way of doing it but just to give an idea. This will help with tab-completion in cli and perhaps other tools too. Thanks, Alexey _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev