I've been looking at the messages that generated clients from different
systems
produce for a WSDL file I wrote. The WSDL file (see attached file)
contains 8 different operations whose soap binding uses different
variants
of style and use, along with message parts that use type and element.
That
I hope this is the right list to report bugs to...
I took an Axis generated wsdl file (see attachment) from the stock sample
and removed the style attribute from the soap:binding element (all the
soap:operation elements include a style). This gets a NPE from WSDL2Java
with the stack trace:
ja
