Hello All,
Is it a bug in Axis1.3 that WSDL with nillable="false" and
minOccurs="0", still genrates a nilable="true" string on serialisation?
Is there somewhere I can log this bug or enhancement?
I may be able to do this in work time. Where would I start with Axis1.3
to add/alter the code to deal with this? WSDL2Java mainly generates
beans and a few other files. How would the code to analyse the presence
of nillable="true" in the schema and the unmarshalling of message
objects fit together in the axis framework? some sort of variable set in
the beans to indicate nillable should not be sent that is inspected on
serilaisation; or some extracted supporting object that contains such
information? Would this be a fairly simple task?
Thanks for you time,
Tim
