Discussion:
wsa10:EndPointReference not recognized and will be ignored
o771858
2010-05-17 16:26:50 UTC
Permalink
I have some WSDL, generated from Windows Communications Framework (WCF), that uses wsa10:EndPointReference. wsdl2h dislikes it and complains:

Warning: element 'wsa10:EndpointReference' at level 3 was not recognized and will be ignored

wsdl:definitions includes xmlns:wsa10="http://www.w3.org/2005/08/addressing"

Does the 2.7.17 open source edition of gSOAP support EndPointReference? If so, what issue would cause the error I'm seeing? If EndPointReference is unsupported, is there some workaround that permits use of WCF WSDL?

FWIW, MSDN says WS-Addressing in WCF always uses endpoint references, and the gSOAP UG says its interoperability with WCF has been verified.

I found a couple of threads reporting this problem, both from 2007, neither with any response. Has anyone used gSOAP on WSDL containing EndPointReference?

Thanks.



------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/gsoap/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/gsoap/join
(Yahoo! ID required)

<*> To change settings via email:
gsoap-digest-***@public.gmane.org
gsoap-fullfeatured-***@public.gmane.org

<*> To unsubscribe from this group, send an email to:
gsoap-unsubscribe-***@public.gmane.org

<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
Robert
2010-05-17 19:42:16 UTC
Permalink
The EndpointReference repeats the endpoint address with an additional information item. For example:

<wsdl:port name="WSHttpBinding_IService1" binding="tns:WSHttpBinding_IService1">
<soap12:address location="http://localhost:15219/Service1.svc/soap12" />
<wsa10:EndpointReference>
<wsa10:Address>http://localhost:15219/Service1.svc/soap12</wsa10:Address>
<Identity xmlns="http://schemas.xmlsoap.org/ws/2006/02/addressingidentity">
<Dns>localhost</Dns>
</Identity>
</wsa10:EndpointReference>
</wsdl:port>

The service location is repeated that gsoap already picked up and there is really no use for it. Also, sometimes this is used to enable SOAP 1.1/1.2 switching. The gsoap services and clients can already dynamically switch between SOAP 1.1 and 1.2 without the need to configure this.

If WS-Addressing is require, see doc/wsa. The need for WS-Addressing is usually indicates with WS-Policy or WSAM.

- Robert
Post by o771858
Warning: element 'wsa10:EndpointReference' at level 3 was not recognized and will be ignored
wsdl:definitions includes xmlns:wsa10="http://www.w3.org/2005/08/addressing"
Does the 2.7.17 open source edition of gSOAP support EndPointReference? If so, what issue would cause the error I'm seeing? If EndPointReference is unsupported, is there some workaround that permits use of WCF WSDL?
FWIW, MSDN says WS-Addressing in WCF always uses endpoint references, and the gSOAP UG says its interoperability with WCF has been verified.
I found a couple of threads reporting this problem, both from 2007, neither with any response. Has anyone used gSOAP on WSDL containing EndPointReference?
Thanks.
------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/gsoap/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/gsoap/join
(Yahoo! ID required)

<*> To change settings via email:
gsoap-digest-***@public.gmane.org
gsoap-fullfeatured-***@public.gmane.org

<*> To unsubscribe from this group, send an email to:
gsoap-unsubscribe-***@public.gmane.org

<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/

Loading...