3.1.4.7 AddExtension

  • 2 minutes to read

This operation is used to add a file extension to the file extensions collection contained in the portal content project.

 <wsdl:operation name="AddExtension">
         <wsdl:input message="AddExtensionSoapIn"/>
         <wsdl:output message="AddExtensionSoapOut"/>
 </wsdl:operation>

The protocol client sends an AddExtensionSoapIn request message and the protocol server responds with an AddExtensionSoapOut response message, as follows:

  • On receipt the protocol server validates the versionIn value from the request message. If it doesn’t match the current configuration version of the crawler application, the protocol server MUST throw a SOAP fault message containing an UpdatedConcurrencyException.

  • The protocol server then updates the current configuration version of the crawler application to the value of versionIn+1.

  • The protocol server first removes any leading or trailing white-space characters from the ext element of the request message.

  • The protocol server then removes the first character of the ext element if it is the ‘.’ character.

  • If the ext element becomes empty, contains any white-space character, or contains any of the invalid characters (‘.’, ‘/’, ‘?’, ‘*’, ‘:’, ‘\’, ‘#’), the protocol server MUST throw a SOAP fault message containing a COMException with the HRESULT field set to 0x80040d45.

  • If the file extension specified by the ext element already exists in the list, the protocol server MUST throw a SOAP fault message containing a COMException with the HRESULT field set to 0x80040D02.

  • The protocol server adds the file extension specified by the ext element to the portal content project’s list of extensions.

  • On success, the protocol server MUST return the updated configuration version of the crawler application in the AddExtensionResult element in the response message.

  • On error, the protocol server MUST throw a SOAP fault message.