Justin Lee wrote:
> I'm all for not saving defaulted attribute values. But not saving
> elements simply because all the attributes have defaulted values is not
> working.
I agree with Justin on this. We ran into the same problem with
SSH support on nodes and ended up hacking around it by always
forcing an attribute of the child element to have a value.
An element with all attributes defaulted is not the same thing
as no element at all. We need to be able to tell the difference.
Joe
>
> On 8/19/10 12:03 PM, Ludovic Champenois wrote:
>> On 8/19/10 8:50 AM, Justin Lee wrote:
>>> That's a horrible hack
>> Not completely sure about that:-) User visible and controllable in
>> config.
>> Reverting to store all default values is anyway uglier... So let's see
>> if there is yet another way to fix the issue.
>> Ludo
>>> to impose locally to a problem that exists everywhere, though. And
>>> it would require another grizzly integration just to get it. Not
>>> really much of an option.
>>>
>>> On 8/19/10 11:39 AM, Ludovic Champenois wrote:
>>>> On 8/19/10 8:30 AM, Justin Lee wrote:
>>>>> We can't use @NotNull because this element isn't always used. I
>>>>> like the idea of not writing out defaulted *attributes* but not
>>>>> writing such elements causes too many problems.
>>>>>
>>>>>
>>>> Will wait for Jerome.
>>>> Maybe you could add a field in http-redirect that says used or not?
>>>> By default it would be off (so not saved), but setting it would
>>>> activate the redirect....and the storage?
>>>> Ludo
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>