What to do if your WSDL has no service definition

[concord]

It appears that TradeMe's wsdl does not include "service definitions", and will therefore not load into Jade.

Their api files include 4 *.xsd files, I've embedded these inside the wsdl but still no luck validating it with JADE's Web Service Consumer .

I've scanned the contents of all the files supplied by TradeMe and can't find anything the resembles the "service defn" sections I'm familiar with from my Jade generated wsdl's.

Not sure what to try next, TradeMe don't seem to be particularly interested.

[murray]

Sorry, I have no expert advice here, but a suggestion: if you can determine the section that the Jade wizard needs to keep it happy (I am guessing it is the "<soap:address location=.../>" that you need), you can then manually edit the WSDL file to suit.

[concord]

The service definitions would have to come from TradeMe, I have no idea what they would look like.

From my own wsdl's (generated from the JDE) I'd expect them to look something like this (see below).

However, I've been through every file supplied by TradeMe and cannot find anything even remotely similar. Our client has some sway with TradeMe and has been putting pressure on their API team for assistance, we've been promised a reply of some-sort from them soon.

=======================================================
<service name="JadeClassName">
<port name="JadeClassNameSoap" binding="tns:JadeClassNameSoap">
<soap:address location="http://192.168.1.10/xyz/?JadeClassName& ... eClassName" />
</port>
<port name="JadeClassNameHttpGet" binding="tns:JadeClassNameHttpGet">
<soap:address location="http://192.168.1.10/xyz/?JadeClassName& ... eClassName" />
</port>
<port name="JadeClassNameHttpPost" binding="tns:JadeClassNameHttpPost">
<soap:address location="http://192.168.1.10/xyz/?JadeClassName& ... eClassName" />
</port>
</service>