Enterprises are inherently complex, comprising of hundreds of applications with completely different semantics. Some of these applications are custom built, where as some are acquired from third parties and some even can be a combination of both and they can be operating in different system environments.
WSO2 VMware Images helps you to try our products inside your virtualized environments without having to go through the trouble of installation and configuration. Download an image and get your hands on cutting edge, lightweight SOA middleware right away!
WSO2 Governance Registry is a product from WSO2 that facilitates you to govern the SOA platform of your organization by helping you store and manage SOA meta data. The product is free and open source with Apache licence and you can download it from http://wso2.org/projects/governance-registry
Hi Peter I think the problem
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
Re: ESB provides Invalid WSDL (sample 150)
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