Werner,
but if we keep that switch we won't be able to deprecate/remove the
static methods on marshaller/unmarshaller which cause more problems then
those on generated code.
IMHO removing the static methods on generated code could only be a step
to also remove those of (un)marshaller.
Ralf
Werner Guttmann schrieb:
Claudio,
Can I (safely) assume that you know that you can turn off generation of
these methods already now ? In other words, we might change the default
value of the property in question so that these methods won't be
generated in the future anymore. If you still want them, yo can get them
by asking for them specifically.
Werner
Claudio Di Vita wrote:
Werner Guttmann ha scritto:
Hi,
we (committers) are currently thinking about deprecating (and
eventually) removing all the static (un-)marshal() methods on classes as
generated using the Castor XML code generator.
The reason for this is simple: we'd like people to use explicit
(Un-)Marshaller instances as there's been a lot of confusion around
usage of mapping files and static methods.
As it is very hard to get one's head around the impact of this change,
I'd like to hear from you, the users, what you think about this change.
As always, if there's no feedback, we consider this suggested change as
acceptable and will continue going about an implementation.
You are right, those static methods generates a lot of confusion.
Moreover I hope that who use the classes generated with the Castor XML
code generator instantiates explicitly a (Un) Marshaller.
Best regards,
Claudio
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
