Director Web Service

Please examine each of the normative statement violations below. Follow the recommendations to remedy it, or add setting to the <webServices> config section to turn off BP 1.1 conformance warnings for the entire vroot.

To turn off BP 1.1 conformance warnings for the entire vroot remove the 'BP1.1' value from the <conformanceWarnings> section of the configuration file of your application:

<configuration>
  <system.web>
    <webServices>
      <conformanceWarnings>
        <remove name='BasicProfile1_1'/>
      </conformanceWarnings>
    </webServices>
  </system.web>
</configuration>

R2304: Operation name overloading in a wsdl:portType is disallowed by the Profile. A wsdl:portType in a DESCRIPTION MUST have operations with distinct values for their name attributes. Note that this requirement applies only to the wsdl:operations within a given wsdl:portType. A wsdl:portType may have wsdl:operations with names that are the same as those found in other wsdl:portTypes.
- Operation 'GetCustomerAccountInfo' on portType 'DirectorSoap' from namespace 'http://tempuri.org/'.
- Operation 'GetMeterERT' on portType 'DirectorSoap' from namespace 'http://tempuri.org/'.
- Operation 'GetMeterInfo' on portType 'DirectorSoap' from namespace 'http://tempuri.org/'.
- Operation 'GetMeterInfo' on portType 'DirectorSoap' from namespace 'http://tempuri.org/'.
- Operation 'GetMeterInfo' on portType 'DirectorSoap' from namespace 'http://tempuri.org/'.
- Operation 'GetNewAddedMeterTable' on portType 'DirectorSoap' from namespace 'http://tempuri.org/'.
- Operation 'GetServiceInventory' on portType 'DirectorSoap' from namespace 'http://tempuri.org/'.
Recommendation: To make service conformant please make sure that all web methods belonging to the same binding have unique names.

For more details on Basic Profile Version 1.1, see the Basic Profile Specification.

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/":

[WebService(Namespace="http://microsoft.com/webservices/")]
public class MyWebService {
    // implementation
}

Visual Basic

<WebService(Namespace:="http://microsoft.com/webservices/")> Public Class MyWebService
    ' implementation
End Class

C++

[WebService(Namespace="http://microsoft.com/webservices/")]
public ref class MyWebService {
    // implementation
};

For more details on XML namespaces, see the W3C recommendation on Namespaces in XML.

For more details on WSDL, see the WSDL Specification.

For more details on URIs, see RFC 2396.