Default XML namespace
Problem reported by Robbie Wright - 9/12/2014 at 11:02 AM
Not A Problem
Anyone else noticed that the wsdl's are all using default xml namespaces? Even the wdsl's say you should do that on the page you load.......

This web service is using http://tempuri.org/ as its default namespace.

Recommendation: Change the default namespace before the XML Web service is made public.

Each XML Web service needs a unique namespace in order for client applications to distinguish it from other services on the Web. http://tempuri.org/ is available for XML Web services that are under development, but published XML Web services should use a more permanent namespace.

Your XML Web service should be identified by a namespace that you control. For example, you can use your company's Internet domain name as part of the namespace. Although many XML Web service namespaces look like URLs, they need not point to actual resources on the Web. (XML Web service namespaces are URIs.)

For XML Web services creating using ASP.NET, the default namespace can be changed using the WebService attribute's Namespace property. The WebService attribute is an attribute applied to the class that contains the XML Web service methods. Below is a code example that sets the namespace to "http://microsoft.com/webservices/":

1 Reply

Reply to Thread
Tim Uzzanti Replied
Employee Post
It is an unfortunate reality that API's developed and pushed to the public must be unchanged to avoid applications such as Control Panels, Billing Systems and so much more from breaking.
Our only options to make things perfect and keep things moving forward on the latest technologies are to introduce NEW methods.  We will be introducing JSON API's in the future.
We have Enterprise organizations that will be using 1.0 versions of our API's for their entire lifetime.  Its an ugly reality :)
Tim Uzzanti
Tim Uzzanti CEO SmarterTools Inc. (877) 357-6278 www.smartertools.com

Reply to Thread