Re: [jboss-as7-dev] Default values in the model
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.
--
Jason T. Greene
JBoss, a division of Red Hat