Project Errors (100 – 126)

This section lists TopLink Workbench project errors.

100: The project caches all statments by default for queries, but does not bind all parameters.

Cause: A named query that caches statements must also bind parameters.

Action: On the Named Queries – Options tab, change the Cache Statements field to False, or change the Bind Parameters field to True.

101: The project uses a custom sequence table, but the counter field is not specified.

Cause: On the project's Sequencing tab, you selected Use Custom Sequence Table, but did not complete the Counter Field field.

Action: Select the field to use as the Counter Field for this sequence table. See "Configuring Sequencing at the Project Level" for details.

102: The project uses a custom sequence table, but the name field is not specified.

Cause: On the project's Sequencing tab, you selected Use Custom Sequence Table, but did not complete the Name Field field.

Action: Select the field to use as the Name Field for this sequence table. See "Configuring Sequencing at the Project Level" for details.

113: The method specified for the inheritance policy's class extraction method on this descriptor is no longer a visible member of this class.

Cause: You changed the class hierarchy within the project, causing the inheritance policy to no longer be visible to the class.

Action: Ensure that the inheritance policy is visible to the class. See "Descriptors and Inheritance".

117: The reference must have at least one field association.

Cause: You selected a table reference for a relationship mapping, but did not define a source and target field key pair.

Action: For variable one-to-one mappings, you must define a query key pair (in the source descriptor's tables) to use for the common query key.

118: The selected parent descriptor for this descriptor's inheritance policy does not have an associated inheritance policy.

Cause: You selected a Parent Descriptor for a descriptor's inheritance policy that does not have an inheritance policy.

Action: Ensure that the parent descriptor's inheritance policy is valid. See "Descriptors and Inheritance".

120: The source reference does not contain any field associations.

Cause: You created a many-to-many mapping, but did not define a source and target reference for the source reference.

Action: You must define a table reference and the appropriate key pairs for each source reference. See "Configuring Table and Field References (Foreign and Target Foreign Keys)".

121: The target reference does not contain any field associations.

Cause: You created a many-to-many mapping, but did not define a source and target reference for the target reference.

Action: You must define a table reference and the appropriate key pairs for each target reference. See "Configuring Table and Field References (Foreign and Target Foreign Keys)".

122: There is no database associated with the query key [query key name].

Cause: You did not associate the specified query key with a database table.

Action: You must select a database Name and Table on the Query Keys tab.

123: This root class has no class indicator mappings for its hierarchy.

Cause: You created an inheritance policy with the Use Class Indicator Dictionary option but did not specify the indicator values for all subclasses.

Action: Specify the indicator values for all subclasses on the descriptor's Inheritance tab. See "Configuring Inheritance for a Child (Branch or Leaf) Class Descriptor".

Note: TopLink displays a list of each subclass and indicator value if you have identified the subclasses' parent descriptor.

126: Writable mappings defined for the class indicator field [field name].

Cause: The class indicator field should not contain any writable mappings.

Action: Select a Use Class Indicator Field on the descriptor's Inheritance tab that does not contain any writable mappings. See "Configuring Inheritance for a Child (Branch or Leaf) Class Descriptor" and "Configuring Inherited Attribute Mapping in a Subclass".