Hot answers tagged wsdl
the article you reference at the end of your question really answers it: custom web services should be placed in _vti_bin. i usually start by adding them to _LAYOUTS but thats only to be able to define my discovery files etc (as described in the MSDN specification you mention). _vti_bin is a virtual directory mapped to the 12/ISAPI folder, so you can ...
Why are you deploying your Custom Web Service to the layouts folder at first place? You need to copy the Web service files to the _vti_bin virtual directory Copy the Service1wsdl.aspx file, the Service1disco.aspx file, and the Service1.asmx file to the _vti_bin virtual directory. This is the directory where all default Web services are stored. Copy the ...
You are correct. There is no WSDL available for specific lists. All the operations on the Lists web service are performed against the local SPWeb and take a ListName as a parameter.
the article you reference at the end of your question really answers it: custom web services should be placed in _vti_bin. i usually start by adding them to _LAYOUTS but thats only to be able to define my discovery files etc (as described in the MSDN specification you mention). I've created a simple commandline tool which generates ...
You don't need the .disco file from the tutorial. That is only if you want auto-discovery. You do however need the WSDL file, if you intend to be able to involve the web service reference using a dynamic url address. Unlike most web services that are deployed from a static and well-known endpoint location, SharePoint web services can be invoked from ...
SPListItem is not serializable so you cannot pass it as a parameter to a web service.
Check that the web.config in SharePointRoot\ISAPI contains <system.web> <webServices> <protocols> ... <add name="Documentation" /> </protocols> </webServices> ... </system.web>
The lists.asmx is a standard SharePoint web service. So you should not install that. It seems that the software you're installing may be using web services instead of exposing them.
Use SPServices, a jQuery plugin that allows easy access to most of the (WCF) Services provided by SharePoint.
This was the same problem with ASP.NET WSDL web services in SharePoint 2007, and why originally you had to create custom WSDL generation pages. This has been fixed in SharePoint 2010 by using SharePoint service factories. If you are using the Microsoft SharePoint web service factories, the root domain should not be a problem as the WSDL generation for the ...
Please check the endpoint address and see if defining it to sharepoint.foo.com does the trick. Also I ran into this where you have multiple suggestions, specifically instructions in how to configure the endpoint of the mex.
My recommendation is to deploy the custom web service to the Layouts (_layouts) folder rather than the ISAPI (_vti_bin) folder. All the issues with the disco and wsdl generation go away. I posted a walkthough for this on my blog, Walkthrough: Creating a Custom ASP.NET (ASMX) Web Service in SharePoint 2010
@Melih Öztürk posted a solution to his own question: contactRef part of the WSDL file seems to be not well-formed. I changed it and problem solved. I'm posting this as a community wiki since this question seems to be abandoned. If anyone has more information, feel free to add it!
Only top voted, non community-wiki answers of a minimum length are eligible