[jboss-as7-dev] Case-sensitivity of restricted model values

[Brian Stansberry]

IMO we should always store and output values that match the "allowed" 
description in the metadata but should always be lenient about accepting 
input.

I had a look at all the uses of ModelDescriptionConstants.ALLOWED and it 
would be pretty simple to tweak a few places and have everything on the 
server side conform to that rule.

I'd prefer to have that be a hard rule than introduce a new piece of 
descriptive metadata. If someone really really needs to have an 
exception to the rule, then we can consider adding descriptive metadata.

On 11/24/11 10:01 PM, Jason Greene wrote:
> Good question. In this case I made it lenient but we don't necessarily have an established convention. IMO it does make a lot of sense to treat enums as case insensitive. Perhaps we need a description attribute for that
>
> Sent from my iPhone
>
> On Nov 24, 2011, at 3:21 AM, David Bosschaert<david at redhat.com>  wrote:
>
>> Hi all,
>>
>> Looking at the security domain subsystem I see that that the
>> authorization flag field has an allowed list of:
>> "allowed" =>  [
>>    "REQUIRED",
>>    "REQUISITE",
>>    "SUFFICIENT",
>>    "OPTIONAL"]
>>
>> However, the default model (what you get with a fresh new AS7 install)
>> has the flag value in lowercase:
>>    "flag" =>  "required",
>>
>> I'm wondering are we generally lenient wrt to case or is the
>> pre-populated value outside the range?
>>
>> Cheers,
>>
>> David
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev


-- 
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat