Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[rmss]

I'm trying to test the Web Service Interface but I'm not able to get the WSDL.
http://myserver:52199/MCWS/v1/WSDL returns empty

Documentation pages (http://myserver:52199/MCWS/v1/doc) works fine, but I would like to get to wsdl and generate a proxy class in my dev environment.
Version I'm using is 15.0.73

[JimH]

Are you starting with documenation from our wiki?  Devzone ....

[rmss]

Yes I've searched the wiki (http://wiki.jrmediacenter.com/index.php/Web_Service_Interface)
and it only directs to download WSDLfrom http://[library server address]/MCWS/v1/WSDL

If somebody has the WSDL-page working could you please post it here. I can proceed with that.

[Matt]

Sorry, it looks like there's a bug where it can return an empty WSDL.  Here's the WSDL.

But let me warn you that we gave up on WSDL for the time being because MCWS is a REST based interface, not a strict web service.  Although the latest WSDL spec can support REST interfaces, .NET can not import a WSDL for a REST interface.  Hopefully this will get cleaned up by Microsoft at some point and we'll do some work to make sure importing the WSDL into .NET makes a nice wrapper.

For now, if you're using .NET, it might be easier to just make the calls directly.

Thanks.

[rmss]

Thank you for the quick reply and information.

Yes I'm using .Net, so I decided to build calls directly.

It looks like the volume command has a bug.
It allways sets volume to all zones even if zone is defined in the call.

[SteveV]

Sorry, it looks like there's a bug where it can return an empty WSDL.  Here's the WSDL.

But let me warn you that we gave up on WSDL for the time being because MCWS is a REST based interface, not a strict web service.  Although the latest WSDL spec can support REST interfaces, .NET can not import a WSDL for a REST interface.  Hopefully this will get cleaned up by Microsoft at some point and we'll do some work to make sure importing the WSDL into .NET makes a nice wrapper.

For now, if you're using .NET, it might be easier to just make the calls directly.

Thanks.

Hi Matt,

Did you guys ever make any progress on this?  I'm looking for a .NET wrapper for the MCWS and would prefer to not start from scratch building my own.

Thanks -- Steve

[Matt]

Did you guys ever make any progress on this?  I'm looking for a .NET wrapper for the MCWS and would prefer to not start from scratch building my own.

There have been no changes.

Maybe when we switch to VS 11 in a year or so we'll revisit this with the hope that Microsoft has updated the .NET WSDL parser.