Hi Nick,
This is somewhat confusing, and the naming of the attributes used in the
binding probably contributes to the confusion. The ns attribute needs to
give the actual namespace URI (as stated in the documentation on these
attributes:
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
Cheers Dennis - you're absolutely right, I just wasn't reading the element
description properly! :)
I had assumed that the ns attribute would take the name value defined in a
previous namespace element rather than needing the full uri to be restated. I
have no justification for this other than
Hello, is it possible to generate JIBX Client stubs easily without a mapping
file. We have an architecture where we are evaluating using JIBX as the
binding for services. For the sake of consistency we would like to use it
also for the SOAP clients , however it seems the client generation is not
Thanks for the reply, Dennis. I made the changes you suggested to my
bindings.xml, that seems to have fixed the previous issue but now I am
receiving another error:
[java] Running binding compiler version jibx_1_2_1
[java] Error running binding compiler
[java]
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
