On 2/5/06, Yu-Hui Jin <[EMAIL PROTECTED]> wrote:
Hmm.. We do process messages with the type attribute and if a nullpointer is thrown it's definitely a bug.
we do not generate code for rpc/encoded and that's the only restriction you'll have to bear in mind.
Yes, that is definitely a feature we are thinking of providing. BTW if you can attach the WSDL that caused a nullpointer it'll be helpful for us to figure out the issue.
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.
Hmm.. We do process messages with the type attribute and if a nullpointer is thrown it's definitely a bug.
Are there any other non-supported features in WSDL 1.1. that we should be aware of ??
we do not generate code for rpc/encoded and that's the only restriction you'll have to bear in mind.
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.
Yes, that is definitely a feature we are thinking of providing. BTW if you can attach the WSDL that caused a nullpointer it'll be helpful for us to figure out the issue.
regards,
-Hui
--
Ajith Ranabahu
