You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-user@axis.apache.org by Daniel Beland <da...@rdketchup.com> on 2005/03/16 19:03:45 UTC

xsd:any element not in the generated wsdl


Hi,

I try to generate java code from a wsdl with the following complexType:

<complexType name="xmlData">
  <sequence>
    <any namespace="##any" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/>
  </sequence>
</complexType>

wsdl2java generates the XmlData class correctly with a single field    
private org.apache.axis.message.MessageElement [] _any;

But when I install this on tomcat and look at the wsdl generated by Axis,
the xmlData complexType now looks like this:

<complexType name="xmlData">
  <sequence/>
</complexType>


Now I cannot validate my client against the wsdl, because it says that the
complexType xmlData doesn't have a child element. Is this a bug or is
there a special serializer to use instead of BeanSerializer, or am I doing
something wrong?

I tried a lot of things but I'm stuck so any help would be appreciated.

Thanks,
Daniel

Re: xsd:any element not in the generated wsdl

Posted by Davanum Srinivas <da...@gmail.com>.

this is a bug. please report it.

thx,
dims


On Wed, 16 Mar 2005 18:03:45 -0000 (GMT), Daniel Beland
<da...@rdketchup.com> wrote:
> 
> 
> Hi,
> 
> I try to generate java code from a wsdl with the following complexType:
> 
> <complexType name="xmlData">
>   <sequence>
>     <any namespace="##any" processContents="lax" minOccurs="0"
> maxOccurs="unbounded"/>
>   </sequence>
> </complexType>
> 
> wsdl2java generates the XmlData class correctly with a single field
> private org.apache.axis.message.MessageElement [] _any;
> 
> But when I install this on tomcat and look at the wsdl generated by Axis,
> the xmlData complexType now looks like this:
> 
> <complexType name="xmlData">
>   <sequence/>
> </complexType>
> 
> Now I cannot validate my client against the wsdl, because it says that the
> complexType xmlData doesn't have a child element. Is this a bug or is
> there a special serializer to use instead of BeanSerializer, or am I doing
> something wrong?
> 
> I tried a lot of things but I'm stuck so any help would be appreciated.
> 
> Thanks,
> Daniel
> 
> 


-- 
Davanum Srinivas - http://webservices.apache.org/~dims/