Error Loading WSDL Document

Posted by fmca143 on 11-Mar-2014 14:55

Hi, I have a problem. We used “OpenEdge Release 10.2A03” and We are trying consume a webservice of a provider. When trying connect to WSDL, We received the following error: 

“Error loading WSDL document.

http://192.168.222.35:8080/SmsDispatcher/SmsDispatcher?wsdl :

http://192.168.222.35:8080/SmsDispatcher/SmsDispatcher?xsd=
1:22: error: attribute ‘final’ cannot have a value of ‘extension

restriction’ as the expected values are

{‘#all’I’extension’I’restriction’} on top-level ‘xs:complexType’

Declaration (11748)”

 And we can’t connect to webservice.

Please, I need your help.

Thanks

Community Groups - Forum

All Replies

Posted by Donicello Lampe on 12-Mar-2014 08:47

In order to help we would need access to the WSDL document and its related XSD files. Are you able to process the WSDL document from another client, for example soapUI ?

Posted by fmca143 on 12-Mar-2014 09:36

 
Hi, Thanks for your help.
 
I can process other client without problem. In this case, the problem is in the attribute "final='extension restriction'" registered in WSLD. I don´t know how resolve this error and consume the webservice as I have done for others cases.
 
I am pasting the WSLD text information in this mail.
 
/******* WSDL ******/
 
<!--
 Published by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is Metro/2.1.1-b09 (branches/2.1-6834; 2011-07-16T17:14:48+0000) JAXWS-RI/2.2.5-promoted-b04 JAXWS/2.2.
-->
<!--
 Generated by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is Metro/2.1.1-b09 (branches/2.1-6834; 2011-07-16T17:14:48+0000) JAXWS-RI/2.2.5-promoted-b04 JAXWS/2.2.
-->
<definitions xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsp="http://www.w3.org/ns/ws-policy"xmlns:wsp1_2="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata"xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://sms.totaltexto.com/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://sms.totaltexto.com/" name="SmsDispatcher">
<types>
<xsd:schema>
<xsd:import namespace="http://sms.totaltexto.com/" schemaLocation="http://192.168.222.35:8080/SmsDispatcher/SmsDispatcher?xsd=1"/>
</xsd:schema>
</types>
<message name="send">
<part name="parameters" element="tns:send"/>
</message>
<message name="sendResponse">
<part name="parameters" element="tns:sendResponse"/>
</message>
<portType name="SmsDispatcher">
<operation name="send">
<input wsam:Action="http://sms.totaltexto.com/SmsDispatcher/sendRequest" message="tns:send"/>
<output wsam:Action="http://sms.totaltexto.com/SmsDispatcher/sendResponse" message="tns:sendResponse"/>
</operation>
</portType>
<binding name="SmsDispatcherPortBinding" type="tns:SmsDispatcher">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<operation name="send">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="SmsDispatcher">
<port name="SmsDispatcherPort" binding="tns:SmsDispatcherPortBinding">
<soap:address location="http://192.168.222.35:8080/SmsDispatcher/SmsDispatcher"/>
</port>
</service>
</definitions>
 
/*******           ******/
 
/******* portType name="SmsDispatcher" operation name="send" ******/
 
 
 
Published by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is Metro/2.1.1-b09 (branches/2.1-6834; 2011-07-16T17:14:48+0000) JAXWS-RI/2.2.5-promoted-b04 JAXWS/2.2.
-->
<xs:schema xmlns:tns="http://sms.totaltexto.com/" xmlns:xs="http://www.w3.org/2001/XMLSchema" version="1.0" targetNamespace="http://sms.totaltexto.com/">
<xs:element name="send" type="tns:send"/>
<xs:element name="sendResponse" type="tns:sendResponse"/>
<xs:complexType name="send">
<xs:sequence>
<xs:element name="id" type="xs:string" minOccurs="0"/>
<xs:element name="key" type="xs:string" minOccurs="0"/>
<xs:element name="addr" type="xs:string" minOccurs="0"/>
<xs:element name="text" type="xs:string" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="sendResponse">
<xs:sequence>
<xs:element name="return" type="tns:result" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="result" final="extension restriction">
<xs:sequence>
<xs:element name="codError" type="xs:string" minOccurs="0"/>
<xs:element name="desError" type="xs:string" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
 
/*******           ******/
 
 
 
I hope I can help me.
 
Regards
 
Saludos!!!
 
Atentamente
Francisco M. Coello A.
Gerencia de Informática
Jefe Dpto. de Sistemas
UNITICKET... Único para todos.
Telf. 0212-8210000
Logo-UniticketRIF
 
De: Donicello Lampe [mailto:bounce-dlampe@community.progress.com]
Enviado el: miércoles, 12 de marzo de 2014 9:18
Para: TU.General@community.progress.com
Asunto: RE: Error Loading WSDL Document
 
RE: Error Loading WSDL Document
Reply by Donicello Lampe

In order to help we would need access to the WSDL document and its related XSD files. Are you able to process the WSDL document from another client, for example soapUI ?

Stop receiving emails on this subject.

Flag this post as spam/abuse.

Posted by fmca143 on 12-Mar-2014 10:02

Hello, Thanks for your help. I can process other client without problem. In this case, the problem is in the attribute "final='extension restriction'" registered in WSLD. I don´t know how resolve this error and consume the webservice as I have done for others cases.
 
I am pasting the WSLD text information in this mail.
 
/*******WSDL******/
 
<!--
 Published by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is Metro/2.1.1-b09 (branches/2.1-6834; 2011-07-16T17:14:48+0000) JAXWS-RI/2.2.5-promoted-b04 JAXWS/2.2.
-->
<!--
 Generated by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is Metro/2.1.1-b09 (branches/2.1-6834; 2011-07-16T17:14:48+0000) JAXWS-RI/2.2.5-promoted-b04 JAXWS/2.2.
-->
<definitions xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsp="http://www.w3.org/ns/ws-policy"xmlns:wsp1_2="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata"xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://sms.totaltexto.com/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://sms.totaltexto.com/" name="SmsDispatcher">
<types>
<xsd:schema>
<xsd:import namespace="http://sms.totaltexto.com/" schemaLocation="http://192.168.222.35:8080/SmsDispatcher/SmsDispatcher?xsd=1"/>
</xsd:schema>
</types>
<message name="send">
<part name="parameters" element="tns:send"/>
</message>
<message name="sendResponse">
<part name="parameters" element="tns:sendResponse"/>
</message>
<portType name="SmsDispatcher">
<operation name="send">
<input wsam:Action="http://sms.totaltexto.com/SmsDispatcher/sendRequest" message="tns:send"/>
<output wsam:Action="http://sms.totaltexto.com/SmsDispatcher/sendResponse" message="tns:sendResponse"/>
</operation>
</portType>
<binding name="SmsDispatcherPortBinding" type="tns:SmsDispatcher">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<operation name="send">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="SmsDispatcher">
<port name="SmsDispatcherPort" binding="tns:SmsDispatcherPortBinding">
<soap:address location="http://192.168.222.35:8080/SmsDispatcher/SmsDispatcher"/>
</port>
</service>
</definitions>
 
/*******           ******/ 
/*******portType name="SmsDispatcher" operation name="send"******/
 
Published by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is Metro/2.1.1-b09 (branches/2.1-6834; 2011-07-16T17:14:48+0000) JAXWS-RI/2.2.5-promoted-b04 JAXWS/2.2.
-->
<xs:schema xmlns:tns="http://sms.totaltexto.com/" xmlns:xs="http://www.w3.org/2001/XMLSchema" version="1.0" targetNamespace="http://sms.totaltexto.com/">
<xs:element name="send" type="tns:send"/>
<xs:element name="sendResponse" type="tns:sendResponse"/>
<xs:complexType name="send">
<xs:sequence>
<xs:element name="id" type="xs:string" minOccurs="0"/>
<xs:element name="key" type="xs:string" minOccurs="0"/>
<xs:element name="addr" type="xs:string" minOccurs="0"/>
<xs:element name="text" type="xs:string" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="sendResponse">
<xs:sequence>
<xs:element name="return" type="tns:result" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="result" final="extension restriction">
<xs:sequence>
<xs:element name="codError" type="xs:string" minOccurs="0"/>
<xs:element name="desError" type="xs:string" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
 
/*******           ******/
 
I hope I can help me.
 
Regards!!!
 
Atentamente
Francisco M. Coello A.
Gerencia de Informática
Jefe Dpto. de Sistemas
 
De: Donicello Lampe [mailto:bounce-dlampe@community.progress.com]
Enviado el: miércoles, 12 de marzo de 2014 9:18
Para: TU.General@community.progress.com
Asunto: RE: Error Loading WSDL Document
 
RE: Error Loading WSDL Document
Reply by Donicello Lampe

In order to help we would need access to the WSDL document and its related XSD files. Are you able to process the WSDL document from another client, for example soapUI ?

Stop receiving emails on this subject.

Flag this post as spam/abuse.

Posted by David Cleary on 12-Mar-2014 14:50

This could be a bug in the version of Xerces used in 10.2A. I found this exact issue in the bug list for the Java version of Xerces, but not in the C++ version. A quick test would be to run the wsdl/schema through OE 11.2 or later which is using Xerces 3.3 to see if it goes away.

Posted by fmca143 on 12-Mar-2014 16:02

Excelent idea. We'll update to OE 11.2 version. And we'll test.
 
Thanks for your help.
 
Regards!!!
 
Atentamente
Francisco M. Coello A.
Gerencia de Informática
Jefe Dpto. de Sistemas
UNITICKET... Único para todos.
Telf. +582128210000
Logo-UniticketRIF
 
De: davec [mailto:bounce-davec@community.progress.com]
Enviado el: miércoles, 12 de marzo de 2014 15:20
Para: TU.General@community.progress.com
Asunto: RE: Error Loading WSDL Document
 
RE: Error Loading WSDL Document
Reply by davec

This could be a bug in the version of Xerces used in 10.2A. I found this exact issue in the bug list for the Java version of Xerces, but not in the C++ version. A quick test would be to run the wsdl/schema through OE 11.2 or later which is using Xerces 3.3 to see if it goes away.

Stop receiving emails on this subject.

Flag this post as spam/abuse.

Posted by fmca143 on 13-Mar-2014 14:00

Excelent idea. We'll update to OE 11.2 version. And we'll test.
 
Thanks for your help.
 
Regards!!!
 
Atentamente
Francisco M. Coello A.
Gerencia de Informática
Jefe Dpto. de Sistemas
UNITICKET... Único para todos.
Telf. +582128210000
Logo-UniticketRIF
 
De: davec [mailto:bounce-davec@community.progress.com]
Enviado el: miércoles, 12 de marzo de 2014 15:20
Para: TU.General@community.progress.com
Asunto: RE: Error Loading WSDL Document
 
RE: Error Loading WSDL Document
Reply by davec

This could be a bug in the version of Xerces used in 10.2A. I found this exact issue in the bug list for the Java version of Xerces, but not in the C++ version. A quick test would be to run the wsdl/schema through OE 11.2 or later which is using Xerces 3.3 to see if it goes away.

Stop receiving emails on this subject.

Flag this post as spam/abuse.

Posted by Donicello Lampe on 14-Mar-2014 10:07

I just tested this in 11.3.1 and the issue still exists. So I suggest you open a Support case to get this issue fixed.

This thread is closed