ConfigEditingService


The following operations are supported. For a formal definition, please review the Service Description.

This web service does not conform to WS-I Basic Profile v1.1.

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>


R2710: The operations in a wsdl:binding in a DESCRIPTION MUST result in wire signatures that are different from one another. An endpoint that supports multiple operations must unambiguously identify the operation being invoked based on the input message that it receives. This is only possible if all the operations specified in the wsdl:binding associated with an endpoint have a unique wire signature.
- Input message 'GetSiteConfigSoapIn' from namespace 'urn:schemas-newtelligence-com:dasblog:config-services' has no elements (empty wire signature)
- Input message 'EnumBlogrollsSoapIn' from namespace 'urn:schemas-newtelligence-com:dasblog:config-services' has no elements (empty wire signature)
- Input message 'GetBlogrollSoapIn' from namespace 'urn:schemas-newtelligence-com:dasblog:config-services' has wire signature 'urn:schemas-newtelligence-com:dasblog:config-services:blogRollName'.
- Input message 'PostBlogrollSoapIn' from namespace 'urn:schemas-newtelligence-com:dasblog:config-services' has wire signature 'urn:schemas-newtelligence-com:dasblog:config-services:blogRollName'.
Recommendation: The Profile defines the "wire signature" of an operation in a wsdl:binding to be the fully qualified name of the child element of the soap:Body of the SOAP input message it describes. For the case of an empty soap:Body this name is an empty string. In the case of rpc-literal binding, the operation name is used as a wrapper for the part accessors. In the document-literal case, since a wrapper with the operation name is not present, the message signatures must be correctly designed so that they meet this requirement.

R2210: If a document-literal binding in a DESCRIPTION does not specify the parts attribute on a soapbind:body element, the corresponding abstract wsdl:message MUST define zero or one wsdl:parts.
- Operation 'PostBlogroll' on binding 'ConfigEditingServiceSoap' from namespace 'urn:schemas-newtelligence-com:dasblog:config-services'.
Recommendation: For Document-literal bindings, the Profile requires that at most one part, abstractly defined with the element attribute, be serialized into the soap:Body element. When using a Bare parameter style, a conformant method must have at most one parameter.

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