IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Advanced development topics > Assuring Quality of Service > Quality of service qualifier reference

Business object (BO) instance data validation qualifier

A data validation qualifier confirms that the data passed in to an operation matches the XSD types of the operation's inputs. It can be used to validate instance data from a business object.

The runtime validator that underlies this qualifier checks the XSD types being passed by a business object are those that were expected by the client.When you add the qualifier to a Javaâ„¢ interface, only the business objects (passed in as data objects) are validated.

Location: Set the data validation qualifier on a WSDL interface. You can apply the qualifier at three levels of a component or import:

• For all of its interfaces

• For an individual interface

• For an individual operation of an interface

Settings: The data validation qualifier can have these settings:

• Log error and continue (default) - If an error is encountered, the error is logged and the requested operation is performed. There is no guarantee that the service can handle data that is not valid, so a runtime error could result.
• Throw exception - If an error is encountered, an exception is thrown and the operation is not performed.

Programming notes

Verifying data in this way limits performance. When performance is a critical consideration, you should not use this qualifier.

The IBM Integration Designer qualifier is supported by the BO instance validator in IBM BPM.

You can access the API information about that qualifier in the IBM BPM documentation.

The following tables list the specific validation checks that are performed on the business object XSD by the data validation feature. They show which data types and constraints are supported (S), not supported (NS), or partially supported (PS) by the validator. An empty cell indicates that the pair is not supported according to the XML Schema 1.1 specification.

Built-in primitive types

Â	Length	minLength	maxLength	Pattern	Enumeration	minInclusive	maxInclusive	minExclusive	maxExclusive	totalDigits	fractionDigits
String	S	S	S	P	S	Â	Â	Â	Â	Â	Â
boolean	Â	Â	Â	S	Â	Â	Â	Â	Â	Â	Â
Decimal	Â	Â	Â	P	S	S	S	S	S	S	S
precisionDecimal	Â	Â	Â	P	S	S	S	S	S	S	Â
float	Â	Â	Â	P	S	S	S	S	S	Â	Â
double	Â	Â	Â	P	S	S	S	S	S	Â	Â
duration	Â	Â	Â	P	P	P	P	P	P	Â	Â
dateTime	Â	Â	Â	P	S	S	S	S	S	Â	Â
Time	Â	Â	Â	P	P	P	P	P	P	Â	Â
Date	Â	Â	Â	P	S	S	S	S	S	Â	Â
gYearMonth	Â	Â	Â	P	S	S	S	S	S	Â	Â
gYear	Â	Â	Â	P	S	S	S	S	S	Â	Â
gMonthDay	Â	Â	Â	P	P	P	P	P	P	Â	Â
gDay	Â	Â	Â	P	P	P	P	P	P	Â	Â
gMonth	Â	Â	Â	P	P	P	P	P	P	Â	Â
hexBinary	S	S	S	S	S	Â	Â	Â	Â	Â	Â
base64Binary	S	S	S	S	S	Â	Â	Â	Â	Â	Â
anyURI	S	S	S	S	S	Â	Â	Â	Â	Â	Â
QName	N	N	N	N	S	Â	Â	Â	Â	Â	Â
NOTATION	S	S	S	S	S	Â	Â	Â	Â	Â	Â

If s about Table 1: The following descriptions explain why some of the XML types are not supported, or are only partially supported.

• Pattern is a constraint on the value space of a data type which is achieved by constraining the lexical space to literals which match each member of a set of patterns. But only the value space is available for the BO run time, it is hard for the BO run time to support the lexical space.

  For example, A Pattern for Decimal is "\+[0-9]*.[0-9]*" (a decimal with a plus sign). "+9.9" should be a valid one. But when "+9.9" is loaded into the runtime environment, it would be "9.9". Then the validator would report pattern validation error.

• Duration is only partially supported because it requires the validator to compare two strings. For these data types– gMonthDay, gDay, gMonth– the corresponding java type is java.lang.String. Consider this example: The time value `09:30:41+08:00' is greater than time value `09:30:40' with string comparison, while the former is in fact less than the latter with time comparison.

• For QName type, the BO instance data validator does not support length, minLength, maxLength and pattern facet validation. The value space of QName is the set of tuples {namespace URI, local part}. For length, minLength and maxLength, according to XSD specification 1.1, any value is valid. And these three facets are deprecated. It is impossible to apply a pattern on a namespace URI.

Â	Length	minLength	maxLength	Pattern	Enumeration	minInclusive	maxInclusive	minExclusive	maxExclusive	totalDigits	fractionDigits
anySimpleType	Â	Â	Â	Â	Â	Â	Â	Â	Â	Â	Â
anyAtomicType	Â	Â	Â	Â	Â	Â	Â	Â	Â	Â	Â
normalizedString	S	S	S	S	S	Â	Â	Â	Â	Â	Â
Token	S	S	S	S	S	Â	Â	Â	Â	Â	Â
Language	S	S	S	S	S	Â	Â	Â	Â	Â	Â
NMTOKEN	S	S	S	S	S	Â	Â	Â	Â	Â	Â
NMTOKENS	S	S	S	S	S	Â	Â	Â	Â	Â	Â
Name	S	S	S	S	S	Â	Â	Â	Â	Â	Â
NCNAME	S	S	S	S	S	Â	Â	Â	Â	Â	Â
ID	S	S	S	S	S	Â	Â	Â	Â	Â	Â
IDREF	S	S	S	S	S	Â	Â	Â	Â	Â	Â
IDREFS	S	S	S	S	S	Â	Â	Â	Â	Â	Â
ENTITY	S	S	S	S	S	Â	Â	Â	Â	Â	Â
ENTITIES	S	S	S	S	S	Â	Â	Â	Â	Â	Â
Integer	Â	Â	Â	P	S	S	S	S	S	S	S
nonPositiveInteger	Â	Â	Â	S	S	S	S	S	S	S	S
negativeInteger	Â	Â	Â	S	S	S	S	S	S	S	S
Long	Â	Â	Â	P	S	S	S	S	S	S	S
Int	Â	Â	Â	P	S	S	S	S	S	S	S
Short	Â	Â	Â	P	S	S	S	S	S	S	S
Byte	Â	Â	Â	S	S	S	S	S	S	S	S
nonNegativeInteger	Â	Â	Â	S	S	S	S	S	S	S	S
unsignedLong	Â	Â	Â	S	S	S	S	S	S	S	S
unsignedInt	Â	Â	Â	S	S	S	S	S	S	S	S
unsignedShort	Â	Â	Â	S	S	S	S	S	S	S	S
unsignedByte	Â	Â	Â	S	S	S	S	S	S	S	S
positiveInteger	Â	Â	Â	S	S	S	S	S	S	S	S
yearMonthDuration	Â	Â	Â	S	P	P	P	P	P	P	P
dayTimeDuration	Â	Â	Â	S	P	P	P	P	P	P	P

Quality of service qualifier reference