Hello
John,
attached you find a complete
example.
Greetings
Franz
-----Ursprüngliche Nachricht-----
Von: John Hawkins [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 10. November 2005 14:42
An: Franz Fehringer
Cc: Apache AXIS C Developers List
Betreff: Re: AW: wsdl2ws strange warnings and results
Hi,
can you give me more context on where this element is please. We can't see why this as it stands would fail. Can you give us the complete wsdl - or at least the snippet that contains where it is.
"Franz Fehringer" <[EMAIL PROTECTED]> 10/11/2005 09:33
John Hawkins/UK/[EMAIL PROTECTED], "Apache AXIS C Developers List" <[email protected]> AW: wsdl2ws strange warnings and results
Hello John,
The problem is that wsdl2ws cannot cope with element tags without type attributes.
So instead of
<xsd:element name="ErrorResponse">
<xsd:annotation>
<xsd:documentation>Describes any errors that occur during system operation.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Error" type="t_Error" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
i have to write
<xsd:element name="ErrorResponse" type="t_ErrorResponse">
<xsd:annotation>
<xsd:documentation>Describes any errors that occur during system operation.</xsd:documentation>
</xsd:annotation>
</xsd:element>
with an appropriate type definition of t_ErrorResponse.
wsdl2java does not suffer from this problem, but in this special case generates Java code with invalid throw declarations
(the throw declaration says that a t_Error[] can be thrown which doesn't compile because arrays are not Throwables).
regards
Franz
-----Ursprüngliche Nachricht-----
Von: John Hawkins [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 9. November 2005 09:47
An: Apache AXIS C Developers List
Betreff: Re: wsdl2ws strange warnings and results
Hi Franz,
the "ignoring anonymous type" message is to be ignored by you too. This is normal and it means that we are not going to create a seperate class for this type. The naming convention is the way WSDL2Ws understands this logic. (I'm just about to remove this message as we've had many people asking about it !)
Now, the fact that you're getting the ">" in source too will be a bug. It could be that you have refs in your wsdl - which aren't supported yet (I'm literally looking into this now) Or, some other bug. If you look at your wsdl and the types that have the ">" in front of them you should be able to see what's different about them compared to the others which appear to work OK. Is your WSDL RPC or doc/literal ?
"Franz Fehringer" <[EMAIL PROTECTED]> 08/11/2005 14:46
"Apache AXIS C Developers List"
"Apache AXIS C Developers List" <[email protected]> wsdl2ws strange warnings and results
Hello,
I get strange warnings and class definitions in using wsdl2ws.
My Axis (C/C++) version is 1.5.
I execute java -cp "%AXISCCLASSPATH%;%CLASSPATH%"
org.apache.axis.wsdl.wsdl2ws.WSDL2Ws -ocpp -lc++ -mgnu -sclient
PegsTour.wsdl
(files are attached).
The warnings are
ignoring anonymous type >ErrorResponse
ignoring anonymous type >_LoginRequest_Expiry
ignoring anonymous type >_LoginResponse_Expiry
ignoring anonymous type >LoginResponse
ignoring anonymous type >LoginRequest
ignoring anonymous type >t_Warning_Description
ignoring anonymous type >_LoginResponse_SessionToken
Note the spurious greaterthan sign in front.
This gt sign also spoils the generated sources, for example
class >t_Warning_Description;
What is wrong?
Thanks in advance
Franz
Dr. Franz Fehringer (Dipl. Math.)
____________________________________
ISO Software Systeme
Eichendorffstrasse 29
90491 Nuremberg
Germany
Tel. : +49/(911) - 99594-0
Fax : +49/(911) - 99594-580
mailto:[EMAIL PROTECTED]
http://www.isogmbh.de
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <definitions xmlns="http://schemas.xmlsoap.org/wsdl/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:fo="http://www.w3.org/1999/XSL/Format"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:pgs="http://www.pegs-pegstour.com/API/XMLSchema/1.0.1"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; name="PegsTour" targetNamespace="http://www.pegs-pegstour.com/API/XMLSchema/1.0.1"; xsi:schemaLocation="http://schemas.xmlsoap.org/wsdl/ http://schemas.xmlsoap.org/wsdl/";> <types> <xsd:schema targetNamespace="http://www.pegs-pegstour.com/API/XMLSchema/1.0.1";> <xsd:include schemaLocation="durchstich.xsd"/> </xsd:schema> </types> <!--MESSAGES--> <!--Common Messages--> <message name="TokenRequestMessage"> <part name="parameters" element="pgs:Token"/> </message> <message name="TokenResponseMessage"> <part name="parameters" element="pgs:TokenResponse"/> </message> <message name="ErrorResponseMessage"> <part name="parameters" element="pgs:ErrorResponse"/> </message> <!--SessionManagement Messages--> <message name="LoginRequestMessage"> <part name="parameters" element="pgs:LoginRequest"/> </message> <message name="LoginResponseMessage"> <part name="results" element="pgs:LoginResponse"/> </message> <!--PORT TYPES--> <portType name="SessionManagementPortType"> <operation name="Login"> <input message="pgs:LoginRequestMessage"/> <output message="pgs:LoginResponseMessage"/> <fault name="LoginFault" message="pgs:ErrorResponseMessage"/> </operation> </portType> <!--BINDINGS--> <binding name="SessionManagementBinding" type="pgs:SessionManagementPortType"> <soap:binding transport="http://schemas.xmlsoap.org/soap/http"; style="document"/> <operation name="Login"> <soap:operation soapAction="#Login"/> <input> <soap:body use="literal"/> </input> <output> <soap:body use="literal"/> <soap:header message="pgs:TokenResponseMessage" part="parameters" use="literal"/> </output> <fault name="LoginFault"> <soap:fault use="literal" name="LoginFault"/> </fault> </operation> </binding> <!--SERVICES--> <service name="PegsTourService"> <port name="SessionManagementPort" binding="pgs:SessionManagementBinding"> <soap:address location="https://prod.pegstour.com/api/soap/"/> </port> </service> </definitions>
durchstich.xsd
Description: application/xml
