On 7/28/2011 5:17 AM, Seref Arikan wrote:
> Greetings,
> I've asked this before, and maybe I failed to describe the problem I'm
> having, so I'll give it another go.
> I have a set of classes generated from XSD using JiBX. I fill in the
> values, and I can see in the debugger that all fields are set
> properly, just before I serialize the root object to XML.
> The result XML is incomplete, with only a few fields serialized to
> XML. No exceptions, no errors.
> I'd like to debug the serialization process to see what is failing,
> but since the code that serializes to XML is added to bytecode, I
> can't do it in the usual way of attaching source code to Java classes.
> Is there a way of debugging this process? Has anyone encountered
> something like this?
>
Long ago I encountered a similar problem. Usually this occurred because
of a
mismatch between the binding description and the classes used for
serialization.
And you are correct, the exception handling for this case isn't as good as it
should be.
The way I resolved this was unit testing a serialization /
de-serialization
loop and comparing the start and end objects. Since I wasn't as good about
maintaining my unit tests, I spent a lot of time working through the mapping
xml
ever time I did a refactoring.
--
Thomas Jones-Low Softstart Services Inc.
tjone...@softstart.com JobScheduler for Oracle
P: 802-398-1012 http://www.softstart.com
------------------------------------------------------------------------------
Got Input? Slashdot Needs You.
Take our quick survey online. Come on, we don't ask for help often.
Plus, you'll get a chance to win $100 to spend on ThinkGeek.
http://p.sf.net/sfu/slashdot-survey
_______________________________________________
jibx-users mailing list
jibx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-users
