No answers? Should I start getting worried ;-) ?
Regards,
Massimiliano
On Fri, Oct 1, 2010 at 16:54, Massimiliano Ziccardi <
[email protected]> wrote:
> Hi Glen.
>
> Thank you for your answer.
>
> Actually, I temporarily solved the issue with the same fix you proposed.
>
> However,
Hi Glen.
Thank you for your answer.
Actually, I temporarily solved the issue with the same fix you proposed.
However, the wsdl is published automatically by axis2 (http://myuri?wsdl),
so my question is: what can I do to make axis publish the wsdl so that
opDate will be nullable?
Thanks a lot,
M
Hi Massimiliano,
Axis2 is just being a bit more strict about schema compliance than Axis1 was
- you have actually indicated in your schema that opDate is required.
Try , which
indicates to the parser that the element may or may not appear. This should
allow the generated code to accept nulls.
-
