Anissa Lam wrote on 06/28/10 04:12 PM:
>>> 2. What should be the default value of this keepState option? False or
>>> null? Shingwai had the concern that if the default value is false, the
>>> container will not know if it's explicitly set to false by the user or
>>> it's the default value. Any thoughts on this? Any potential issue of
>>> having this option default value as null?
>>
>> I'm a little nervous about assuming that these boolean options are
>> actually tri-state values - null/false/true. But, I believed we've
>> used this elsewhere, and it does solve the problem of allowing the
>> CLI to override the deployment descriptor if the option is specified
>> explicitly.
>
> From the GUI point of view, a boolean is either true or false.
> Think about a checkbox in the re-deploy screen. I can only pass in a
> 'true' if the box is checked, or 'false' if the box is unchecked.
> When the redeploy screen shows up, the box will be unchecked, when user
> press 'redeploy button', GUI will pass in a 'false' for this option.
> Hope thats what you expected.
Does the GUI have other cases where it allows you to override the
behavior specified in the deployment descriptor, or not? What if
the behavior is something that has a boolean value? How is that
represented in the GUI?
How does the GUI represent the drop/create options for EJB and JPA?