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 "Surridge, Christopher S (Titan) @ TITAN" <ch...@L-3Com.com> on 2006/03/24 00:25:44 UTC

Displayed WSDL different from source WSDL in Axis2

I began with a WSDL file and used the WSDL2.sh script to generate stubs for my service. I managed to get an aar file built and deployed and the service now shows up on the list of available services. However, when I check the link to the WSDL for my service, it is not close to the WSDL I started with. Am I missing something in my aar file, or is there some configuration step I missed? The structure of my aar looks like:

META-INF\
	services.xml
com\
org\
lib\
	*.jar
resources\
	schemaorg_apache_xmlbeans\


The main difference between the WSDL files is that the source WSDL specifies simple types with restrictions and the resulting WSDL is missing the simple types. For example, if the source WSDL has:


   <simpleType name="queryType">
    <restriction base="xsd:string">
     <maxLength value="4096"/>
    </restriction>
   </simpleType>

   <element name="findMessages">
    <complexType>
     <sequence>
      <element name="query" type="impl:queryType"/>
     </sequence>
    </complexType>
   </element>

The resulting WSDL has a section like:

<xs:element type="ns1:FindMessagesDocument" name="FindMessagesDocument" />
<xs:complexType name="FindMessagesDocument">
<xs:sequence>
<xs:element type="ns1:FindMessagesDocument$FindMessages" name="FindMessages" />
</xs:sequence>
</xs:complexType>
<xs:element type="ns1:FindMessagesDocument$FindMessages" name="FindMessagesDocument$FindMessages" />
<xs:complexType name="FindMessagesDocument$FindMessages">
<xs:sequence />
</xs:complexType>

Thanks in advance,

Chris Surridge
Sr. Software Engineer
L-3 Titan Corporation
11955 Freedom Drive, Suite 14101
Reston, VA 20190
703-434-5307

Re: Displayed WSDL different from source WSDL in Axis2

Posted by Siamak Haschemi <si...@gmx.de>.
Hello Christopher.

As i remember you can add your own WSDL-file into the META-INF folder. 
Then Axis2 uses this one.
For you, your initial WSDL-file should be placed into the META-INF 
folder inside the *.aar package.

I hope that helps.

Thanks,

Siamak Haschemi

Surridge, Christopher S (Titan) @ TITAN schrieb:

>I began with a WSDL file and used the WSDL2.sh script to generate stubs for my service. I managed to get an aar file built and deployed and the service now shows up on the list of available services. However, when I check the link to the WSDL for my service, it is not close to the WSDL I started with. Am I missing something in my aar file, or is there some configuration step I missed? The structure of my aar looks like:
>
>META-INF\
>	services.xml
>com\
>org\
>lib\
>	*.jar
>resources\
>	schemaorg_apache_xmlbeans\
>
>
>The main difference between the WSDL files is that the source WSDL specifies simple types with restrictions and the resulting WSDL is missing the simple types. For example, if the source WSDL has:
>
>
>   <simpleType name="queryType">
>    <restriction base="xsd:string">
>     <maxLength value="4096"/>
>    </restriction>
>   </simpleType>
>
>   <element name="findMessages">
>    <complexType>
>     <sequence>
>      <element name="query" type="impl:queryType"/>
>     </sequence>
>    </complexType>
>   </element>
>
>The resulting WSDL has a section like:
>
><xs:element type="ns1:FindMessagesDocument" name="FindMessagesDocument" />
><xs:complexType name="FindMessagesDocument">
><xs:sequence>
><xs:element type="ns1:FindMessagesDocument$FindMessages" name="FindMessages" />
></xs:sequence>
></xs:complexType>
><xs:element type="ns1:FindMessagesDocument$FindMessages" name="FindMessagesDocument$FindMessages" />
><xs:complexType name="FindMessagesDocument$FindMessages">
><xs:sequence />
></xs:complexType>
>
>Thanks in advance,
>
>Chris Surridge
>Sr. Software Engineer
>L-3 Titan Corporation
>11955 Freedom Drive, Suite 14101
>Reston, VA 20190
>703-434-5307
>
>  
>