Web Service: CmsMetadataService
Port CmsMetadataServiceInterfacePort Port typeSource code
- getCmsMetadataKeysByStatementDetailSource code
- getCmsMetadataValuesByStatementDetailSource code
- performCmsMetadataKeyActionDetailSource code
- performCmsMetadataValueActionDetailSource code
Operations
- getCmsMetadataKeysByStatementDescription:Returns a page of {@link CmsMetadataKey}s matching the specified {@link Statement}. The following fields are supported for filtering:
PQL Property Object Property {@code id} {@link CmsMetadataKey#cmsMetadataKeyId} {@code cmsKey} {@link CmsMetadataKey#keyName} {@code status} {@link CmsMetadataKey#status} Operation type:Request-response. The endpoint receives a message, and sends a correlated message.Input:getCmsMetadataKeysByStatementRequest (wsdlsoap:header, use = literal, part = RequestHeader)Source codeparameters type getCmsMetadataKeysByStatementReturns a page of {@link CmsMetadataKey}s matching the specified {@link Statement}. The following fields are supported for filtering:PQL Property Object Property {@code id} {@link CmsMetadataKey#cmsMetadataKeyId} {@code cmsKey} {@link CmsMetadataKey#keyName} {@code status} {@link CmsMetadataKey#status} - statement - optional; type StatementCaptures the {@code WHERE}, {@code ORDER BY} and {@code LIMIT} clauses of a PQL query. Statements are typically used to retrieve objects of a predefined domain type, which makes SELECT clause unnecessary.
An example query text might be {@code "WHERE status = 'ACTIVE' ORDER BY id LIMIT 30"}.
Statements support bind variables. These are substitutes for literals and can be thought of as input parameters to a PQL query.
An example of such a query might be {@code "WHERE id = :idValue"}.
Statements also support use of the LIKE keyword. This provides wildcard string matching.
An example of such a query might be {@code "WHERE name LIKE '%searchString%'"}.
The value for the variable idValue must then be set with an object of type {@link Value}, e.g., {@link NumberValue}, {@link TextValue} or {@link BooleanValue}.- query - optional; type stringHolds the query in PQL syntax. The syntax is:
[WHERE{[AND | OR] ...}]
[ORDER BY[ASC | DESC]]
[LIMIT {[,] } | { OFFSET }]
:={< | <= | > | >= | = | != }
:={< | <= | > | >= | = | != }
:= IN
:= IS NULL
:= LIKE
:= :
- values - optional, unbounded; type String_ValueMapEntryHolds keys and values for bind variables and their values. The key is the name of the bind variable. The value is the literal value of the variable.
In the example {@code "WHERE status = :bindStatus ORDER BY id LIMIT 30"}, the bind variable, represented by {@code :bindStatus} is named {@code bindStatus}, which would also be the parameter map key. The bind variable's value would be represented by a parameter map value of type {@link TextValue}. The final result, for example, would be an entry of {@code "bindStatus" => StringParam("ACTIVE")}.
This represents an entry in a map with a key of type String and value of type Value.- key - optional; type string
- value - optional; type Value{@code Value} represents a value.
- query - optional; type string
Output:getCmsMetadataKeysByStatementResponse (wsdlsoap:header, use = literal, part = ResponseHeader)Source codeparameters type getCmsMetadataKeysByStatementResponse- rval - optional; type CmsMetadataKeyPageCaptures a page of CMS metadata key objects.
- totalResultSetSize - optional; type int
- startIndex - optional; type int
- results - optional, unbounded; type CmsMetadataKeyKey associated with a piece of content from a publisher's CMS.
- id - optional; type longThe ID of this CMS metadata key. This field is read-only and provided by Google.
- name - optional; type stringThe key of a key-value pair.
- status - optional; type CmsMetadataKeyStatus - type string with restriction - enum { 'ACTIVE', 'INACTIVE', 'UNKNOWN' }The status of this CMS metadata key. This attribute is read-only.
- id - optional; type long
Fault:ApiException (wsdlsoap:fault, use = literal)Source codeApiException type ApiExceptionFaultException class for holding a list of service errors.Base class for exceptions.- message - optional; type stringError message.
- errors - optional, unbounded; type ApiErrorThe API error base class that provides details about an error that occurred while processing a service request.
The OGNL field path is provided for parsers to identify the request data element that may have caused the error.
- fieldPath - optional; type stringThe OGNL field path to identify cause of error.
- fieldPathElements - optional, unbounded; type FieldPathElementA parsed copy of the field path. For example, the field path "operations[1].operand" corresponds to this list: {FieldPathElement(field = "operations", index = 1), FieldPathElement(field = "operand", index = null)}.A segment of a field path. Each dot in a field path defines a new segment.
- field - optional; type stringThe name of a field in lower camelcase. (e.g. "biddingStrategy")
- index - optional; type intFor list fields, this is a 0-indexed position in the list. Null for non-list fields.
- field - optional; type string
- trigger - optional; type stringThe data that caused the error.
- errorString - optional; type stringA simple string representation of the error and reason.
List of errors. - fieldPath - optional; type string
A fault element of type ApiException. - statement - optional; type Statement
- getCmsMetadataValuesByStatementDescription:Returns a page of {@link CmsMetadataValue}s matching the specified {@link Statement}. The following fields are supported for filtering:
PQL Property Object Property {@code id} {@link CmsMetadataValue#cmsMetadataValueId} {@code cmsValue} {@link CmsMetadataValue#valueName} {@code cmsKey} {@link CmsMetadataValue#key#name} {@code cmsKeyId} {@link CmsMetadataValue#key#id} {@code status} {@link CmsMetadataValue#status} Operation type:Request-response. The endpoint receives a message, and sends a correlated message.Input:getCmsMetadataValuesByStatementRequest (wsdlsoap:header, use = literal, part = RequestHeader)Source codeparameters type getCmsMetadataValuesByStatementReturns a page of {@link CmsMetadataValue}s matching the specified {@link Statement}. The following fields are supported for filtering:PQL Property Object Property {@code id} {@link CmsMetadataValue#cmsMetadataValueId} {@code cmsValue} {@link CmsMetadataValue#valueName} {@code cmsKey} {@link CmsMetadataValue#key#name} {@code cmsKeyId} {@link CmsMetadataValue#key#id} {@code status} {@link CmsMetadataValue#status} - statement - optional; type StatementCaptures the {@code WHERE}, {@code ORDER BY} and {@code LIMIT} clauses of a PQL query. Statements are typically used to retrieve objects of a predefined domain type, which makes SELECT clause unnecessary.
An example query text might be {@code "WHERE status = 'ACTIVE' ORDER BY id LIMIT 30"}.
Statements support bind variables. These are substitutes for literals and can be thought of as input parameters to a PQL query.
An example of such a query might be {@code "WHERE id = :idValue"}.
Statements also support use of the LIKE keyword. This provides wildcard string matching.
An example of such a query might be {@code "WHERE name LIKE '%searchString%'"}.
The value for the variable idValue must then be set with an object of type {@link Value}, e.g., {@link NumberValue}, {@link TextValue} or {@link BooleanValue}.- query - optional; type stringHolds the query in PQL syntax. The syntax is:
[WHERE{[AND | OR] ...}]
[ORDER BY[ASC | DESC]]
[LIMIT {[,] } | { OFFSET }]
:={< | <= | > | >= | = | != }
:={< | <= | > | >= | = | != }
:= IN
:= IS NULL
:= LIKE
:= :
- values - optional, unbounded; type String_ValueMapEntryHolds keys and values for bind variables and their values. The key is the name of the bind variable. The value is the literal value of the variable.
In the example {@code "WHERE status = :bindStatus ORDER BY id LIMIT 30"}, the bind variable, represented by {@code :bindStatus} is named {@code bindStatus}, which would also be the parameter map key. The bind variable's value would be represented by a parameter map value of type {@link TextValue}. The final result, for example, would be an entry of {@code "bindStatus" => StringParam("ACTIVE")}.
This represents an entry in a map with a key of type String and value of type Value.- key - optional; type string
- value - optional; type Value{@code Value} represents a value.
- query - optional; type string
Output:getCmsMetadataValuesByStatementResponse (wsdlsoap:header, use = literal, part = ResponseHeader)Source codeparameters type getCmsMetadataValuesByStatementResponse- rval - optional; type CmsMetadataValuePageCaptures a page of CMS metadata value objects.
- totalResultSetSize - optional; type int
- startIndex - optional; type int
- results - optional, unbounded; type CmsMetadataValueKey value pair associated with a piece of content from a publisher's CMS.
- cmsMetadataValueId - optional; type longThe ID of this CMS metadata value, to be used in targeting. This field is read-only and provided by Google.
- valueName - optional; type stringThe value of this key-value pair.
- key - optional; type CmsMetadataKeyKey associated with a piece of content from a publisher's CMS.
- id - optional; type longThe ID of this CMS metadata key. This field is read-only and provided by Google.
- name - optional; type stringThe key of a key-value pair.
- status - optional; type CmsMetadataKeyStatus - type string with restriction - enum { 'ACTIVE', 'INACTIVE', 'UNKNOWN' }The status of this CMS metadata key. This attribute is read-only.
- id - optional; type long
- status - optional; type CmsMetadataValueStatus - type string with restriction - enum { 'ACTIVE', 'INACTIVE', 'ARCHIVED', 'UNKNOWN' }The status of this CMS metadata value. This attribute is read-only.
- cmsMetadataValueId - optional; type long
Fault:ApiException (wsdlsoap:fault, use = literal)Source codeApiException type ApiExceptionFaultException class for holding a list of service errors.Base class for exceptions.- message - optional; type stringError message.
- errors - optional, unbounded; type ApiErrorThe API error base class that provides details about an error that occurred while processing a service request.
The OGNL field path is provided for parsers to identify the request data element that may have caused the error.
- fieldPath - optional; type stringThe OGNL field path to identify cause of error.
- fieldPathElements - optional, unbounded; type FieldPathElementA parsed copy of the field path. For example, the field path "operations[1].operand" corresponds to this list: {FieldPathElement(field = "operations", index = 1), FieldPathElement(field = "operand", index = null)}.A segment of a field path. Each dot in a field path defines a new segment.
- field - optional; type stringThe name of a field in lower camelcase. (e.g. "biddingStrategy")
- index - optional; type intFor list fields, this is a 0-indexed position in the list. Null for non-list fields.
- field - optional; type string
- trigger - optional; type stringThe data that caused the error.
- errorString - optional; type stringA simple string representation of the error and reason.
List of errors. - fieldPath - optional; type string
A fault element of type ApiException. - statement - optional; type Statement
- performCmsMetadataKeyActionDescription:Performs actions on {@link CmsMetadataKey} objects that match the given {@link Statement#query}.Operation type:Request-response. The endpoint receives a message, and sends a correlated message.Input:performCmsMetadataKeyActionRequest (wsdlsoap:header, use = literal, part = RequestHeader)Source codeparameters type performCmsMetadataKeyActionPerforms actions on {@link CmsMetadataKey} objects that match the given {@link Statement#query}.
- keyAction - optional; type CmsMetadataKeyActionRepresents the actions that can be performed on {@link CmsMetadataKey} objects.
- filterStatement - optional; type StatementCaptures the {@code WHERE}, {@code ORDER BY} and {@code LIMIT} clauses of a PQL query. Statements are typically used to retrieve objects of a predefined domain type, which makes SELECT clause unnecessary.
An example query text might be {@code "WHERE status = 'ACTIVE' ORDER BY id LIMIT 30"}.
Statements support bind variables. These are substitutes for literals and can be thought of as input parameters to a PQL query.
An example of such a query might be {@code "WHERE id = :idValue"}.
Statements also support use of the LIKE keyword. This provides wildcard string matching.
An example of such a query might be {@code "WHERE name LIKE '%searchString%'"}.
The value for the variable idValue must then be set with an object of type {@link Value}, e.g., {@link NumberValue}, {@link TextValue} or {@link BooleanValue}.- query - optional; type stringHolds the query in PQL syntax. The syntax is:
[WHERE{[AND | OR] ...}]
[ORDER BY[ASC | DESC]]
[LIMIT {[,] } | { OFFSET }]
:={< | <= | > | >= | = | != }
:={< | <= | > | >= | = | != }
:= IN
:= IS NULL
:= LIKE
:= :
- values - optional, unbounded; type String_ValueMapEntryHolds keys and values for bind variables and their values. The key is the name of the bind variable. The value is the literal value of the variable.
In the example {@code "WHERE status = :bindStatus ORDER BY id LIMIT 30"}, the bind variable, represented by {@code :bindStatus} is named {@code bindStatus}, which would also be the parameter map key. The bind variable's value would be represented by a parameter map value of type {@link TextValue}. The final result, for example, would be an entry of {@code "bindStatus" => StringParam("ACTIVE")}.
This represents an entry in a map with a key of type String and value of type Value.- key - optional; type string
- value - optional; type Value{@code Value} represents a value.
- query - optional; type string
Output:performCmsMetadataKeyActionResponse (wsdlsoap:header, use = literal, part = ResponseHeader)Source codeparameters type performCmsMetadataKeyActionResponse- rval - optional; type UpdateResultRepresents the result of performing an action on objects.
- numChanges - optional; type intThe number of objects that were changed as a result of performing the action.
- numChanges - optional; type int
Fault:ApiException (wsdlsoap:fault, use = literal)Source codeApiException type ApiExceptionFaultException class for holding a list of service errors.Base class for exceptions.- message - optional; type stringError message.
- errors - optional, unbounded; type ApiErrorThe API error base class that provides details about an error that occurred while processing a service request.
The OGNL field path is provided for parsers to identify the request data element that may have caused the error.
- fieldPath - optional; type stringThe OGNL field path to identify cause of error.
- fieldPathElements - optional, unbounded; type FieldPathElementA parsed copy of the field path. For example, the field path "operations[1].operand" corresponds to this list: {FieldPathElement(field = "operations", index = 1), FieldPathElement(field = "operand", index = null)}.A segment of a field path. Each dot in a field path defines a new segment.
- field - optional; type stringThe name of a field in lower camelcase. (e.g. "biddingStrategy")
- index - optional; type intFor list fields, this is a 0-indexed position in the list. Null for non-list fields.
- field - optional; type string
- trigger - optional; type stringThe data that caused the error.
- errorString - optional; type stringA simple string representation of the error and reason.
List of errors. - fieldPath - optional; type string
A fault element of type ApiException. - keyAction - optional; type CmsMetadataKeyAction
- performCmsMetadataValueActionDescription:Performs actions on {@link CmsMetadataValue} objects that match the given {@link Statement#query}.Operation type:Request-response. The endpoint receives a message, and sends a correlated message.Input:performCmsMetadataValueActionRequest (wsdlsoap:header, use = literal, part = RequestHeader)Source codeparameters type performCmsMetadataValueActionPerforms actions on {@link CmsMetadataValue} objects that match the given {@link Statement#query}.
- valueAction - optional; type CmsMetadataValueActionRepresents the actions that can be performed on {@link CmsMetadataValue} objects.
- filterStatement - optional; type StatementCaptures the {@code WHERE}, {@code ORDER BY} and {@code LIMIT} clauses of a PQL query. Statements are typically used to retrieve objects of a predefined domain type, which makes SELECT clause unnecessary.
An example query text might be {@code "WHERE status = 'ACTIVE' ORDER BY id LIMIT 30"}.
Statements support bind variables. These are substitutes for literals and can be thought of as input parameters to a PQL query.
An example of such a query might be {@code "WHERE id = :idValue"}.
Statements also support use of the LIKE keyword. This provides wildcard string matching.
An example of such a query might be {@code "WHERE name LIKE '%searchString%'"}.
The value for the variable idValue must then be set with an object of type {@link Value}, e.g., {@link NumberValue}, {@link TextValue} or {@link BooleanValue}.- query - optional; type stringHolds the query in PQL syntax. The syntax is:
[WHERE{[AND | OR] ...}]
[ORDER BY[ASC | DESC]]
[LIMIT {[,] } | { OFFSET }]
:={< | <= | > | >= | = | != }
:={< | <= | > | >= | = | != }
:= IN
:= IS NULL
:= LIKE
:= :
- values - optional, unbounded; type String_ValueMapEntryHolds keys and values for bind variables and their values. The key is the name of the bind variable. The value is the literal value of the variable.
In the example {@code "WHERE status = :bindStatus ORDER BY id LIMIT 30"}, the bind variable, represented by {@code :bindStatus} is named {@code bindStatus}, which would also be the parameter map key. The bind variable's value would be represented by a parameter map value of type {@link TextValue}. The final result, for example, would be an entry of {@code "bindStatus" => StringParam("ACTIVE")}.
This represents an entry in a map with a key of type String and value of type Value.- key - optional; type string
- value - optional; type Value{@code Value} represents a value.
- query - optional; type string
Output:performCmsMetadataValueActionResponse (wsdlsoap:header, use = literal, part = ResponseHeader)Source codeparameters type performCmsMetadataValueActionResponse- rval - optional; type UpdateResultRepresents the result of performing an action on objects.
- numChanges - optional; type intThe number of objects that were changed as a result of performing the action.
- numChanges - optional; type int
Fault:ApiException (wsdlsoap:fault, use = literal)Source codeApiException type ApiExceptionFaultException class for holding a list of service errors.Base class for exceptions.- message - optional; type stringError message.
- errors - optional, unbounded; type ApiErrorThe API error base class that provides details about an error that occurred while processing a service request.
The OGNL field path is provided for parsers to identify the request data element that may have caused the error.
- fieldPath - optional; type stringThe OGNL field path to identify cause of error.
- fieldPathElements - optional, unbounded; type FieldPathElementA parsed copy of the field path. For example, the field path "operations[1].operand" corresponds to this list: {FieldPathElement(field = "operations", index = 1), FieldPathElement(field = "operand", index = null)}.A segment of a field path. Each dot in a field path defines a new segment.
- field - optional; type stringThe name of a field in lower camelcase. (e.g. "biddingStrategy")
- index - optional; type intFor list fields, this is a 0-indexed position in the list. Null for non-list fields.
- field - optional; type string
- trigger - optional; type stringThe data that caused the error.
- errorString - optional; type stringA simple string representation of the error and reason.
List of errors. - fieldPath - optional; type string
A fault element of type ApiException. - valueAction - optional; type CmsMetadataValueAction
Port type CmsMetadataServiceInterfaceSource code
WSDL source code
About wsdl-viewer.xsl
Author: tomi vanek
Download athttp://tomi.vanek.sk/xml/wsdl-viewer.xsl.
The transformation was inspired by the article
Uche Ogbuji: WSDL processing with XSLT