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 Lorenzo Carnevale <lo...@innovery.it> on 2009/09/11 16:45:38 UTC

Generated WSDL has wrong "types"

Sorry, I have yet another problem.
I have to add the policy tags to the wsdl, so I use USEORIGINALWSDL to 
false... the resulting WSDL copies the policy tags correctly from 
SERVICES.XML, but the original 'types' of the input and output elements 
disappered...

Origianl WSDL :

<element name="ExecuteSelectResponse">
    <complexType>
        <sequence>
            <element name="Result" minOccurs="0" type="tse:selectResponse" 
/>
        </sequence>
    </complexType>
</element>

<complexType name="selectResponse">
    <sequence>
        <element name="response" type="xsd:int" />
        <element name="xmlResponse" type="xsd:base64Binary" />
        <element name="message" type="xsd:string" />
    </sequence>
</complexType>

Generated WSDL:

 <xs:element name="ExecuteSelectResponse">
                <xs:complexType>
                    <xs:sequence>
                        <xs:element minOccurs="0" name="return" 
nillable="true" type="xs:anyType"/>
                    </xs:sequence>
                </xs:complexType>
            </xs:element>

So the usual 'wizards' that build clients from WSDLs can't really guess 
what's going on.
Thanks
              Lorenzo

Re: Generated WSDL has wrong "types"

Posted by Amila Suriarachchi <am...@gmail.com>.

On Fri, Sep 11, 2009 at 8:15 PM, Lorenzo Carnevale <
lorenzo.carnevale@innovery.it> wrote:

> Sorry, I have yet another problem.
> I have to add the policy tags to the wsdl, so I use USEORIGINALWSDL to
> false... the resulting WSDL copies the policy tags correctly from
> SERVICES.XML, but the original 'types' of the input and output elements
> disappered...
>

try to add the policy to relavent place in wsdl file instead of adding them
to services.xml.

thanks,
Amila.

>
> Origianl WSDL :
>
> <element name="ExecuteSelectResponse">
>   <complexType>
>       <sequence>
>           <element name="Result" minOccurs="0" type="tse:selectResponse" />
>       </sequence>
>   </complexType>
> </element>
>
> <complexType name="selectResponse">
>   <sequence>
>       <element name="response" type="xsd:int" />
>       <element name="xmlResponse" type="xsd:base64Binary" />
>       <element name="message" type="xsd:string" />
>   </sequence>
> </complexType>
>
> Generated WSDL:
>
> <xs:element name="ExecuteSelectResponse">
>               <xs:complexType>
>                   <xs:sequence>
>                       <xs:element minOccurs="0" name="return"
> nillable="true" type="xs:anyType"/>
>                   </xs:sequence>
>               </xs:complexType>
>           </xs:element>
>
> So the usual 'wizards' that build clients from WSDLs can't really guess
> what's going on.
> Thanks
>             Lorenzo
>



-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/