WAS v8.5 > Reference > Developer best practices

Validation and error handling for user-defined value sets

The UDDI registry user console performs validation while a save tModel entity request is built, that is, before the publish occurs.

For example, if you try to add two customTaxonomy:displayName keyedReference elements, the following message is displayed:

Advice: Only one 'urn:x-ibm:uddi:customTaxonomy:displayName' key name is 
allowed for the 'Other' taxonomy.

If a keyedReference element containing a keyName value that starts with urn:x-ibm:uddi:customTaxonomy: is followed by anything other than displayName, the following message is displayed:

Advice: Only key name values of 'urn:x-ibm:uddi:customTaxonomy:displayName' 
are supported.

For requests where the save_tModel entity message might have multiple tModel entities, if any one of the tModel entities is a categorization tModel entity and it fails validation, the request fails with a UDDIInvalidValueException plus additional information to explain the cause, and none of the tModel entities is published. For example:

E_invalidValue (20200) A value that was passed in a keyValue attribute did not 
pass validation.  This applies to checked categorizations, identifiers and 
other validated code lists. The error text will clearly indicate the key and 
value combination that failed validation. Invalid 'customTaxonomy:dbKey' 
keyValue [naics] in keyedReference. KeyValue already in use by 
tModelKey[UUID:C0B9FE13-179F-413D-8A5B-5004DB8E5BB2]

Related

Use the UDDI registry

Reference:

Publish a checked categorization tModel entity
Load user-defined value set data
Enable support for a user-defined value set

+

Search Tips   |   Advanced Search