Jacob Lauemøller wrote:
> But it's unfortunate (IMHO) and somewhat clumsy that I either
> have to add this annotation to every element that has a minOccurs="0"
> constraint (and this will only work well, by the way, when I control the
> schema file) or add it at the schema level (e.g in a JAXB binding file) and
> live with the fact that I then end up with isSetXXX, unsetXXX methods on
> properties that are always set and cannot be unset (because their minOccurs
> constraint is 1 or greater).
I agree. It's clumsy. The problem for me is that when something is a
spec-specified behavior, the RI can't really change it on its own. Plus,
we care for the compatibility, and changing the signature of the
generated code will break existing clients.
But I think this is a great input toward 2.0.
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
For additional commands, e-mail: users-help_at_jaxb.dev.java.net