[Spce-user] Provisioning WSDL & .net app

Andrew Pogrebennyk apogrebennyk at sipwise.com
Mon Feb 18 05:28:31 EST 2013


For the history:
Replied with some tips in private, namely:

1) Fix namespace names (we'll backport it to 2.7 with a next occasion):
             targetNamespace="http://dev.sipwise.com/SOAP/Provisioning"
             xmlns:tns="http://dev.sipwise.com/SOAP/Provisioning"
             xmlns:typens="http://dev.sipwise.com/SOAP/Provisioning/Types"

2) you may need to strip the documentation elements from the file:

perl -i -0777 -ple's/\s*<documentation>.+?<\/documentation>//sg'
Provisioning.wsdl

On 02/17/2013 02:55 PM, Jirka Jirout wrote:
> Hello,
> 
> we are trying to build a helpdesk solution for our instance of spce using .net and c#. When we try to import the spce provisioning wsdl, we get a ton of error  messages:
> 
>> The document at the url file:///c:/Provisioning.wsdl was not recognized as a known document type.
>>
>> The error message from each known type may help you fix the problem:
>> - Report from 'XML Schema' is 'The root element of a W3C XML Schema should be <schema> and its namespace should be 'http://www.w3.org/2001/XMLSchema'.'.
>> - Report from 'DISCO Document' is 'Discovery document at the URL file:///c:/Provisioning.wsdl could not be found.'.
>>   - The document format is not recognized.
>> - Report from 'WSDL Document' is 'There is an error in XML document (25, 10).'.
>>   - The element was not expected in this context: <documentation xmlns='http://www.w3.org/2001/XMLSchema'>..</documentation>. 
>>
>> Expected elements: http://www.w3.org/2001/XMLSchema:annotation,http://www.w3.org/2001/XMLSchema:complexContent, http://www.w3.org/2001/XMLSchema:simpleContent,http://www.w3.org/2001/XMLSchema:group, http://www.w3.org/2001/XMLSchema:sequence,http://www.w3.org/2001/XMLSchema:choice, http://www.w3.org/2001/XMLSchema:all,http://www.w3.org/2001/XMLSchema:attribute, http://www.w3.org/2001/XMLSchema:attributeGroup,http://www.w3.org/2001/XMLSchema:anyAttribute.
>> If the service is defined in the current solution, try building the solution and adding the service reference again.
>>
> I have managed to supress the documentation error, but the rest is still there. Has anyone succeeded in using the provisioning interface in .net app? Writing all the objects manually is not really an option for us.
> 
> regards, jj
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user
> 





More information about the Spce-user mailing list