ESB provides Invalid WSDL (sample 150)

Home » Forums » Project: WSO2 Enterprise Service Bus (WSO2 ESB)
thygesen's picture
Submitted by thygesen on November 8, 2008 - 09:27
I setup sample 150: Introduction to proxy services Opened the wsdl from http://localhost:8280/soap/StockQuoteProxy?wsdl in Altova XmlSpy. Xmlspy automatically validated the wsdl. This is the error message: File http://localhost:8280/soap/StockQuoteProxy?wsdl is not valid. Attribute ‘part’ in extensibility element ‘’ refers to part ‘getQuote’ wich could not be found in message ‘getQuoteMessage’ I also tried to have Visual Studio 2008 generate a proxy client class for the service. (kind a like wsdl2java but this is for C#). It also gave me errors and could not generate class from the wsdl. Custom tool warning: Cannot import wsdl:port Detail: The '/' character, hexadecimal value 0x2F, cannot be included in a name. Parameter name: name XPath to Error Source: //wsdl:definitions[@targetNamespace='http://services.samples']/wsdl:service[@name='StockQuoteProxy']/wsdl:port[@name='StockQuoteProxyAdmin/httpsSoap11Endpoint'] Detail: The '/' character, hexadecimal value 0x2F, cannot be included in a name. Parameter name: name XPath to Error Source: //wsdl:definitions[@targetNamespace='http://services.samples']/wsdl:service[@name='StockQuoteProxy']/wsdl:port[@name='StockQuoteProxyAdmin/httpsSoap12Endpoint'] Detail: The required WSDL extension element 'binding' from namespace 'http://schemas.xmlsoap.org/wsdl/http/' was not handled. XPath to Error Source: //wsdl:definitions[@targetNamespace='http://services.samples']/wsdl:binding[@name='StockQuoteProxyHttpBinding'] Detail: There was an error importing a wsdl:binding that the wsdl:port is dependent on. XPath to wsdl:binding: //wsdl:definitions[@targetNamespace='http://services.samples']/wsdl:binding[@name='StockQuoteProxyHttpBinding'] XPath to Error Source: //wsdl:definitions[@targetNamespace='http://services.samples']/wsdl:service[@name='StockQuoteProxy']/wsdl:port[@name='StockQuoteProxyHttpEndpoint'] Detail: There was an error importing a wsdl:binding that the wsdl:port is dependent on. XPath to wsdl:binding: //wsdl:definitions[@targetNamespace='http://services.samples']/wsdl:binding[@name='StockQuoteProxyHttpBinding'] XPath to Error Source: //wsdl:definitions[@targetNamespace='http://services.samples']/wsdl:service[@name='StockQuoteProxy']/wsdl:port[@name='StockQuoteProxyHttpsEndpoint'] This is very annoying.. brgds Peter Thygesen
‹ how to set up wso2 esb in eclipse? Independent Registry Administration ›
asankha's picture

Hi Peter I think the problem

Submitted by asankha on November 9, 2008 - 08:54.
Hi Peter I think the problem resulted in us shipping a slightly outdated WSDL with the sample.. To workaround this, first you can make the sample service (i.e. SimpleStockQuoteService) generate its own WSDL correctly (by deleting the line that reads as ".. copy file="wsdl/SimpleStockQuoteService.wsdl..." from the build.xml file at samples/axis2Server/src/SimpleStockQuoteService and re-run ant from there to build the service again) Now, update your sample configuration 150 to use the WSDL from http://localhost:9000/soap/SimpleStockQuoteService?WSDL instead of the one we've shipped on the file system This should work correctly for now, and would be corrected in the next release asankha http://esbmagic.blogspot.com
indika's picture

Re: ESB provides Invalid WSDL (sample 150)

Submitted by indika on November 9, 2008 - 09:30.
Hi I have validated ‘wsdl’ using [1] and [2]. Those tools successfully loaded wsdl and showed operations, port, etc...   BTW, it seems ports generated for the ESB admin console https binding contains a ‘/’ character inside its name attribute and It may cause the code generation failure.   <wsdl:port name="StockQuoteProxyAdmin/httpsSoap12Endpoint"                  binding="axis2:StockQuoteProxySoap12Binding">   BTW, there is an option in proxy service configuration that force to use  the given original WSDL <proxy> …. <publishWSDL uri="file:repository/conf/sample/resources/proxy/sample_proxy_1.wsdl"/> ….. <parameter name="useOriginalwsdl">true</parameter>   </proxy>   In this case,'?wsdl' will be the wsdl given by the ‘publishWSDL’ , here it is ‘sample_proxy_1.wsdl’.   Thanks Indika     [1] http://www.validwsdl.com/ [2] http://www.xmethods.net