3.1.4.9 GetCustomizedPageStatus

This operation<17> obtains the customization status (also known as the uncustomized status) of the specified page or file. This operation is defined as follows:

 <wsdl:operation name="GetCustomizedPageStatus">
     <wsdl:input message="tns:GetCustomizedPageStatusSoapIn" />
     <wsdl:output message="tns:GetCustomizedPageStatusSoapOut" />
 </wsdl:operation>

The protocol client sends a GetCustomizedPageStatusSoapIn request message to obtain the customization status of the specified page or file. The protocol server responds by sending a GetCustomizedPageStatusSoapOut response message. The response specifies customization status of the page or file identified by the fileUrl, where the customization status MUST be one of the following:

§ None

§ Customized

§ Uncustomized

The protocol server portion of the HTTP POST address MUST be the address of a site. For example, a valid POST address might be "http://www.example.com/SiteDirectory".

The fileUrl MUST specify a page or a file on the context site. The fileUrl MUST be relative to the POST address. For example, a valid fileUrl might be "Pages/category.aspx".

This operation returns a customization status value that specifies whether the fileUrl represents a customized page, an uncustomized page, or a file containing static content.

A customized page is a page that the protocol server generates dynamically by some combination of database query and code execution. An uncustomized page is a previously generated page to which the protocol server can refer. A file containing static content is a file, such as an individual text file or a static HTML page that contains no code and requires no access to the content database to be rendered.

The table in CustomizedPageStatus (section 3.1.4.9.4.1) specifies the meaning of each customization status value.