Hi Eitan,
The implementation I supplied assumes the version information will be
included in the binding. That does seem unnecessary, given that the
BindingSelector has to have the attribute information anyway. So I guess
it's "by oversight". ;-)
- Dennis
Eitan Suez wrote:
hi all,
i'm not sure whether this is by design or not (or whether i'm
mistaken altogether):
using the binding selector,
the implementation of marshalVersioned does not appear to be
writing out the version number (using m_attributeName) when
marshalling. or does the version information have to be specified
in the binding file?
thanks, eitan
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
_______________________________________________
jibx-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jibx-users
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
jibx-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jibx-users
