I am confused. Put off making any changes until system failed. Still running old XMLTV and just ran a successful download.
Has the the migration been delayed???
ericwl wrote:I am confused. Put off making any changes until system failed. Still running old XMLTV and just ran a successful download.
Has the the migration been delayed???
ericwl wrote:I am confused. Put off making any changes until system failed. Still running old XMLTV and just ran a successful download.
Has the the migration been delayed???
rmeden wrote:The WSDL is available. http://dd.schedulesdirect.org/tech/tmsd ... ivery.wsdl
-> "C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\wsdl.exe" /namespace:SchedulesDirectWebSer
vice tvDataDelivery.wsdl
Microsoft (R) Web Services Description Language Utility
[Microsoft (R) .NET Framework, Version 4.0.30319.33440]
Copyright (C) Microsoft Corporation. All rights reserved.
Warning: This web reference does not conform to WS-I Basic Profile v1.1.
R2028, R2029: A DESCRIPTION using the WSDL namespace and the WSDL SOAP binding namespace MUST be valid according to the
XML Schemas found at http://schemas.xmlsoap.org/wsdl/2003-02-11.xsd and http://schemas.xmlsoap.org/wsdl/soap/2003-02-11.
xsd.
- Warning: The 'http://www.w3.org/XML/1998/namespace:lang' attribute is not declared. Line 55, position 18.
- Warning: The 'name' attribute is invalid - The value 'tms:webserviceFault' is invalid according to its datatype 'ht
tp://www.w3.org/2001/XMLSchema:NCName' - The ':' character, hexadecimal value 0x3A, cannot be included in a name. Line 8
1, position 17.
R2706: A wsdl:binding in a DESCRIPTION MUST use the value of "literal" for the use attribute in all soapbind:body, soapb
ind:fault, soapbind:header and soapbind:headerfault elements.
- Input element soapbind:body of operation 'download' on portType 'xtvdBinding' from namespace 'urn:TMSWebServices'.
- Output element soapbind:body of operation 'download' on portType 'xtvdBinding' from namespace 'urn:TMSWebServices'.
- soapbind:fault 'tms:webserviceFault' on operation 'download' on portType 'xtvdBinding' from namespace 'urn:TMSWebSe
rvices'.
R2717: An rpc-literal binding in a DESCRIPTION MUST have the namespace attribute specified, the value of which MUST be a
n absolute URI, on contained soapbind:body elements.
- Input element soapbind:body of operation 'acknowledge' on portType 'xtvdBinding' from namespace 'urn:TMSWebServices
'.
- Output element soapbind:body of operation 'acknowledge' on portType 'xtvdBinding' from namespace 'urn:TMSWebService
s'.
R2705: A DESCRIPTION MUST use the same value of, either 'rpc' or 'document' for the style attribute for all of its opera
tions in a portType, in the SOAP Binding description.
- Binding 'xtvdBinding' from namespace 'urn:TMSWebServices'.
For more details on the WS-I Basic Profile v1.1, see the specification
at http://www.ws-i.org/Profiles/BasicProfile-1.1.html.
Error: Unable to import binding 'xtvdBinding' from namespace 'urn:TMSWebServices'.
- Unable to import operation 'download'.
- The datatype 'urn:TMSWebServices:dateTime' is missing.
http://dd.schedulesdirect.org/tech/tmsdatadirect/schedulesdirect/tmsxgv1.xsd
http://dd.schedulesdirect.org/tech/tmsdatadirect/schedulesdirect/tmsxtvdv1.xsd
skst wrote:Again, I can't comment on any other toolset, but it compiles successfully for Visual Studio 2013 Update 4. I do still have to download the XSD file referenced by the WSDL file and the XSD file referenced by the first XSD file. Then, of course, I have to edit the WSDL and XSD files to remove the URL path (leaving just the filename, so it's referencing the local copy).
- Code: Select all
http://dd.schedulesdirect.org/tech/tmsdatadirect/schedulesdirect/tmsxgv1.xsd
http://dd.schedulesdirect.org/tech/tmsdatadirect/schedulesdirect/tmsxtvdv1.xsd
Note: the start and stop times are in UTC and in ISO 8601 format: YYYY-MM-DDThh:mm:ssZ
It might be useful to some if that were added to the documentation in the WSDL file itself.
Users browsing this forum: No registered users and 6 guests