I would agree with that. If one is invalid, nothing should be set and
an error message and code should be returned.
On Oct 1, 2009, at 6:51 PM, Lloyd Chambers wrote:
> The only safe approach is "all or none" IMO, since the desire to set
> this way will likely involved related values.
>
> Lloyd
>
> On Oct 1, 2009, at 4:27 PM, Bill Shannon wrote:
>
>> I asked a few people privately but I thought it would be good to get
>> more opinions...
>>
>> If I do
>>
>> asadmin set a=b c=d e=f
>>
>> and "c" is an invalid name, what do you expect to happen?
>>
>> 1. fail after setting "a"?
>>
>> 2. fail after setting "a" and "e"?
>>
>> 3. fail before setting anything?
>>
>> 4. succeed with a warning that "c" wasn't set?
>>
>>
>> Right now (with my pending changes) it does #1 because that's what
>> was easy to implement.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
> Lloyd Chambers
> lloyd.chambers_at_sun.com
> GlassFish Team
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
Jason Lee
Senior Java Developer
GlassFish Administration Console
Sun Microsystems, Inc.
Phone x31197/+1 405-343-1964
Email jasondlee_at_sun.com
Blog
http://blogs.sun.com/jasondlee
Blog
http://blogs.steeplesoft.com