Hello,
I'm trying (currently unsuccessfully :-( to integrate BindingSelector into
my project, to support a smart migration from one binding version to another
(the java classes did not change, that's just the way the xml is produced
that has evolved).
For that, I'm reading the existing xml files in the version they declare to
be written is, but when time comes to write them back to files, I
systematically force the version to the newest.
I have one problem I would like to submit to your sagacity, as well as one
question:
* The problem
The unmarshalling part works well, choosing the right binding from the
version taken from a custom attribute in the root binding.
the marshalling part fails because in the marshalled file, my custom version
attribute appears twice.
I have looked at my bindings over and over, without being able to see where
I'm wrong.
It may even not be related to binding versioning, I'm not sure.
* The question
The current solution - with BindingSelector - forces the java model to have
at least a "version" field.
What I would like is to manage the "binding version resolution" stuff
outside my java model, and not introduce a field just for the needs of
serialization.
So I would like to be able to add the custom "version" attribute of the root
element at the very last moment.
I'm not sure if and how it could be possible. But this certainly would be
interesting !
Thanks in advance,
--
Laurent
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
jibx-users mailing list
jibx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-users
