I switched to use "document" style and @type. The codegen is done without exceptions. However, my eclipse, after compiling the code, says the "org.apache.axis2.om.OMElement.MY_QNAME" could not be found in the following line of code:
(org.apache.axis2.om.OMAbstractFactory.getOMFactory(), param.getPullParser(org.apache.axis2.om.OMElement.MY_QNAME));
Using @element does not cause the problem. Eclipse compiles fine in that case.
thanks,
-Hui
On 2/6/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
Note that @type is allowed in the <wsdl:part> definition only when using RPC style. If you are using document style, then you must specify @element instead.
AnneOn 2/5/06, Yu-Hui Jin <[EMAIL PROTECTED]> wrote:
I noticed that the code generator WSDL2Java for Axis can't take some of the allowable syntax in WSDL 1.1.
In WSDL 1.1. spec, the "type" is allowed in a message body:
<message name="GetItemByIdRequest">
<part name="GetItemByIdParam" type="xs:string"/>
</message>
However, WSDL2Java throws NullPointerException on this. I had to define an element ItemId of "xs:string" in the <wsdl:types> section, then use that element instead.
Are there any other non-supported features in WSDL 1.1. that we should be aware of ??
BTW, another suggestion is if the code generator could be made more intelligent, that it'll report the specific syntax error on the line of the WSDL, that'll make our life a whole lot easier. Making WSDL 2 Java generation work and compilable is a very demanding and painful job.
regards,
-Hui
