Hi - I am evaluating jibx as a potential replacement for some of our
homegrown xml serialization code and I had a question... Say I have a
class that I want to define a binding for:
class A {
B b
String name;
}
and say that class 'B' is defined in a separate package that is built
separately from class 'A'.
With my first stab at defining a binding for 'A', jibx wants to modify
the bytecodes for 'B', which is a bit of a pain cause that would require
changes to the way 'B' is packaged and built. Are there ways to do this
without affecting the bytecodes for 'B'? I guess I could create a
subclass of 'B' in the same package as 'A' and let jibx muck with those
bytecodes, but that's ugly enough to get me to stay with the existing
serialization code (as is mucking with the build process). Is there
something obvious that I am missing?
Thanks,
Paul
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
jibx-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jibx-users
