Descriptor Exceptions (1 – 200)
DescriptorException
is a development exception that is raised when insufficient information is provided to the descriptor. The message that is returned includes the name of the descriptor or mapping that caused the exception. If a mapping within the descriptor caused the error, then the name and parameters of the mapping are part of the returned message, as shown in Example 13-1.
Internal exception, mapping and descriptor appear only if TopLink has enough information about the source of the problem to provide this information.
Format
EXCEPTION [TOPLINK – error code]: Exception name
EXCEPTION DESCRIPTION: Message
INTERNAL EXCEPTION: Message
MAPPING: Database mapping
DESCRIPTOR: Descriptor
Example 13-1 Descriptor Exception
EXCEPTION [TOPLINK – 75]: oracle.toplink.exceptions.DescriptorException
EXCEPTION DESCRIPTION: The reference class is not specified.
-
1: ATTRIBUTE_AND_MAPPING_WITH_INDIRECTION_ MISMATCH
-
Cause: attributeName
is not declared as type ValueHolderInterface
, but the mapping uses indirection. The mapping is set to use indirection, but the related attribute is not defined as type ValueHolderInterface
. It is raised on foreign reference mappings.
-
Action: If you want to use indirection on the mapping, change the attribute to type ValueHolderInterface
. Otherwise, change the mapping associated with the attribute so that it does not use indirection.
-
2: ATTRIBUTE_AND_MAPPING_WITHOUT_INDIRECTION_ MISMATCH
-
Cause: attributeName
is declared as type ValueHolderInterface
, but TopLink is unable to use indirection. The attribute is defined to be of type ValueHolderInterface
, but the mapping is not set to use indirection. It is raised on foreign reference mappings.
-
Action: If you do not want to use indirection on the mapping, change the attribute so it is not of type ValueHolderInterface
. Otherwise, change the mapping associated with the attribute to use indirection.
-
6: ATTRIBUTE_NAME_NOT_SPECIFIED
-
Cause: The attribute name is missing or not specified in the mapping definition.
-
Action: Specify the attribute name in the mapping by calling the method setAttributeName(String attributeName)
.
-
7: ATTRIBUTE_TYPE_NOT_VALID
-
Cause: When using Java 2, the specified attributeName
is not defined as type vector
, or a type that implements the Map
or Collection
interface. This occurs in one-to-many mapping, many-to-many mapping, and collection mapping when mapping is set not to use indirection, and the attribute type is not declared.
-
Action: Declare the attribute to be of type java.util.Vector
.
-
8: CLASS_INDICATOR_FIELD_NOT_FOUND
-
Cause: The class indicator field is defined, but the descriptor is set to use inheritance. When using inheritance, a class indicator field or class extraction method must be set. The class indicator field is used to create the right type of domain object.
-
Action: Set either a class indicator field or class extraction method.
-
9: DIRECT_FIELD_NAME_NOT_SET
-
Cause: The direct field name from the target table is not set in the direct collection mapping.
-
Action: Specify the direct field name by calling the method setDirectFieldName(String fieldName)
.
-
10: FIELD_NAME_NOT_SET_IN_MAPPING
-
Cause: The field name is not set in the mapping. It is raised from direct to field mapping, array mapping, and structure mapping.
-
Action: Specify the field name by calling the method setFieldName(String fieldName)
.
-
11: FOREIGN_KEYS_DEFINED_INCORRECTLY
-
Cause: One-to-one mapping foreign key is defined incorrectly. Multiple foreign key fields were set for one-to-one mapping by calling the method setForeignKeyFieldName(String fieldName)
.
-
Action: Use the method addForeignKeyFieldName(String sourceForeignKeyName
, String targetPrimaryKeyFieldName)
to add multiple foreign key fields.
-
12: IDENTITY_MAP_NOT_SPECIFIED
-
Cause: The descriptor must use an identity map to use the Check cache does exist option. The descriptor has been set not to use identity map, but the existence checking is set to be performed on identity map.
-
Action: Either use identity map, or set the existence checking to some other option.
-
13: ILLEGAL_ACCESS_WHILE_GETTING_VALUE_THRU_ INSTANCE_VARIABLE_ACCESSOR
-
Cause: TopLink is unable to access the attributeName
instance variable in object objectName
. The instance variable in the domain object is not accessible. This exception is raised when TopLink tries to access the instance variable using the java.lang.reflect
Java package. The error is a purely Java exception, and TopLink wraps only the reflection exception.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
14: ILLEGAL_ACCESS_WHILE_CLONING
-
Cause: TopLink is unable to clone the object domainObject
because the clone method methodName
is not accessible. The method name specified using useCloneCopyPolicy(String cloneMethodName)
or the clone()
method to create the clone on the domain object, is not accessible by TopLink using Java reflection. The error is a purely Java exception, and TopLink wraps only the reflection exception.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
15: ILLEGAL_ACCESS_WHILE_CONSTRUCTOR_INSTANTIATION
-
Cause: The domain class does not define a public default constructor, which TopLink needs to create new instances of the domain class.
-
Action: Define a public default constructor or use a different instantiation policy.
-
16: ILLEGAL_ACCESS_WHILE_EVENT_EXECUTION
-
Cause: The descriptor callback method eventMethodName
with DescriptorEvent
as an argument is not accessible. This exception is raised when TopLink tries to access the event method using Java reflection. The error is a purely Java exception, and TopLink wraps only the reflection exception.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
17: ILLEGAL_ACCESS_WHILE_GETTING_VALUE_THRU_ METHOD_ACCESSOR
-
Cause: Trying to invoke inaccessible methodName
on the object objectName
. The underlying get accessor method to access an attribute in the domain object is not accessible. This exception is raised when TopLink tries to access an attribute through a method using the java.lang.reflect
Java package. The error is a purely Java exception, and TopLink wraps only the reflection exception.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
18: ILLEGAL_ACCESS_WHILE_INSTANTIATING_METHOD_ BASED_PROXY
-
Cause: The method used by the transformation mapping using a valueholder is invalid. This exception is raised when TopLink tries to access the method using Java reflection. The problem occurs when the method base valueholder is instantiated.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
19: ILLEGAL_ACCESS_WHILE_INVOKING_ATTRIBUTE_METHOD
-
Cause: On transformation mapping, the underlying attribute method that is used to retrieve values from the database row while reading the transformation mapped attribute is not accessible.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
20: ILLEGAL_ACCESS_WHILE_INVOKING_FIELD_TO_METHOD
-
Cause: On transformation mapping, the method methodName
that is used to retrieve value from the object while writing the transformation mapped attribute is not accessible. The error is a purely Java exception, and TopLink wraps only the reflection exception.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
21: ILLEGAL_ACCESS_WHILE_INVOKING_ROW_EXTRACTION_ METHOD
-
Cause: TopLink was unable to extract data row
, because TopLink cannot access the row specified in the databaseRow
argument of the method. The method to extract class from row on the domain object is not accessible. The error is a purely Java exception, and TopLink wraps only the reflection exception.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
22: ILLEGAL_ACCESS_WHILE_METHOD_INSTANTIATION
-
Cause: TopLink is unable to create a new instance, because the method methodName
that creates instances on the domain class is not accessible. The error is a purely Java exception, and TopLink wraps only the reflection exception.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
23: ILLEGAL_ACCESS_WHILE_OBSOLETE_EVENT_EXECUTION
-
Cause: The descriptor callback method eventMethodName
with Session
as an argument is inaccessible. This exception is raised when TopLink tries to access the event method using Java reflection. The error is a purely Java exception, and TopLink wraps only the reflection exception.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
24: ILLEGAL_ACCESS_WHILE_SETTING_VALUE_THRU_ INSTANCE_VARIABLE_ACCESSOR
-
Cause: The attributeName
instance variable in the object objectName
is not accessible through Java reflection. The error is raised by Java, and TopLink wraps only the reflection exception.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
25: ILLEGAL_ACCESS_WHILE_SETTING_VALUE_THRU_ METHOD_ACCESSOR
-
Cause: TopLink is unable to invoke a method setMethodName
on the object with parameter parameter
. The attribute's set accessor method is not accessible through Java reflection. The error is raised by Java and TopLink wraps only the reflection exception.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
26: ILLEGAL_ARGUMENT_WHILE_GETTING_VALUE_ THRU_INSTANCE_VARIABLE_ACCESSOR
-
Cause: TopLink is unable to get a value for an instance variable attributeName
of type typeName
from the object. The specified object is not an instance of the class or interface declaring the underlying field. An object is accessed to get the value of an instance variable that does not exist.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
27: ILLEGAL_ARGUMENT_WHILE_GETTING_VALUE_THRU_ METHOD_ACCESSOR
-
Cause: TopLink is unable to invoke method methodName
on the object objectName
. The get accessor method declaration on the domain object differs from the one that is defined. The number of actual and formal parameters differ, or an unwrapping conversion has failed.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
28: ILLEGAL_ARGUMENT_WHILE_INSTANTIATING_METHOD_ BASED_PROXY
-
Cause: The method that the method-based proxy uses in a transformation mapping is receiving invalid arguments when the valueholder is being instantiated. This exception is raised when TopLink tries to access the method using the java.lang.reflect
Java package.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
29: ILLEGAL_ARGUMENT_WHILE_INVOKING_ATTRIBUTE_ METHOD
-
Cause: The number of actual and formal parameters differ, or an unwrapping conversion has failed. On transformation mapping, the method used to retrieve values from the database row while reading the transformation mapped attribute is getting an invalid argument.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
30: ILLEGAL_ARGUMENT_WHILE_INVOKING_FIELD_TO_ METHOD
-
Cause: The number of actual and formal parameters differs for method methodName
, or an unwrapping conversion has failed. On transformation mapping, the method used to retrieve value from the object while writing the transformation mapped attribute is getting an invalid argument. The error is a purely Java exception, and TopLink wraps only the reflection exception.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
31: ILLEGAL_ARGUMENT_WHILE_OBSOLETE_EVENT_ EXECUTION
-
Cause: The number of actual and formal parameters for the descriptor callback method eventMethodName
differs, or an unwrapping conversion has failed. The callback event method is invoked with an invalid argument. This exception is raised when TopLink tries to invoke the event method using Java reflection. The error is a purely Java exception, and TopLink wraps only the reflection exception.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
32: ILLEGAL_ARGUMENT_WHILE_SETTING_VALUE_THRU_ INSTANCE_VARIABLE_ACCESSOR
-
Cause: An invalid value is being assigned to the attribute instance variable. TopLink is unable to set a
value
for an instance variable
attributeName
of type
typeName
in the object. The specified object is not an instance of the class or interface that is declaring the underlying field, or an unwrapping conversion has failed.
TopLink assigns value by using Java reflection. Java raises the error and TopLink wraps only the reflection exception.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
33: ILLEGAL_ARGUMENT_WHILE_SETTING_VALUE_THRU _METHOD_ACCESSOR
-
Cause: An illegal argument is being passed to the attribute's set accessor method. TopLink is unable to invoke method setMethodName
on the object. The number of actual and formal parameters differs, or an unwrapping conversion has failed. Java raises the error and TopLink wraps only the reflection exception.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
34: INSTANTIATION_WHILE_CONSTRUCTOR_INSTANTIATION
-
Cause: The class does not define a public default constructor, or the constructor raised an exception. This error occurs when you invoke the default constructor for the domain object to create a new instance of the object while building new domain objects if:
-
The class represents an abstract class, an interface, an array class, a primitive type, or void.
-
The instantiation fails for some other reason.
Java raises the error and TopLink wraps only the reflection exception.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
35: INVALID_DATA_MODIFICATION_EVENT
-
Cause: Applications should never encounter this exception. This exception usually occurs at the time of developing TopLink, although in cases where the developer writes new mapping, it is possible to get this exception. In direct collection mapping and many-to-many mapping, the target table and relational table are populated at the end of the commit process, and if a data modification event is sent to any other mapping, then this exception is raised.
-
Action: Contact Oracle Support Services.
-
36: INVALID_DATA_MODIFICATION_EVENT_CODE
-
Cause: An application should never encounter this exception. This exception usually occurs at the time of developing TopLink, although in cases where developers write new mappings, it is possible to get this exception. In direct collection mapping and many-to-many mapping, the target table and relational table are populated at the end of the commit process, and if a data modification event is sent to these two mappings with wrong event code, then this exception is raised.
-
Action: Contact Oracle Support Services.
-
37: INVALID_DESCRIPTOR_EVENT_CODE
-
Cause: An application should never encounter this exception. This exception usually occurs at the time of developing TopLink. The exception means that the descriptor event manager does not support the event code passed in the event.
-
Action: Contact Oracle Support Services.
-
38: INVALID_IDENTITY_MAP
-
Cause: The identity map constructor failed because an invalid identity map was specified. The identity map class given in the descriptor cannot be instantiated. The exception is a Java exception that is raised by a Java reflection when TopLink instantiates the identity map class. TopLink wraps only the Java exception.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
39: JAVA_CLASS_NOT_SPECIFIED
-
Cause: The descriptor does not define a Java class. The Java class is not specified in the descriptor.
-
Action: Specify the Java Class.
-
40: DESCRIPTOR_FOR_INTERFACE_IS_MISSING
-
Cause: A descriptor for the referenced interface is not added to the session.
-
Action: Add that descriptor to the session.
-
41: MAPPING_FOR_SEQUENCE_NUMBER_FIELD
-
Cause: A non-read-only mapping is not defined for the sequence number field. A mapping is required so that TopLink can put and extract values for the primary key.
-
Action: Define a mapping.
-
43: MISSING_CLASS_FOR_INDICATOR_FIELD_VALUE
-
Cause: TopLink is missing the class for indicator field value classFieldValue
of type type
. There was no class entry found in the inheritance policy for the indicator field value that was read from the database. It is likely that the method addClassIndicator(Class class, Object typeValue)
was not called for the field value. The class and typeValue
are stored in a hash table, and later the class is extracted from the hash table by passing typeValue
as a key. Because Integer(1)
is not equivalent to Float(1)
, this exception occurs when the type of typeValue
is incorrectly specified.
-
Action: Verify the descriptor.
-
44: MISSING_CLASS_INDICATOR_FIELD
-
Cause: The class indicator field is missing from the database row
that was read from the database. This is performed in the inheritance model where after reading rows from the database, child domain objects are to be constructed depending upon the type indicator values.
-
Action: Verify the printed row for correct spelling.
-
45: MISSING_MAPPING_FOR_FIELD
-
Cause: TopLink is missing a mapping for field
; a mapping for the field is not specified.
-
Action: Define a mapping for the field.
-
46: NO_MAPPING_FOR_PRIMARY_KEY
-
Cause: A mapping for the primary key is not specified. There should be one non-read-only mapping defined for the primary key field.
-
Action: Define a mapping for the primary key.
-
47: MULTIPLE_TABLE_PRIMARY_KEY_NOT_SPECIFIED
-
Cause: The multiple table primary key mapping must be specified when a custom multiple table join is used. If multiple tables are specified in the descriptor and the join expression is customized, then the primary keys for all the tables must be specified. If the primary keys are not specified, then the exception occurs.
-
Action: Call the method addMultipleTablePrimaryKeyFieldName(String fieldNameInPrimaryTable, String fieldNameInSecondaryTable)
on the descriptor to set the primary keys.
-
48: MULTIPLE_WRITE_MAPPINGS_FOR_FIELD
-
Cause: Multiple writable mappings for the field
fieldName
are defined in the descriptor. Exactly one must be defined as writable; the others must be specified as read-only. When multiple write mappings are defined for the field, TopLink is unable to choose the appropriate mapping for writing the value of the field in the database row. Therefore, the exception is raised during the validation process of descriptors.
The most common cause of this problem occurs when the field has direct-to-field mapping, as well as one-to-one mapping. In this case, the one-to-one mapping must either be read-only or a target foreign key reference.
-
Action: Make one of those mappings read-only.
-
49: NO_ATTRIBUTE_TRANSFORMATION_METHOD
-
Cause: The attribute transformation method name in the transformation mapping is not specified. This method is invoked internally by TopLink to retrieve value to store in the domain object.
-
Action: Define a method and set the method name on the mapping by calling the method setAttributeTransformation(String methodName)
.
-
50: NO_FIELD_NAME_FOR_MAPPING
-
Cause: No field name is specified in direct-to-field mapping.
-
Action: Set the field by calling setFieldName(String fieldName)
.
-
51: NO_FOREIGN_KEYS_ARE_SPECIFIED
-
Cause: Neither the selection criteria nor the foreign keys were specified on one-to-one mapping. If the selection criterion is not specified, then TopLink tries to build one from the foreign keys specified in the mapping.
-
Action: Specify the fields.
-
52: NO_REFERENCE_KEY_IS_SPECIFIED
-
Cause: No query key named queryKey
is found in descriptor
. No reference key from the target table is specified on direct collection mapping.
-
Action: Specify the fields by calling the method setReferenceKeyFieldName(String fieldName)
.
-
53: NO_RELATION_TABLE
-
Cause: The relation table name is not set in this many-to-many mapping.
-
Action: Set the relation table name by calling the method setRelationTableName(String tableName)
.
-
54: NO_SOURCE_RELATION_KEYS_SPECIFIED
-
Cause: There are no source relation keys specified in this many-to-many mapping.
-
Action: Add source relation keys to the mapping.
-
55: NO_SUCH_METHOD_ON_FIND_OBSOLETE_METHOD
-
Cause: TopLink cannot find the descriptor callback method selector
on the domain class. It must take a Session
or a DescriptorEvent
as its argument. TopLink tries to invoke the method using Java reflection. It is a Java exception and TopLink is wrapping only the main exception.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
56: NO_SUCH_METHOD_ON_INITIALIZING_ATTRIBUTE_METHOD
-
Cause: TopLink cannot find the method attributeMethodName
with parameters databaseRow
or databaseRow
, session
. TopLink wraps the Java reflection exception that is caused when the method is being created from the method name. This method is set by calling setAttributeMethodName(String aMethodName)
.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
57: NO_SUCH_METHOD_WHILE_CONSTRUCTOR_INSTANTIATION
-
Cause: The constructor is inaccessible to TopLink. TopLink wraps the Java reflection exception that is caused when it is creating a new instance of the domain.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
58: NO_SUCH_METHOD_WHILE_CONVERTING_TO_METHOD
-
Cause: TopLink failed to find a method with signature methodName
or methodName(oracle.toplink.sessions.Session)
. TopLink wraps the Java reflection exception that was raised by its attempt to create a Method
type (java.lang.reflect) from the method names in the transformation mapping.
-
Action: Ensure that the method methodName
is defined on the domain class that owns the attribute mapped by the transformation mapping.
-
59: NO_SUCH_FIELD_WHILE_INITIALIZING_ATTRIBUTES_ IN_INSTANCE_VARIABLE_ACCESSOR
-
Cause: The instance variable attributeName
is not defined in the domain class, or it is not accessible. TopLink wraps the Java reflection exception that is caused when it is creating a Field
type (java.lang.reflect.Field
) from the attribute name.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
60: NO_SUCH_METHOD_WHILE_INITIALIZING_ ATTRIBUTES_IN_METHOD_ACCESSOR
-
Cause: The method setMethodName
or getMethodName
is not defined for the attribute in the domain class javaClassName
, or it is not accessible. TopLink wraps the Java reflection exception that is caused when it is creating a Method
type from the method name.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
61: NO_SUCH_METHOD_WHILE_INITIALIZING_CLASS_EXTRACTION_METHOD
-
Cause: The static class extraction method methodName
with databaseRow
as an argument does not exist, or is not accessible. A Java reflection exception wrapped in a TopLink exception is raised when a class extraction method is being created from the method name in the inheritance policy.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
62: NO_SUCH_METHOD_WHILE_INITIALIZING_COPY_POLICY
-
Cause: The clone method methodName
with no arguments does not exist, or is not accessible. A Java reflection exception wrapped in a TopLink exception is raised when a method to create clones is being created from the method name in the copy policy.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
63: NO_SUCH_METHOD_WHILE_INITIALIZING_INSTANTIATION_POLICY
-
Cause: The instance creation method methodName
with no arguments does not exist, or is not accessible. A Java reflection exception wrapped in a TopLink exception is raised when a method to create the new instance is being created from the method name in the instantiation policy.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
64: NO_TARGET_FOREIGN_KEYS_SPECIFIED
-
Cause: The foreign keys in the target table are not specified in one-to-many mappings. These fields are not required if a selection criterion is given in the mapping, but otherwise they must be specified.
-
Action: Set target foreign keys or selection criteria.
-
65: NO_TARGET_RELATION_KEYS_SPECIFIED
-
Cause: There are no target relation keys specified in many-to-many mappings.
-
Action: Call method addTargetRelationKeyFieldName(String targetRelationKeyFieldName
, String targetPrimaryKeyFieldName)
to set the fields.
-
66: NOT_DESERIALIZABLE
-
Cause: The object cannot be deserialized from the byte array that is read from the database. The exception is raised when the serialized object mapping is converting the byte array into an object.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
67: NOT_SERIALIZABLE
-
Cause: The object cannot be serialized into a byte array. The exception is raised when a serialized object mapping is converting the object into a byte array.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
68: NULL_FOR_NON_NULL_AGGREGATE
-
Cause: The value of the aggregate in the source object object
is null
. Null values are not allowed for aggregate mappings unless allow null is specified in the aggregate mapping.
-
Action: Call the mapping method allowNull
. Provide parameters only if you are making a distinction between foo()
and foo(integer)
.
-
69: NULL_POINTER_WHILE_GETTING_VALUE_THRU_INSTANCE_VARIABLE_ACCESSOR
-
Cause: An object is accessed to get the value of an instance variable through Java reflection. This exception is raised only on some JVMs.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
70: NULL_POINTER_WHILE_GETTING_VALUE_THRU_METHOD_ACCESSOR
-
Cause: The getter method is invoked to get the value of an attribute through Java reflection. This exception is raised only on some JVM.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
71: NULL_POINTER_WHILE_SETTING_VALUE_THRU_INSTANCE_VARIABLE_ACCESSOR
-
Cause: A null pointer exception has been raised while setting the value of the attributeName
instance variable in the object to value. An object is accessed to set the value of an instance variable through Java reflection. This exception is raised only on some JVMs.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
72: NULL_POINTER_WHILE_SETTING_VALUE_THRU_METHOD_ACCESSOR
-
Cause: A null pointer exception has been raised while setting the value through setMethodName
method in the object with an argument argument
. The set accessor method is invoked to set the value of an attribute through Java reflection. This exception is raised only on some JVMs.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
73: PARENT_DESCRIPTOR_NOT_SPECIFIED
-
Cause: TopLink is unable to find the descriptor for the parent class. The descriptor of a subclass has no parent descriptor.
-
Action: The method setParentClass(Class parentClass)
must be called on the subclass descriptor.
-
74: PRIMARY_KEY_FIELDS_NOT_SPECIFIED
-
Cause: The primary key fields are not set for this descriptor.
-
Action: Add primary key field names using method setPrimaryKeyFieldName(String fieldName)
.
-
75: REFERENCE_CLASS_NOT_SPECIFIED
-
Cause: The reference class is not specified in the foreign reference mapping.
-
Action: Set the reference class by calling the method setReferenceClass(Class aClass)
.
-
77: REFERENCE_DESCRIPTOR_IS_NOT_AGGREGATE
-
Cause: The referenced descriptor for className
should be set to an aggregate descriptor. An aggregate mapping should always reference a descriptor that is aggregate.
-
Action: Call the method descriptorIsAggregate
on the referenced descriptor.
-
78: REFERENCE_KEY_FIELD_NOT_PROPERLY_SPECIFIED
-
Cause: The table for the reference field must be the reference table. If the reference field name that is specified in the direct collection mapping is qualified with the table name, then the table name should match the reference table name.
-
Action: Qualify the field with the proper name, or change the reference table name.
-
79: REFERENCE_TABLE_NOT_SPECIFIED
-
Cause: The reference table name in the direct collection mapping is not specified.
-
Action: Use the method setReferenceTableName(String tableName)
on the mapping to set the table name.
-
80: RELATION_KEY_FIELD_NOT_PROPERLY_SPECIFIED
-
Cause: The table for the relation key field must be the relation table. If the source and target relation fields names that are specified in the many-to-many mapping are qualified with the table name, then the table name should match the relation table name.
-
Action: Qualify the field with the proper name, or change the relation table name.
-
81: RETURN_TYPE_IN_GET_ATTRIBUTE_ACCESSOR
-
Cause: The method attributeMethodName
that is specified in the transformation mapping should have a return type set in the attribute because this method is used to extract value from the database row.
-
Action: Verify the method and make appropriate changes.
-
82: SECURITY_ON_FIND_METHOD
-
Cause: The descriptor callback method selector
with DescriptorEvent
as an argument is not accessible. Java raises a security exception when a Method
type is created from the method name using Java reflection. The method is a descriptor event callback on the domain object that takes DescriptorEvent
as its parameter.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
83: SECURITY_ON_FIND_OBSOLETE_METHOD
-
Cause: The descriptor callback method selector
with session
as an argument is not accessible. Java raises a security exception when a Method
type is created from the method name using Java reflection. The method is a descriptor event callback on the domain object, which takes class and session as its parameters.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
84: SECURITY_ON_INITIALIZING_ATTRIBUTE_METHOD
-
Cause: Access to the method attributeMethodName
with parameters databaseRow
or databaseRow
, Session
has been denied. Java raises a security exception when a Method
type is created from the attribute method name using Java reflection. The attribute method that is specified in the transformation mapping is used to extract value from the database row and set by calling setAttributeTransformation(String methodName)
.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
85: SECURITY_WHILE_CONVERTING_TO_METHOD
-
Cause: TopLink failed to find a method with signature methodName()
or methodName(oracle.toplink.sessions.Session)
. Java raises a security exception when a Method
type is created from the method name using Java reflection. These are the methods that extract the field value from the domain object in the transformation mapping.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
86: SECURITY_WHILE_INITIALIZING_ATTRIBUTES_IN_INSTANCE_VARIABLE_ACCESSOR
-
Cause: Access to the instance variable attributeName
in the class javaClassName
is denied. Java raises a security exception when creating a Field
type from the given attribute name using Java reflection.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
87: SECURITY_WHILE_INITIALIZING_ATTRIBUTES_IN_METHOD_ACCESSOR
-
Cause: The methods setMethodName
and getMethodName
in the object javaClassName
are inaccessible. Java raises a security exception when creating a Method
type from the given attribute accessor method name using Java reflection.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
88: SECURITY_WHILE_INITIALIZING_CLASS_ EXTRACTION_METHOD
-
Cause: The static class extraction method methodName
with DatabaseRow
as an argument is not accessible. Java raises a security exception when creating a Method
type from the given class extraction method name using Java reflection. The method is used to extract the class from the database row in the inheritance policy.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
89: SECURITY_WHILE_INITIALIZING_COPY_POLICY
-
Cause: The clone method methodName
with no arguments is inaccessible. Using ClassDescriptor
method useCloneCopyPolicy
(java.lang.String methodName
), you can specify that the creation of clones within a unit of work is done by sending the methodName
method to the original object. If the clone method methodName
with no arguments is inaccessible (your application does not have sufficient privileges to call the method), Java raises a security exception when reflectively accessing the method with the given method name using the java.lang.reflect
Java package.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
90: SECURITY_WHILE_INITIALIZING_INSTANTIATION_POLICY
-
Cause: The instance creation method methodName
with no arguments is inaccessible. Using any of the ClassDescriptor
methods useFactoryInstantiationPolicy
(java.lang.Class factoryClass
, java.lang.String methodName
), useFactoryInstantiationPolicy
(java.lang.Class factoryClass
, java.lang.String
methodName
, java.lang.String factoryMethodName
), useFactoryInstantiationPolicy
(java.lang.Object factory
, java.lang.String
methodName
), or useMethodInstantiationPolicy
(java.lang.String
staticMethodName
), you can specify how new instances are created. If any of the methods or factory methods are inaccessible (your application does not have sufficient privileges to call the method), Java raises a security exception when reflectively accessing the method with the given method name using the java.lang.reflect
Java package.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
91: SEQUENCE_NUMBER_PROPERTY_NOT_SPECIFIED
-
Cause: Either the sequence field name or the sequence number name is missing. To use sequence-generated IDs, both the sequence number name and field name properties must be set.
-
Action: To use sequence-generated IDs, set both the sequence number name and field name properties.
-
92: SIZE_MISMATCH_OF_FOREIGN_KEYS
-
Cause: The size of the primary keys on the target table does not match the size of the foreign keys on the source in one-to-one mapping.
-
Action: Verify the mapping and the reference descriptor's primary keys.
-
93: TABLE_NOT_PRESENT
-
Cause: The table tableName
is not present in the descriptor.
-
Action: Verify the qualified field names that are specified in the mappings and descriptor so that any fields that are qualified with the table name reference the correct table.
-
94: TABLE_NOT_SPECIFIED
-
Cause: No table is specified in the descriptor. The descriptor must have a table name defined.
-
Action: Call the method addTableName(String tableName)
or setTableName(String tableName)
to set the tables on the descriptor.
-
96: TARGET_FOREIGN_KEYS_SIZE_MISMATCH
-
Cause: The size of the foreign keys on the target table does not match the size of the source keys on the source table in the one-to-many mapping.
-
Action: Verify the mapping.
-
97: TARGET_INVOCATION_WHILE_CLONING
-
Cause: TopLink has encountered a problem in cloning the object domainObject
clone method. The methodName
triggered an exception. Java raises this exception when the cloned object is invoked while the object is being cloned. The clone method is specified on the copy policy that is usually invoked to create clones in unit of work.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
98: TARGET_INVOCATION_WHILE_EVENT_EXECUTION
-
Cause: A descriptor callback method eventMethodName
that includes a DescriptorEvent
as argument is not accessible. The exception occurs when the descriptor event method is invoked using Java reflection.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
99: TARGET_INVOCATION_WHILE_GETTING_VALUE_THRU_METHOD_ACCESSOR
-
Cause: The method methodName
on the object objectName
is throwing an exception. Java is throwing an exception while getting an attribute value from the object through a method accessor.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
100: TARGET_INVOCATION_WHILE_INSTANTIATING_METHOD_BASED_PROXY
-
Cause: A method has raised an exception. Java raises this exception while instantiating a method based proxy and instantiating transformation mapping.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
101: TARGET_INVOCATION_WHILE_INVOKING_ATTRIBUTE_METHOD
-
Cause: The underlying method raises an exception. Java is throwing an exception while invoking an attribute transformation method on transformation mapping. The method is invoked to extract value from the database row to set into the domain object.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
102: TARGET_INVOCATION_WHILE_INVOKING_FIELD_TO_METHOD
-
Cause: The method methodName
is throwing an exception. Java is throwing exception while invoking field transformation method on transformation mapping. The method is invoked to extract value from the domain object to set into the database row.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
103: TARGET_INVOCATION_WHILE_INVOKING_ROW_EXTRACTION_METHOD
-
Cause: TopLink encountered a problem extracting the class type from row row
while invoking a class extraction method.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
104: TARGET_INVOCATION_WHILE_METHOD_INSTANTIATION
-
Cause: TopLink is unable to create a new instance. The creation method methodName
caused an exception.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
105: TARGET_INVOCATION_WHILE_OBSOLETE_EVENT_EXECUTION
-
Cause: The underlying descriptor callback method eventMethodName
with session
as argument raises an exception. Java is throwing an exception while invoking a descriptor event method that takes a session as its parameter.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
106: TARGET_INVOCATION_WHILE_SETTING_VALUE_THRU_METHOD_ACESSOR
-
Cause: The method setMethodName
on the object raises an exception. Java is throwing an exception while invoking a set accessor method on the domain object to set an attribute value into the domain object.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
108: VALUE_NOT_FOUND_IN_CLASS_INDICATOR_MAPPING
-
Cause: The indicator value is not found in the class indicator mapping in the parent descriptor for the class.
-
Action: Verify the addClassIndicator(Class childClass, Object typeValue)
on the inheritance policy.
-
109: WRITE_LOCK_FIELD_IN_CHILD_DESCRIPTOR
-
Cause: The child descriptor has a write-lock field defined. This is unnecessary, because it inherits any required locking from the parent descriptor.
-
Action: Check your child descriptor, and remove the field.
-
110: DESCRIPTOR_IS_MISSING
-
Cause: The descriptor for the reference class className
is missing from the mapping.
-
Action: Verify the session to see if the descriptor for the reference class was added.
-
111: MULTIPLE_TABLE_PRIMARY_KEY_MUST_BE_FULLY_QUALIFIED
-
Cause: Multiple table primary key field names are not fully qualified. These field names are given on the descriptor if it has more than one table.
-
Action: Specify the field names with the table name.
-
112: ONLY_ONE_TABLE_CAN_BE_ADDED_WITH_THIS_METHOD
-
Cause: You have tried to enter more than one table through this method.
-
Action: Use the method addTableName(String tableName)
to add multiple tables to the descriptor.
-
113: NULL_POINTER_WHILE_CONSTRUCTOR_INSTANTIATION
-
Cause: The constructor is inaccessible. Java is throwing this exception while invoking a default constructor to create new instances of the domain object.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
114: NULL_POINTER_WHILE_METHOD_INSTANTIATION
-
Cause: The new instance methodName
creation method is inaccessible. Java is throwing an exception while calling a method to a build new instance of the domain object. This method is given by the user to override the default behavior of creating new instances through a class constructor.
-
Action: Inspect the internal exception, and refer to the Java documentation.
-
115: NO_ATTRIBUTE_VALUE_CONVERSION_TO_FIELD_VALUE_PROVIDED
-
Cause: The field conversion value for the attribute value attributeValue
was not given in the object type mapping.
-
Action: Verify the attribute value, and provide a corresponding field value in the mapping.
-
116: NO_FIELD_VALUE_CONVERSION_TO_ATTRIBUTE_VALUE_PROVIDED
-
Cause: The attribute conversion value for the fieldValue
was not given in the object type mapping.
-
Action: Verify the field value, and provide a corresponding attribute value in the mapping.
-
118: LOCK_MAPPING_CANNOT_BE_READONLY
-
Cause: The domain object className
cannot have a read-only mapping for the write-lock fields when the version value is stored in the object.
-
Action: Verify the mappings on the write-lock fields.
-
119: LOCK_MAPPING_MUST_BE_READONLY
-
Cause: The domain object className
does not have a read-only mapping for the write-lock fields when the version value is stored in the cache.
-
Action: Verify the mappings on write-lock fields.
-
120: CHILD_DOES_NOT_DEFINE_ABSTRACT_QUERY_KEY
-
Cause: The query key queryKeyName
is defined in the parent descriptor but not in the child descriptor. The descriptor has not defined the abstract query key.
-
Action: Define any class that implements the interface descriptor by the abstract query key in the interface descriptor.
-
122: SET_EXISTENCE_CHECKING_NOT_UNDERSTOOD
-
Cause: The interface descriptor parent
does not have at least one abstract query key defined. The string given to the method setExistenceChecking(String token)
is not understood.
-
Action: Contact Oracle Support Services.
-
125: VALUE_HOLDER_INSTANTIATION_MISMATCH
-
Cause: The DatabaseMapping for the attribute getAttributeName()
uses indirection and must be initialized to a new value holder.
-
Action: Ensure that the mapping uses indirection and that the attribute is initialized to a new value holder.
-
126: NO_SUB_CLASS_MATCH
-
Cause: No subclass matches this class theClass
when inheritance is in aggregate relationship mapping.
-
Action: Verify the subclass and the relationship mapping.
-
127: RETURN_AND_MAPPING_WITH_INDIRECTION_MISMATCH
-
Cause: The return type of the method used to get the attribute getAttributeName
()
of DatabaseMapping is not declared as type ValueHolderInterface
, but the mapping is using indirection.
-
Action: Verify that the method used to get the attribute named getAttributeName
()
of DatabaseMapping returns a value holder, or change the mapping so it does not use indirection.
-
128: RETURN_AND_MAPPING_WITHOUT_INDIRECTION_MISMATCH
-
Cause: The return type of the method used to get the attribute getAttributeName
()
of DatabaseMapping is declared as type ValueHolderInterface
, but the mapping is not using indirection.
-
Action: Ensure that the mapping is using indirection, or change the return type from value holder.
-
129: PARAMETER_AND_MAPPING_WITH_INDIRECTION_MISMATCH
-
Cause: The return type of the method used to set the attribute getAttributeName()
of DatabaseMapping is not declared as type ValueHolderInterface
, but the mapping is using indirection.
-
Action: Ensure that the set method parameter is declared as a valueholder, or change the mapping so it does not use indirection.
-
130: PARAMETER_AND_MAPPING_WITHOUT_INDIRECTION_MISMATCH
-
Cause: The return type of the method used to set the attribute getAttributeName()
of DatabaseMapping is declared as type ValueHolderInterface
, but the mapping is not using indirection.
-
Action: Ensure that the mapping is changed to use indirection, or that the method parameter is not declared as a value holder.
-
131: GET_METHOD_RETURN_TYPE_NOT_VALID
-
Cause: The return type of the method used to get the attribute getAttributeName()
of DatabaseMapping is not declared as type Vector
(or a type that implements the Map
or Collection
interface if using Java 2).
-
Action: Declare the return type of the method used to get the attribute getAttributeName()
of DatabaseMapping as type Vector
(or a type that implements the map or collection interface if using Java 2).
-
133: SET_METHOD_PARAMETER_TYPE_NOT_VALID
-
Cause: The parameter type of the method used to set the attribute getAttributeName()
of DatabaseMapping is not declared as type Vector
(or a type that implements the map or collection interface, if using Java 2).
-
Action: Declare the parameter type of the method used to set the attribute getAttributeName()
of DatabaseMapping as type Vector
(or a type that implements the Map
or Collection
interface, if using Java 2).
-
135: ILLEGAL_TABLE_NAME_IN_MULTIPLE_TABLE_FOREIGN_KEY
-
Cause: The table in the multiple table foreign key relationship refers to an unknown table.
-
Action: Verify the table name.
-
138: ATTRIBUTE_AND_MAPPING_WITH_TRANSPARENT_INDIRECTION_MISMATCH
-
Cause: The attribute getAttributeName()
of DatabaseMapping is not declared as a supertype of validTypeName
, but the mapping is using transparent indirection.
-
Action: Verify the attribute's type and the mapping setup.
-
139: RETURN_AND_MAPPING_WITH_TRANSPARENT_INDIRECTION_MISMATCH
-
Cause: The return type of the method used to get the attribute getAttributeName()
of DatabaseMapping is not declared as a super-type of validTypeName
, but the mapping is using transparent indirection.
-
Action: Verify the attribute's type and the mapping setup.
-
140: PARAMETER_AND_MAPPING_WITH_TRANSPARENT_INDIRECTION_MISMATCH
-
Cause: The parameter type of the method used to set the attribute getAttributeName()
of DatabaseMapping is not declared as a supertype of validTypeName
, but the mapping is using transparent indirection.
-
Action: Verify the attribute's type and the mapping setup.
-
141: FIELD_IS_NOT_PRESENT_IN_DATABASE
-
Cause: The field fieldname
is not present in the table tableName
in the database.
-
Action: Verify the field name for the attribute.
-
142: TABLE_IS_NOT_PRESENT_IN_DATABASE
-
Cause: The table whose name is provided by the Descriptor
method getTableName
is not present in the database.
-
Action: Verify the table name for the descriptor.
-
143: MULTIPLE_TABLE_INSERT_ORDER_MISMATCH
-
Cause: The multiple table insert order vector specified the Descriptor
method getMultipleTableInsertOrder
has fewer or more tables than are specified in the Descriptor
method getTables. All the tables must be included in the insert order vector.
-
Action: Ensure that all table names for the descriptor are present and that there are no extra tables.
-
144: INVALID_USE_OF_TRANSPARENT_INDIRECTION
-
Cause: Transparent indirection is being used with a mapping other than a CollectionMapping
.
-
Action: Verify the mapping. It must be a collection mapping.
-
145: MISSING_INDIRECT_CONTAINER_CONSTRUCTOR
-
Cause: The indirect container class does not implement the constructor.
-
Action: Implement the constructor for the container.
-
146: COULD_NOT_INSTANTIATE_INDIRECT_CONTAINER_CLASS
-
Cause: TopLink is unable to instantiate the indirect container class using the constructor.
-
Action: Validate the constructor for the indirect container class.
-
147: INVALID_CONTAINER_POLICY
-
Cause: You have used a container policy with an incompatible version of the JDK. This container policy must only be used with JDK 1.3.1 or later.
-
Action: Validate the container policy being used.
-
148: INVALID_CONTAINER_POLICY_WITH_TRANSPARENT_ INDIRECTION
-
Cause: The container policy is incompatible with transparent indirection.
-
Action: Change the container policy to be compatible with transparent indirection, or do not use transparent indirection.
-
149: INVALID_USE_OF_NO_INDIRECTION
-
Cause: NoIndirectionPolicy
objects should not receive this message.
-
Action: Contact Oracle Support Services.
-
150: INDIRECT_CONTAINER_INSTANTIATION_MISMATCH
-
Cause: The mapping for the attribute mapping.getAttributeName()
uses transparent indirection and must be initialized to an appropriate container.
-
Action: Initialize the mapping to an appropriate container.
-
151: INVALID_MAPPING_OPERATION
-
Cause: An invalid mapping operation has been used.
-
Action: See the documentation for valid mapping operations.
-
152: INVALID_INDIRECTION_POLICY_OPERATION
-
Cause: An invalid indirection policy operation has been used.
-
Action: See the documentation for valid indirection policy operations.
-
153: REFERENCE_DESCRIPTOR_IS_NOT_AGGREGATECOLLECTION
-
Cause: The reference descriptor for className
is not set to an aggregate collection descriptor.
-
Action: Set the reference descriptor to an aggregate collection descriptor.
-
154: INVALID_INDIRECTION_CONTAINER_CLASS
-
Cause: An invalid indirection container class has been used.
-
Action: Verify the container class.
-
155: MISSING_FOREIGN_KEY_TRANSLATION
-
Cause: The mapping does not include a foreign key field linked to the primary key field.
-
Action: Link the foreign key to the appropriate primary key.
-
156: STRUCTURE_NAME_NOT_SET_IN_MAPPING
-
Cause: The structure name is not set.
-
Action: Set the structure name appropriately.
-
157: NORMAL_DESCRIPTORS_DO_NOT_SUPPORT_ NON_RELATIONAL_EXTENSIONS
-
Cause: Relational descriptors do not support non-relational extensions.
-
Action: Contact Oracle Support Services.
-
158: PARENT_CLASS_IS_SELF
-
Cause: The descriptor's parent class has been set to itself.
-
Action: Contact Oracle Support Services.
-
159: PROXY_INDIRECTION_NOT_AVAILABLE
-
Cause: An attempt to use proxy indirection has been made, but JDK 1.3.1 or later is not being used.
-
Action: Use JDK 1.3.1 or later.
-
160: INVALID_ATTRIBUTE_TYPE_FOR_PROXY_INDIRECTION
-
Cause: The attribute was not specified in the list of interfaces given to use proxy indirection.
-
Action: Verify the attribute.
-
161: INVALID_GET_RETURN_TYPE_FOR _PROXY_INDIRECTION
-
Cause: The return type for the indirection policy is invalid for the indirection policy.
-
Action: Ensure that the parameter type of the getter method is correct for the indirection policy.
-
162: INVALID_SET_PARAMETER_TYPE_FOR_PROXY_ INDIRECTION
-
Cause: The parameter for the setter method is incorrect for the indirection type.
-
Action: Ensure that the parameter type of the setter method is correct for the indirection policy.
-
163: INCORRECT_COLLECTION_POLICY
-
Cause: The container policy is invalid for the collection type.
-
Action: Ensure that the container policy is correct for the collection type.
-
164: INVALID_AMENDMENT_METHOD
-
Cause: The amendment method that is provided is invalid, not public, or cannot be found.
-
Action: Ensure that the amendment method is public, static, returns void, and has a single argument: Descriptor
.
-
165: ERROR_OCCURRED_IN_AMENDMENT_METHOD
-
Cause: The specified amendment method threw an exception.
-
Action: Examine the returned exception for further information.
-
166: VARIABLE_ONE_TO_ONE_MAPPING_IS_NOT_DEFINED
-
Cause: There is no mapping for the attribute.
-
Action: Validate the mapping and attribute.
-
167: NO_CONSTRUCTOR_INDIRECT_COLLECTION_CLASS
-
Cause: A valid constructor was not found for the indirection container class.
-
Action: Add a default constructor or a constructor with a ValueHolderInterface
in the container class.
-
168: TARGET_INVOCATION_WHILE_CONSTRUCTOR_INSTANTIATION
-
Cause: The constructor is missing.
-
Action: Create the required constructor.
-
169: TARGET_INVOCATION_WHILE_CONSTRUCTOR_INSTANTIATION_OF_FACTORY
-
Cause: The constructor is missing.
-
Action: Create the required constructor.
-
170: ILLEGAL_ACCESS_WHILE_CONSTRUCTOR_INSTANTIATION_OF_FACTORY
-
Cause: Permissions do not allow access to the constructor.
-
Action: Adjust the Java security permissions to permit access to the constructor.
-
171: INSTANTIATION_WHILE_CONSTRUCTOR_INSTANTIATION_OF_FACTORY
-
Cause: An instantiation failed inside the associated constructor.
-
Action: Determine which objects are being instantiated, and verify that all are instantiated properly.
-
172: NO_SUCH_METHOD_WHILE_CONSTRUCTOR_INSTANTIATION_OF_FACTORY
-
Cause: A method call from inside the constructor is invalid because this method does not exist.
-
Action: Ensure that the factory has a default constructor for the called method.
-
173: NULL_POINTER_WHILE_CONSTRUCTOR_INSTANTIATION_OF_FACTORY
-
Cause: A method on a null
object was called from inside a constructor. The factory constructor was inaccessible.
-
Action: Examine the internal exception and take the appropriate action.
-
174: ILLEGAL_ACCESS_WHILE_METHOD_INSTANTIATION_OF_FACTORY
-
Cause: A method was called on an object from inside a factory instantiation, and Java has determined this method to be invalid.
-
Action: Determine why the method is invalid, and replace the method with a valid one.
-
175: TARGET_INVOCATION_WHILE_METHOD_INSTANTIATION_OF_FACTORY
-
Cause: A problem was encountered creating factory using creation method. The creation method triggered an exception.
-
Action: Examine the exception and take the corresponding action.
-
176: NULL_POINTER_WHILE_METHOD_INSTANTIATION_OF_FACTORY
-
Cause: A method called to instantiate a factory threw a null pointer exception. The creation method is not accessible.
-
Action: Do not use that method to instantiate a factory.
-
177: NO_MAPPING_FOR_ATTRIBUTENAME
-
Cause: Mapping is missing for the attribute.
-
Action: The attribute must be mapped.
-
178: NO_MAPPING_FOR_ATTRIBUTENAME_IN_ENTITY_BEAN
-
Cause: Cannot find mapping for attribute in entity bean.
-
Action: The attribute must be mapped.
-
179: UNSUPPORTED_TYPE_FOR_BIDIRECTIONAL_RELATIONSHIP_MAINTENANCE
-
Cause: The attribute uses bidirectional relationship maintenance, but has ContainerPolicy
, which does not support it.
-
Action: The attribute must be mapped with a different collection type.
-
180: REFERENCE_DESCRIPTOR_CANNOT_BE_AGGREGATE
-
Cause: No string is defined in the DescriptorExceptionResource.java
file.
-
Action: The reference descriptor for a relationship mapping (except AggregateCollectionMapping
) cannot be aggregate. You must change the reference descriptor to non-aggregate.
-
181: ATTRIBUTE_TRANSFORMER_CLASS_NOT_FOUND
-
Cause: The AttributeTransformer
class cannot be found.
-
Action: Ensure that the AttributeTransformer
class exists and is on the classpath.
-
182: FIELD_TRANSFORMER_CLASS_NOT_FOUND
-
Cause: The FieldTransformer
class cannot be found.
-
Action: Ensure that the FieldTransformer
class exists and is on the classpath.
-
183: ATTRIBUTE_TRANSFORMER_CLASS_INVALID
-
Cause: The class cannot be used as an AttributeTransformer
.
-
Action: Examine the internal exception stack trace and make the appropriate correction.
-
184: FIELD_TRANSFORMER_CLASS_INVALID
-
Cause: The class cannot be used as a FieldTransformer
.
-
Action: Do not use the class as a FieldTransformer
.
-
185: RETURNING_POLICY_FIELD_TYPE_CONFLICT
-
Cause: ReturningPolicy
contains field with two different types.
-
Action: The field was added to ReturningPolicy
twice with different types. The field must be added to ReturningPolicy
once. You must remove excessive addFieldForInsert
and/or addInsertField
calls.
-
186: RETURNING_POLICY_FIELD_INSERT_CONFLICT
-
Cause: ReturningPolicy
contains field that has been added twice using addInsertField
and addInsertFieldReturnOnly
.
-
Action: A field must be added to ReturningPolicy
only once. You must remove excessive addField
calls.
-
187: RETURNING_POLICY_AND_DESCRIPTOR_FIELD_TYPE_CONFLICT
-
Cause: ReturningPolicy
contains field with type [{1}], but the same field in descriptor has type [{2}].
-
Action: Specify field type in addField
method only in the event that it cannot be obtained from the descriptor.
-
188: RETURNING_POLICY_UNMAPPED_FIELD_TYPE_NOT_SET
-
Cause: ReturningPolicy
contains unmapped field that requires type.
-
Action: You must specify field type in the addField
method.
-
189: RETURNING_POLICY_MAPPED_FIELD_TYPE_NOT_SET
-
Cause: ReturningPolicy
contains mapped field that requires type.
-
Action: You must specify field type in the addField
method.
-
190: RETURNING_POLICY_MAPPING_NOT_SUPPORTED
-
Cause: ReturningPolicy
contains a field that is mapped with unsupported mapping.
-
Action: You cannot use ReturningPolicy
with this field. Do not add it to ReturningPolicy
.
-
191: RETURNING_POLICY_FIELD_NOT_SUPPORTED
-
Cause: ReturningPolicy
contains a field that is not supported. Field is either sequence field, class type indicator, or used for locking.
-
Action: You cannot use ReturningPolicy
with this field. Do not add it to ReturningPolicy
.
-
192: CUSTOM_QUERY_AND_RETURNING_POLICY_CONFLICT
-
Cause: ReturningPolicy
contains a field, but custom doesn't output it.
-
Action: Update the custom query so that it outputs a value for this field.
-
193: NO_CUSTOM_QUERY_FOR_RETURNING_POLICY
-
Cause: There is no custom set, but ReturningPolicy
contains one or more fields to be returned and doesn't support generating call with return.
-
Action: Specify a custom InsertObjectQuery
or UpdateObjectQuery
through DescriptorQueryManager
setInsertQuery
, setInsertCall
, setUpdateQuery
, or setUpdateCall
that outputs values for fields added to ReturningPolicy
.
-
194: CLASS_EXTRACTION_METHOD_MUST_BE_STATIC
-
Cause: The class extraction method must be a static method on the descriptor's class.
-
Action: Make the class extraction method a static method on the descriptor's class.
-
195: ISOLATED_DESCRIPTOR_REFERENCED_BY_SHARED_DESCRIPTOR
-
Cause: The shared class must not reference the isolated class.
-
Action: Ensure that the shared class does not reference the isolated class.
-
196: UPDATE_ALL_FIELDS_NOT_SET
-
Cause: UpdateAllFields
has not been set or has been set to false
. When using setForceUpdate(true)
of CMPPolicy you must also call setUpdateAllFields(true)
of CMPPolicy.
-
Action: Ensure that updateAllFields
is set to true
if forceUpdate
is true
.
-
197: INVALID_MAPPING_TYPE
-
Cause: The mapping is not the appropriate type for this descriptor.
-
Action: The mapping type has to map the descriptor type, e.g. relational mapping for relational descriptor, EIS mapping for EIS descriptor, and XML mapping for XML descriptor.
-
198: NEED_TO_IMPLEMENT_CHANGETRACKER
-
Cause: In order to use ObjectChangeTrackingPolicy
or AttributeChangeTrackingPolicy
, the object has to implement the ChangeTracker
interface.
-
Action: Ensure that the object implements ChangeTrackerInterface
in order to use ObjectChangeTrackingPolicy
or AttributeChangeTrackingPolicy
.
-
199: NEED_TO_IMPLEMENT_FETCHGROUPTRACKER
-
Cause: In order to use a fetch group, the domain class has to implement the FetchGroupTracker
interface.
-
Action: Ensure that the domain class implements the FetchGroupTracker
interface in order to use the fetch group.
-
200: ATTEMPT_TO_REGISTER_DEAD_INDIRECTION
-
Cause: Attempt to register an object with dead indirection as a new object. Possibly the object was deleted or removed from the cache during a merge of a serialized clone or did not exist in the cache at the time of the merge. This is a concurrency violation.
-