To understand why the dates are getting off you'd need to look at the
actual XML being marshalled or unmarshalled. The format you give is that
used for the schema xs:dateTime type, which allows (but does not
require) a UTC offset. If the XML representation doesn't include UTC
offsets it could
Hi Glenn,
I don't know why load=true on the Ant task would cause a problem. Do
you have any more information about what went wrong?
Re the dateTime attributes, JiBX by default handles the conversions to
and from java.util.Date with some assumptions, which may or may not be
correct for your
Thanks for that Dennis,
I've since rewrote the binding from scratch. I think it may have had
something to do with the way I was handling the namespaces.
Without the date format declared, 24 hour time is mishandled. All dates
increase by 12 hours. The date format I'm currently using is
Found it.
The Ant task org.jibx.binding.ant.CompileTask had load=true. It came
in when copying an example. Removing it solved my problem.
Thanks anyway
--
Let Crystal Reports handle the reporting - Free Crystal Reports
Hi all,
I'm having a problem unmarshalling my request.
Using the binding below, I'm unable to access any unmarshallers. When on
UnmarshallingContext.getUnmarshaller(),
JiBX_BindingFactory.m_unmarshallers has only 3 null strings, while
m_unmarshalMap is an empty hashmap.
binding
