[jboss-as7-dev] Default values in the model

[Emanuel Muckenhuber]

We also seem to be talking about three different things.

- storing default values in the internal configuration model really does 
not add any value in the end. Nothing on the server side needs this as 
part of the model and can be easily added based on the description for 
the client. This is what Brian was referring to.

- exposing defaults in the read-resource operation - i personally would 
be more interested in what i configured, rather than static defaults. I 
do see why Ike wants the defaults in the result for the console - i'm 
just not sure if that should be the default view?

- A effective runtime model view sounds more like a completely separate 
topic/discussion.

On 08/01/2011 03:12 PM, Jason T. Greene wrote:
> On 7/29/11 6:42 AM, Heiko Braun wrote:
>>
>> IMO point 2 can be neglected. It's an edge case, if you ask me.
>>
>> The first point is no big deal. Verbosity or not. It's always better to
>> strive for
>> a simple, easy to grasp solution. I believe (as a consumer of that API)
>> that it should reflect the effective runtime model, no matter what.
>
> This is essentially unachievable when you have runtime properties
> evaluated on the server level. You would have to hit the server
> everytime which does not scale.
>
>
>> Including the defaults. Going through additional hoops&  loops to figure
>> out the effective runtime configuration is counter productive
>> (curl,bash, etc) and will not be used.
>>
>> Further more, consumer do not care if the attribute derives from a
>> default value or not.
>> And why should they?
>
> They care if they specified or they did not.
>
>> The fact that it's written back to xml, is an implementation detail to me.
>> But it should not mandate how the actually API works.
>
> It's simply wrong to store values the user did not specify, since the
> config represents their specification.
>