Re: [wildfly-dev] Preparation for requirements and capabilities.

On 19/03/15 16:23, James R. Perkins wrote: > > On 03/19/2015 03:20 AM, Darran Lofthouse wrote: >> Assuming the title still covers the scenarios I have in mind is there >> anything we can be doing now to prepare for requirements and >> capabilities support to make transitioning easier once it is available. >> >> As an example within Elytron we will have a number of services that >> define either standard types or types defined by API that we want to >> inject - is there anything we can do today for subsystems that want to >> say "I want a type X, named Y injected here" whilst minimising >> interaction with and knowledge of the Elytron subsystem. >> >> Secondly is there anything we can do at the model level regarding >> assisting the user with referential integrity, as an example say I am >> writing an attribute using the CLI called 'keystore', this is going to >> be a reference to a named KeyStore - how about some form of op >> associated with that attribute that can dynamically generate the list of >> accepted values on demand, e.g. by querying the model and finding out >> which KeyStores are actually available. > Attributes can use an EnumValidator which allows only the values in an > enum to be used. These work with tab complete in CLI as well. Would that > solve the your issue? Or are you looking for the allowed values based on > another resource? Allowed based on other resources, also we probably need to accept values not in the allowed list as it could be a compound op adding the acceptable resource.

>> Regards, >> Darran Lofthouse. >> _______________________________________________ >> wildfly-dev mailing list >> wildfly-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/wildfly-dev _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev