No wrapper vis created when importing web service

[Premise03]

Hi,

I am having an issue in LV 8.5 when importing a web service my company created.  Everything goes well, no errors, I get a list of methods to import, a project and library are created.  However, in the end no VIs are created in the lvlib file.

I tried the example http://zone.ni.com/devzone/cda/tut/p/id/4728 which imports from ws.cdyne.com and VIs were created.

I am suspecting that the WSDL has some flaw, but I am not a web service expert nor the creator of the web service.

Any advice on how to proceed?

Thanks,

Premise03 (Chris Roth)

[andre.buurman@carya]

If your company created the webservice, then you should talk to the people that created it and ask them what the difference is with the ws.cdyne.com example wsdl.

André

[Premise03]

Good suggestion, which I am working on.

I was able to successfully query the WSDL from Visual Studio 2005.  And the existing consumers of the web service are able to use it OK.

There seem to be a number of WSDL validator tools out there, but the web service has to be exposed to the outside world which it is not.

I was hoping to find some tool that would validate the WSDL output that you see when you point your browser at it.

[TobyD]

You can try http://www.soapui.org/. Click on "Click here to webstart now" and the Java app will download and run on you machine. You can use it to verify your WSDL.

[andreas_nilsson]

Hi,

I have the same problem. No VIs are created. I suspect that something is wrong on the Labview side, since the web service seems to work. I managed to successfully call it using http://www.soapui.org/.

Please help!

[TobyD]

You can try the web services browser (http://zone.ni.com/devzone/cda/tut/p/id/4729) but you'll probably have the same results. I had one WSDL that I had to compile using Microsoft's wsdl.exe tool. If my memory serves me, I had to download a trial version of VB.net to use the tool, but then it compiled my wsdl to a dll that I could call from LabVIEW and/or generate wrapper VIs for. There are quite a few tutorials online if you search for wsdl.exe. It was all done through the command line, but it was fast and it worked!

Good Luck,

Toby

[andreas_nilsson]

Problem solved      New problem

I just installed Labview 8.5.1. The problem is gone. However, a new problem appeared. The XML output does not contain the actual result values. When I call the web service using SOAPUI from http://www.soapui.org/, I can see the actual result values in a section of the XML output called diffgr:diffgram. When I inspect the Labview XML output, the whole diffgram section is missing!

Our IT guy says that they have not payed much attention to the WSDL since they themselves run Microsoft .net only. Could there be some WSDL-non-according-to-standard problem? Another thought: Is Labview capable of handling the diffgram data type? What do you guys think? Please see attached copies of output.

[andreas_nilsson]

... here are the attached files.

[Van_L]

Hi Andreas,

Have you been successful since your last post?
This isn't my topic of expertise.
I'll take some time to look into it.
Meanwhile, try formulate your new problem in a new thread so others are aware of it. And post a link from this thread to the new thread you created.

Good luck

[andreas_nilsson]

Thanks!

I posted it here: http://forums.ni.com/ni/board/message?board.id=170&thread.id=316285. Still no answers, though.