Hi Dennis,
Thanks for prompt response!
Here's the stack trace you asked for:
org.jibx.runtime.impl.UnmarshallingContext.toStart(UnmarshallingContext.java:489)
org.jibx.runtime.impl.UnmarshallingContext.parsePastStartTag(UnmarshallingContext.java:749)
Thanks for the trace. After looking at it I found a problem in the
handling of non-optional short values within the JiBX code. I'll get
this fixed in CVS today, but a quick workaround for now is to just make
the short value optional by giving it a default value that should never
be seen in
Falk Langhammer wrote:
Dennis Sosnoski wrote:
It's not as simple as it might appear, Falk. The issue is that JiBX
makes use of element ordering in combination with a pull parser to
improve unmarshalling performance. Because of this, JiBX always wants to
know what to expect next.
ok, I
