CWUDX

CWUDX0001E: Caught UDDIException on {0}.
Explanation The JAXR provider caught a org.uddi4j.UDDIException while sending a request to the UDDI registry.
Action The user should interrogate the cause UDDIException of the JAXRException for more information.
CWUDX0002E: Caught TransportException sending request to registry.
Explanation The JAXR provider caught a TransportException while sending a request to the UDDI registry.
Action The user should interrogate the cause TransportException of the JAXRException for more information.
CWUDX0003E: AccessURI and TargetBinding are mutually exclusive.
Explanation An attempt was made to set both the AccessURI and the TargetBinding of a ServiceBinding.
Action The user should set only one of AccessURI and TargetBinding.
CWUDX0004E: Source object of an Association must be an Organization.
Explanation The object passed to the setSourceObject method was not an Organization.
Action The user should only pass Organization objects to the setSourceObject method.
CWUDX0005E: Source and target objects of an Association must be set in order to save.
Explanation An attempt was made to save an Association that did not have both source and target objects set.
Action The user should only attempt to save Associations which have both source and target objects set.
CWUDX0006E: Target object of an Association must be an Organization.
Explanation The object passed to the setTargetObject method was not an Organization.
Action The user should only pass Organization objects to the setTargetObject method.
CWUDX0007E: Format of associationKey is incorrect. Correct format is <sourceObjectKey>:<targetObjectKey>:<associationType> : {0}
Explanation The user passed an associationKey that did not have the correct format.
Action The user should ensure that associationKeys passed to the deleteAssociations method have the correct format.
CWUDX0008E: AssociationType Concept must come from the AssociationType enumeration, and have value either HasChild, HasParent, RelatedTo or EquivalentTo.
Explanation When finding Associations, the user passed a Concept in the associationTypes Collection that was from the AssociationType enumeration, but did not have a value that is valid for UDDI. When saving Associations, the user passed an Association whose associationType Concept was from the AssociationType enumeration, but did not have a value that is valid for UDDI.
Action The user should only use Concepts for associationTypes that are from the AssociationType enumeration and have value either HasChild, HasParent, RelatedTo or EquivalentTo.
CWUDX0009E: AssociationType Concept must come from the AssociationType enumeration.
Explanation When finding Associations, the user passed a Concept that was not from the AssociationType enumeration in the associationTypes Collection. When saving Associations, the user passed an Association whose associationType Concept was not from the AssociationType enumeration.
Action The user should only use Concepts from the AssociationType enumeration for associationTypes.
CWUDX0010E: Cannot create a ClassificationScheme from a taxonomy Concept.
Explanation The user passed a taxonomy Concept to the createClassificationScheme method.
Action This method is provided to allow for Concepts returned by the BusinessQueryManager.findConcepts call to be safely converted to ClassificationScheme. It is up to the programmer to make sure that the Concept is indeed semantically a ClassificationScheme.
CWUDX0011E: Connection is closed.
Explanation The user called a method that required a connection to the registry after they had closed the Connection by calling the Connection.close() method.
Action The user should not call methods that require a connection to the registry after the Connection has been closed.
CWUDX0012E: ConnectionFactory properties are not set.
Explanation The createConnection() method was called before the properties had been set on the ConnectionFactory.
Action Ensure that the ConnectionFactory properties have been set before attempting to create a Connection.
CWUDX0013E: Could not create DocumentBuilder.
Explanation The JAXR provider caught a javax.xml.parsers.ParserConfigurationException while attempting to initialize the XML parser.
Action The user should interrogate the cause ParserConfigurationException of the JAXRException for more information.
CWUDX0014E: Could not parse XML input stream.
Explanation The JAXR provider caught a java.io.IOException while attempting to parse the XML request.
Action The user should interrogate the cause IOException of the JAXRException for more information.
CWUDX0015E: Could not serialize XML response.
Explanation The JAXR provider caught a java.io.IOException while attempting to serialize the XML response.
Action The user should interrogate the cause IOException of the JAXRException for more information.
CWUDX0016E: Interface name of object to create not specifed.
Explanation The user passed a null interfaceName to the createObject method.
Action The user should ensure they only pass a valid interfaceName to the createObject method.
CWUDX0017W: Enumeration data file {0} contains an invalid line: {1}
Explanation The JAXR provider has encountered an invalid line in an enumeration data file while the Connection is initialized. The JAXR provider will ignore the invalid line and will be unaffected.
Action The user should ensure that the enumeration data file is valid in order to use all members of the enumeration. The correct format of each line is <enumeration name><separator char><concept value>.
CWUDX0018E: Could not read enumeration data file: {0}
Explanation The JAXR provider caught a java.io.IOException while attempting to read an enumeration data file.
Action The user should interrogate the cause IOException of the JAXRException for more information.
CWUDX0019W: enumerationConfig.properties file contains an invalid property value: {0}
Explanation The JAXR provider has encountered an invalid property value in the enumerationConfig.properties file while the Connection is initializsed. The JAXR provider will ignore the invalid property, and hence ignore the corresponding enumeration.
Action The user should ensure that the enumerationConfig.properties file is valid in order to use all enumerations. The correct format of each line is <enumeration ID>=<enumeration name>,<data filename>,<separator char>
CWUDX0020E: An IOException occurred while attempting to read the enumerationConfig.properties file.
Explanation The JAXR provider caught a java.io.IOException while attempting to read the enumerationConfig.properties file.
Action The user should interrogate the cause IOException of the JAXRException for more information.
CWUDX0021E: An IOException occurred while attempting to read the taxonomyConfig.properties file.
Explanation The JAXR provider caught a java.io.IOException while attempting to read the taxonomyConfig.properties file.
Action The user should interrogate the cause IOException of the JAXRException for more information.
CWUDX0022E: External URI is malformed: {0}
Explanation A malformed URI was passed to the setExternalURI method when URI validation has set to true by passing true to the ExternalLink.setValidateURI(boolean validate) method.
Action Either the user should ensure that the URI is well formed, or URI validation should be set to false.
CWUDX0023E: External URI is not accessible: {0}
Explanation An inaccessible URI was passed to the setExternalURI method when URI validation has set to true by passing true to the ExternalLink.setValidateURI(boolean validate) method.
Action Either the user should ensure that the URI is accessible, or URI validation should be set to false.
CWUDX0024E: Invalid interface name: {0}
Explanation The user passed an invalid interface name to the createObject method.
Action The user should only pass valid interface names to the createObject method. Valid interface names are public final static String fields of the LifeCycleManager class.
CWUDX0025E: Cannot change the ClassificationScheme of an internal Classification.
Explanation The user called the setClassificationScheme method of an internal Classification.
Action The user should not attempt to modify the ClassificationScheme of an internal Classification directly. The ClassificationScheme of an internal Classification is determined by the Classification's Concept and cannot be modified independently.
CWUDX0026E: Cannot change the name of an internal Classification.
Explanation The user called the setName method of an internal Classification.
Action The user should not attempt to modify the name of an internal Classification directly. The name of an internal Classification is determined by the Classification's Concept and cannot be modified independently.
CWUDX0027E: Cannot change the value of an internal Classification.
Explanation The user called the setValue method of an internal Classification.
Action The user should not attempt to modify the value of an internal Classification directly. The value of an internal Classification is determined by the Classification's Concept and cannot be modified independently.
CWUDX0028E: The Concept of an internal Classification must have a parent ClassificationScheme.
Explanation The user passed a non-null Concept without a parent ClassificationScheme to the setConcept method.
Action Setting a Classification's Concept causes a Classification to become internal. The Classification's ClassificationScheme is then set to the parent ClassificationScheme of the Concept. If the Concept has no parent ClassificationScheme (that is, it is not a taxonomy Concept), that is invalid. The user should therefore only pass taxonomy Concepts to the setConcept method.
CWUDX0029E: Taxonomy Concepts cannot be saved as UDDI tModels.
Explanation The user attempted to save a taxonomy Concept as a UDDI tModel in the registry.
Action Taxonomy Concepts cannot be saved as tModels in a UDDI registry. They are used to classify objects saved in the registry but cannot be saved independently. The user should not attempt to save taxonomy Concepts in the registry.
CWUDX0030E: The parent RegistryObject of a taxonomy Concept must be either a Concept or a ClassificationScheme.
Explanation The user attempted to create a taxonomy Concept whose parent was not a Concept or a ClassificationScheme.
Action The parent of a taxonomy Concept can only be another Concept or a ClassificationScheme, so the user should only attempt to set one of these as the parent of a taxonomy Concept.
CWUDX0031E: Concept does not have a parent, therefore does not have a path.
Explanation The user called the getPath() method on a Concept that was not a taxonomy Concept. Only taxonomy Concepts have parents.
Action Only taxonomy Concepts have parents, therefore only taxonomy Concepts have paths. The user should not attempt to call the getPath() method on a Concept that is not a taxonomy Concept.
CWUDX0032E: Concept does not have a value, therefore does not have a path.
Explanation The user called the getPath() method on a Concept that did not have a value.
Action A Concept must have a value in order to have a path, so the user should not attempt to call the getPath() method on Concepts that do not have a value.
CWUDX0033E: Concept's parent ClassificationScheme does not have an ID, therefore the Concept does not have a path.
Explanation The user called the getPath() method on a Concept whose ClassificationScheme did not have an ID.
Action A Concept's ClassificationScheme must have an ID in order for the Concept to have a path. The user should not attempt to call the getPath() method on a Concept whose ClassificationScheme does not have an ID.
CWUDX0034E: The ConnectionFactory property javax.xml.registry.uddi.maxRows does not contain a parsable integer: {0}
Explanation The user called the createConnection method when the ConnectionFactory property javax.xml.registry.uddi.maxRows did not contain a parsable integer.
Action The user should ensure that if the javax.xml.registry.uddi.maxRows ConnectionFactory property is set that it contains a parsable integer.
CWUDX0035E: Invalid UDDI XML String.
Explanation The String passed to the makeRegistrySpecificRequest method was not valid XML.
Action The user should ensure that the String passed to the makeRegistrySpecificRequest method is valid XML.
CWUDX0036E: The ConnectionFactory property javax.xml.registry.lifeCycleManagerURL specifies a malformed URL.
Explanation The user called the createConnection method when the ConnectionFactory property javax.xml.registry.lifeCycleManagerURL contained a malformed URL.
Action The user should ensure that the javax.xml.registry.lifeCycleManagerURL ConnectionFactory property contains a well formed URL.
CWUDX0037E: The ConnectionFactory property javax.xml.registry.queryManagerURL specifies a malformed URL.
Explanation The user called the createConnection method when the ConnectionFactory property javax.xml.registry.queryManagerURL contained a malformed URL.
Action The user should ensure that the javax.xml.registry.queryManagerURL ConnectionFactory property contains a well formed URL.
CWUDX0038E: Multiple matches on find ClassificationScheme by name.
Explanation More than one ClassificationScheme was found that matched the search criteria.
Action The user should narrow their search criteria to find only one ClassificationScheme.
CWUDX0039E: Invalid objectType: {0}
Explanation The user passed an invalid objectType.
Action The user should ensure they pass a valid objectType.
CWUDX0040E: Cannot save objects of type: {0}
Explanation An object was passed to the saveObjects method of a type that cannot be saved directly in the registry.
Action The user should ensure that objects passed to the saveObjects method are of a valid type. Valid types are Association, ClassificationScheme, Concept, Organization, Service and ServiceBinding.
CWUDX0041E: RegistryObject is a ClassificationScheme not a Concept: {0}
Explanation An objectType of LifeCycleManager.CONCEPT was passed, but the id or one of the objectKeys was that of a ClassificationScheme.
Action The user should ensure that they specify the correct objectType corresponding to the object keys.
CWUDX0042E: RegistryObject is a Concept not a ClassificationScheme: {0}
Explanation An objectType of LifeCycleManager.CLASSIFICATIONSCHEME was passed, but the id or one of the objectKeys was that of a Concept.
Action The user should ensure that they specify the correct objectType corresponding to the object keys.
CWUDX0043E: RequestID not found: {0}
Explanation The requestId specified was not found.
Action The user should only pass valid requestIds to the getBulkResponse method. Note that once the getBulkResponse method has been called once for a particular requestId, that requestId is removed from the cache and subsequent calls to getBulkResponse passing that requestId will result in an InvalidRequestException.
CWUDX0044E: {0} is not a valid path of a concept in a defined internal taxonomy.
Explanation The javax.xml.registry.semanticEquivalences ConnectionFactory property defines a semantic equivalence between a Concept in the PostalAddressAttributes enumeration and a Concept which has not been defined in any internal taxonomy.
Action The user should ensure that the Concept paths used in the javax.xml.registry.semanticEquivalences ConnectionFactory property have been defined in a internal taxonomy.
CWUDX0045W: Semantic equivalence pair does not have exactly 2 elements: {0}
Explanation The javax.xml.registry.semanticEquivalences ConnectionFactory contains a keyPair which contains more than two elements.
Action The user should ensure that the javax.xml.registry.semanticEquivalences ConnectionFactory property has the correct format, as defined in the JAXR specification.
CWUDX0046E: Semantic equivalence pair does not contain a key in the postalAddressAttributes enumeration: {0}
Explanation The javax.xml.registry.semanticEquivalences ConnectionFactory contains a keyPair which does not contain the path of a Concept in the PostalAddressAttributes enumeration. Semantic equivalences for a UDDI JAXR providers are only allowed for Concepts in the PostalAddressAttributes enumeration.
Action The user should only attempt to define semantic equivalences for Concepts in the PostalAddressAttributes enumeration.
CWUDX0047E: Invalid Slot name: {0}.
Explanation The user passed an invalid slot name to one of the methods of the ExtensibleObject interface.
Action The user should ensure that the slot name is valid for the particular instance of ExtensibleObject.
CWUDX0048E: A Slot instance cannot have duplicate values.
Explanation The user passed a collection of values to the setValues method that contained duplicate values.
Action The user should pass only a collection of unique values to setValues method.
CWUDX0049E: A sortCode Slot must have only 1 value.
Explanation The user passed a Slot with name Slot.SORT_CODE_SLOT and multiple values to the addSlot method.
Action When adding a Slot with name Slot.SORT_CODE_SLOT to a PostalAddress, the user should ensure that it only has 1 value.
CWUDX0050E: A SpecificationLink can have only one ExternalLink.
Explanation The user attempted to give a SpecificationLink more than one ExternalLink. A SpecificationLink may only have one ExternalLink.
Action The user should give a SpecificationLink a maximum of one ExternalLink.
CWUDX0051E: A SpecificationLink can have only one UsageParameter.
Explanation The user attempted to give the SpecificationLink more than one usage parameter. A SpecificationLink can only have one usage parameter.
Action The user should give a SpecificationLink a maximum of one usage parameter.
CWUDX0052E: SpecificationObject must be a Concept with no parent.
Explanation The user attempted to set a Concept with a parent (that is, a taxonomyConcept) as the specification object of the SpecificationLink.
Action The user must set a specification Concept as the specification object of a SpecificationLink.
CWUDX0053E: SpecificationObject must be a Concept.
Explanation The user attempted to set a RegistryObject that was not a Concept as the specification object of a SpecificationLink.
Action The user must set a specification Concept as the specification object of a SpecificationLink.
CWUDX0054E: Invalid escape sequence found during SQL-92 LIKE processing: {0}
Explanation The user passed a namePattern to one of the above methods which contained an invalid escape sequence.
Action The user should ensure that namePatterns do not contain invalid escape sequences.
CWUDX0055E: Invalid escape sequence found terminating pattern during SQL-92 LIKE processing: {0}
Explanation The user passed a namePattern to one of the above methods which contained an invalid escape sequence terminating the pattern.
Action The user should ensure that namePatterns do not contain invalid escape sequences.
CWUDX0056E: The System property http.proxyPort does not contain a parsable integer: {0}
Explanation The user called the createConnection() method when the System property http.proxyPort contained a String that was not parsable as an integer.
Action The user should ensure that if the System property http.proxyPort is set it contains a parsable integer.
CWUDX0057W: Taxonomy data file {0} contains an invalid line: {1}
Explanation A taxonomy data file contains an invalid line.
Action The format of each line is <taxonomy ID><Concept name><Concept value><Concept parent>
CWUDX0058W: Warning: Unable to locate parentConcept named {0} for concept named {1} in taxonomy datafile {2}.
Explanation A taxonomy data file contains an line for a Concept whose parent cannot be located in that file.
Action The user should ensure that a parent exists for each Concept in the taxonomy data file.
CWUDX0059E: Could not read taxonomy data file: {0}
Explanation The JAXR provider caught a java.io.IOException while attempting to read the taxonomy data file.
Action The user should interrogate the cause IOException of the JAXRException for more information.
CWUDX0060W: taxonomyConfig.properties file contains an invalid property value: {0}
Explanation An invalid property value in the taxonomyConfig.properties file while the Connection is initialized. The JAXR provider will ignore the invalid property, and hence ignore the corresponding taxonomy.
Action The user should ensure that the taxonomyConfig.properties file is valid in order to use all taxonomies. The correct format of each line is <taxonomy ID>=<tModelKey>,<data filename>,<separator char>.
CWUDX0061E: Expecting object of type: {0}. Got object of type: {1}.
Explanation The user passed an object to a method that was not expecting an object of that type.
Action The user should only pass objects of the appropriate type to JAXR methods.
CWUDX0062E: Expecting object of type String or LocalizedString. Got object of type: {0}.
Explanation The user passed an object which was not a String or a LocalizedString as a namePattern to a query method.
Action The user should only use Strings of LocalizedStrings as namePattern objects.
CWUDX0063E: The ConnectionFactory property javax.xml.registry.queryManagerURL is not specified.
Explanation The user attempted to create a Connection without specifying the javax.xml.registry.queryManagerURL ConnectionFactory property.
Action The user must specify the javax.xml.registry.queryManagerURL ConnectionFactory property before attempting to create a Connection.
CWUDX0064E: Unsupported value for the ConnectionFactory property javax.xml.registry.security.authenticationMethod: {0}
Explanation The user attempted to create a Connection with an invalid value of the javax.xml.registry.security.authenticationMethod ConnectionFactory property.
Action The user should only use a valid vale for this property. Valid values are UDDI_GET_AUTHTOKEN and HTTP_BASIC.
CWUDX0065E: Classification does not have a Concept (Classification is external). When using a JAXR Provider for UDDI, ServiceBinding can only be classified with a sub-concept of the URLType enumeration.
Explanation The user attempted to classify a ServiceBinding using an external Classification, which therefore is not a Classification with a sub-Concept of the internal URLType enumeration.
Action The user should only classify a ServiceBinding using a sub-Concept of the internal URLType enumeration.
CWUDX0066E: Classification's Concept is not from the URLType enumeration. When using a JAXR Provider for UDDI, ServiceBinding can only be classified with a sub-concept of the URLType enumeration.
Explanation The user attempted to classify a ServiceBinding using an internal Classification that has a Concept which is not a sub-Concept of the internal URLType enumeration.
Action The user should only classify a ServiceBinding using a sub-Concept of the URLType enumeration.
Reference topic    

Terms and conditions for information centers | Feedback

Last updated: Jun 13, 2012 3:34:38 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.html

© Copyright IBM Corporation 2006, 2011. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)