> In 2.0, XJC will be able to just generate value classes, so there won't
> be any casting between your class and interfaces. Also, in 2.0, you can
> have XJC generate the code once, move that into the repository, and then
> you can start making modifications to the generated classes directly.
Does this mean that if the schema changes (than the code will change) and
then I have lost all my modifications?
I'm using the following very simple code-preserving-technic when working with
ORM (Object/Relational Mapping) tools:
I let the ORM create an Class gti.conf.EquipmentEntity, but when it creates
the class-file I prepend "generated" before the className.
So now generated/gti/conf/EquipmentEntity.java is generated. I now have to create
a the class-file gti/conf/EquipmentEntity.java myself (with empty constructor).
In this class-file I can append my modifications without ever getting it lost.
Is this possible in jaxb 1.0?
or jaxb 2.0?
> So
> when this kind of problems come up, instead of learning a new
> customization, you can just go ahead and change the signature of the
> generated code and it will still work.
Is there any documentation on this? Can you give me a pointer?
If jaxb will solve all my current casting/typesafe problems in 2.0 then
I will surely go ahead with it.
Kees.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
For additional commands, e-mail: users-help_at_jaxb.dev.java.net