>> I also think it's very confusing to users to not write out that
>> default value.
> the main problem with writing out the default value in the domain.xml is
> that if we decide that the default value should be changed between
> releases *and* we are dealing with an upgrade scenario then the user
> would retain the previous default value which was clearly not his intent.
That's right, but don't you think that a change in default value is a source
of incompatibility?
(It really boils down to whether our @Configured interfaces are our product
interfaces because default values are now in annotations on them).