|
Business Components | |||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Object | +--java.util.ResourceBundle | +--java.util.ListResourceBundle | +--oracle.jbo.common.CheckedListResourceBundle | +--oracle.jbo.CSMessageBundle
Defines the error codes and default error messages for operations on business objects.
These error codes may be localized by extending this class, and overriding
getContents()
to return a table in which the error codes are
associated with other message strings. The subclass should be given a name of the
form CSMessageBundle_locale
, where Locale is
the name of a language.
CSMessageBundle_xx
is an example locale, for the toy language Xx.
CSMessageBundle_xx
Field Summary | |
static java.lang.String |
EXC_AFTER_COMMIT
JBO-26100: AfterCommitException |
static java.lang.String |
EXC_AFTER_POST
JBO-26101: AfterPostException |
static java.lang.String |
EXC_AFTER_ROLLBACK
JBO-26102: AfterRollbackException |
static java.lang.String |
EXC_ALREADY_CONNECTED
JBO-25201: AlreadyConnectedException |
static java.lang.String |
EXC_ALREADY_LOCKED
JBO-26030: AlreadyLockedException |
static java.lang.String |
EXC_AM_ACTIVATE
JBO-25033: JboSerializationException |
static java.lang.String |
EXC_AM_PASSIVATE
JBO-25032: JboSerializationException |
static java.lang.String |
EXC_APPMODULE_CREATE
JBO-25222: ApplicationModuleCreateException |
static java.lang.String |
EXC_ATTR_LOAD_DATUM_EXCEPTION
JBO-27021: AttributeLoadException |
static java.lang.String |
EXC_ATTR_LOAD_EXCEPTION
JBO-27022: AttributeLoadException |
static java.lang.String |
EXC_ATTRIBUTE_INDEX_MISMATCH
JBO-26003: PersistenceException |
static java.lang.String |
EXC_CANNOT_REMOVE_REFERENCED_OBJ
JBO-25008: InvalidOperException |
static java.lang.String |
EXC_CANNOT_SET_USER_QUERY_WITH_VL
JBO-26016: InvalidOperException |
static java.lang.String |
EXC_CHILD_AM_WITH_NO_PARENT
JBO-25301: InvalidOwnerException |
static java.lang.String |
EXC_COMP_OBJ_WITH_NO_PARENT
JBO-25302: InvalidOwnerException |
static java.lang.String |
EXC_CONNECTION_REQUEST_TIMED_OUT
JBO-26069: JboException |
static java.lang.String |
EXC_CUSTOM_CLASS_NOT_ASSIGNABLE
JBO-26023: CustomClassNotFoundException |
static java.lang.String |
EXC_CUSTOM_CLASS_NOT_FOUND
JBO-26022: CustomClassNotFoundException |
static java.lang.String |
EXC_DATA_CREATION
JBO-25021: oracle.jbo.domain.DataCreationException |
static java.lang.String |
EXC_DATA_CREATION_CLASS_NOT_FOUND
JBO-25029: oracle.jbo.domain.DataCreationException |
static java.lang.String |
EXC_DATA_CREATION_FROM_VALUE
JBO-25009: oracle.jbo.domain.DataCreationException |
static java.lang.String |
EXC_DATA_CREATION_WITH_MSG
JBO-25028: oracle.jbo.domain.DataCreationException |
static java.lang.String |
EXC_DATABASE_STATE_EXISTS
JBO-25224: JboException |
static java.lang.String |
EXC_DEAD_ENTITY_ACCESS
JBO-27101: DeadEntityAccessException |
static java.lang.String |
EXC_DEAD_VIEW_ROW_ACCESS
JBO-27102: DeadViewRowAccessException |
static java.lang.String |
EXC_DML_GENERATE_PK_BASED_REF
JBO-26045: DMLException |
static java.lang.String |
EXC_DML_GENERATE_REF_AND_OID
JBO-26042: DMLException |
static java.lang.String |
EXC_DML_GET_EST_ROW_COUNT
JBO-26044: DMLException |
static java.lang.String |
EXC_DML_PK_BASED_REF_NOT_SUPPORTED
JBO-26046: |
static java.lang.String |
EXC_DML_POST_ENTITY
JBO-26041: DMLException |
static java.lang.String |
EXC_DML_REF_AND_OID_NOT_SUPPORTED
JBO-26043: DMLException |
static java.lang.String |
EXC_DOMAIN_OPERATION
JBO-25023: oracle.jbo.domain.GenericDomainException |
static java.lang.String |
EXC_ENTITIES_INV_IN_B4_COMMIT
JBO-28202: JboException |
static java.lang.String |
EXC_ENTITY_ROW_CREATE
JBO-25017: RowCreateException |
static java.lang.String |
EXC_ENTITY_ROW_MISSING
JBO-25031: RowNotFoundException |
static java.lang.String |
EXC_ENTITY_ROW_NOT_FOUND
JBO-25019: RowNotFoundException |
static java.lang.String |
EXC_ENTITY_SELECT
JBO-26080: DMLException |
static java.lang.String |
EXC_EO_NOT_PRIMARY_BASE
JBO-25012: InvalidOperException |
static java.lang.String |
EXC_GENERIC_PERSISTENCE
JBO-26000: JboException |
static java.lang.String |
EXC_IDENT_MISMATCH
JBO-50002: |
static java.lang.String |
EXC_INSERT_WITH_NO_ATTR_SET
JBO-26018: InvalidOperException |
static java.lang.String |
EXC_INVALID_ATTRIBUTE_KIND
JBO-27016: InvalidAttrKindException |
static java.lang.String |
EXC_INVALID_DEFINITION_NAME
JBO-25004: InvalidDefNameException |
static java.lang.String |
EXC_INVALID_ENTITY_ATTR_NAME
JBO-26010: PersistenceException |
static java.lang.String |
EXC_INVALID_ENTITYASSOC_DEFN
JBO-26017: PersistenceException |
static java.lang.String |
EXC_INVALID_FETCH_MODE
JBO-26005: PersistenceException |
static java.lang.String |
EXC_INVALID_FETCH_SIZE
JBO-26006: PersistenceException |
static java.lang.String |
EXC_INVALID_JDBC_POOL_CONNECTION
JBO-26068: JboException |
static java.lang.String |
EXC_INVALID_MAX_FETCH_SIZE
JBO-26007: PersistenceException |
static java.lang.String |
EXC_INVALID_METHOD_CALL
JBO-25221: JboException |
static java.lang.String |
EXC_INVALID_OBJECT_ACCESS
JBO-25036: InvalidObjAccessException |
static java.lang.String |
EXC_INVALID_OBJECT_NAME
JBO-25005: InvalidObjNameException |
static java.lang.String |
EXC_INVALID_OPER_FORWARD_ROWSET
JBO-25011: InvalidOperException |
static java.lang.String |
EXC_INVALID_OPER_SET_ROW_VALIDATION
JBO-25007: InvalidOperException |
static java.lang.String |
EXC_INVALID_PARAMETER
JBO-25006: InvalidParamException |
static java.lang.String |
EXC_INVALID_PASSIVATION_STORE
JBO-25035: JboException |
static java.lang.String |
EXC_INVALID_SER_FILE
JBO-26009: PersistenceException |
static java.lang.String |
EXC_INVALID_VIEWLINK_DEFN
JBO-26012: PersistenceException |
static java.lang.String |
EXC_JDBC_CLOSE_CONNECTION
JBO-26062: DMLException |
static java.lang.String |
EXC_JDBC_CLOSE_STATEMENT
JBO-26064: DMLException |
static java.lang.String |
EXC_JDBC_COLUMN_DEFN
JBO-26070: DMLException |
static java.lang.String |
EXC_JDBC_COMMIT
JBO-26065: DMLException |
static java.lang.String |
EXC_JDBC_GET_SQL_DATUM
JBO-26081: SQLDatumException |
static java.lang.String |
EXC_JDBC_OPEN_CONNECTION
JBO-26061: DMLException |
static java.lang.String |
EXC_JDBC_POOL_SIZE_EXCEEDED
JBO-26067: JboException |
static java.lang.String |
EXC_JDBC_REGISTER_DRIVER
JBO-26060: DMLException |
static java.lang.String |
EXC_JDBC_ROLLBACK
JBO-26066: DMLException |
static java.lang.String |
EXC_KEY_NOT_FOUND
JBO-27017: KeyNotFoundException |
static java.lang.String |
EXC_LOADING_PROPERTIES
JBO-26026: PersistenceException |
static java.lang.String |
EXC_LOCATING_XML_FILE
JBO-26001: NoXMLFileException |
static java.lang.String |
EXC_NAME_CLASH
JBO-25001: NameClashException |
static java.lang.String |
EXC_NO_DEFINITION
JBO-25002: NoDefException |
static java.lang.String |
EXC_NO_ENTITY_OWNER
JBO-25030: InvalidOwnerException |
static java.lang.String |
EXC_NO_MATCHING_EO_BASE
JBO-26020: InvalidOperException |
static java.lang.String |
EXC_NO_OBJECT
JBO-25003: NoObjException |
static java.lang.String |
EXC_NOT_CONNECTED
JBO-25200: NotConnectedException |
static java.lang.String |
EXC_OBSOLETE_METHOD
JBO-25024: JboException |
static java.lang.String |
EXC_PARSING_XML_FILE
JBO-26002: PersistenceException |
static java.lang.String |
EXC_PCOLL_ACTIVATE
JBO-28021: PCollException |
static java.lang.String |
EXC_PCOLL_CHILD_ID_NOT_FOUND
JBO-28037: PCollException |
static java.lang.String |
EXC_PCOLL_COMMIT
JBO-28007: PCollException |
static java.lang.String |
EXC_PCOLL_CONNECT
JBO-28001: PCollException |
static java.lang.String |
EXC_PCOLL_CREATE_CONTROL_TAB
JBO-28002: PCollException |
static java.lang.String |
EXC_PCOLL_CREATE_TAB
JBO-28006: PCollException |
static java.lang.String |
EXC_PCOLL_DELETE_ALL
JBO-28038: PCollException |
static java.lang.String |
EXC_PCOLL_DELETE_ROW
JBO-28032: PCollException |
static java.lang.String |
EXC_PCOLL_GETCURTIME
JBO-28009: PCollException |
static java.lang.String |
EXC_PCOLL_INSERT_ROW
JBO-28030: PCollException |
static java.lang.String |
EXC_PCOLL_INVALID_ID
JBO-28035: PCollException |
static java.lang.String |
EXC_PCOLL_INVALID_ROOT_NODE
JBO-28039: PCollException |
static java.lang.String |
EXC_PCOLL_LOCK_CONTROL_ROW
JBO-28004: PCollException |
static java.lang.String |
EXC_PCOLL_NO_PERSIST_MGR_CLASS
JBO-28000: PCollException |
static java.lang.String |
EXC_PCOLL_OBJ_ALREADY_ACTIVE
JBO-28036: PCollException |
static java.lang.String |
EXC_PCOLL_PASSIVATE
JBO-28020: PCollException |
static java.lang.String |
EXC_PCOLL_RETRIEVE_BY_ID
JBO-28034: PCollException |
static java.lang.String |
EXC_PCOLL_RETRIEVE_ROW
JBO-28033: PCollException |
static java.lang.String |
EXC_PCOLL_UPDATE_CONTROL_ROW
JBO-28005: PCollException |
static java.lang.String |
EXC_PCOLL_UPDATE_ROW
JBO-28031: PCollException |
static java.lang.String |
EXC_POST_THRESHOLD_REACHED
JBO-28201: JboException |
static java.lang.String |
EXC_QUERY_COLLECTION_CLOSED
JBO-25015: InvalidOperException |
static java.lang.String |
EXC_READ_ATTRIBUTE_XML
JBO-25027: AttributeReadXMLException |
static java.lang.String |
EXC_READ_ROW_XML
JBO-25026: RowReadXMLException |
static java.lang.String |
EXC_READ_ROWSET_XML
JBO-25025: ReadXMLException |
static java.lang.String |
EXC_READONLY_ASSOC_ATTR
JBO-27001: ReadOnlyAttrException |
static java.lang.String |
EXC_RECURSIVE_AM_INCLUSION
JBO-25226: ApplicationModuleCreateException |
static java.lang.String |
EXC_RECURSIVE_BASE_DEF
JBO-26004: InvalidOperException |
static java.lang.String |
EXC_REMOVE_WITH_DETAILS
JBO-26019: JboException |
static java.lang.String |
EXC_ROOT_APPMOD_ALREADY_CREATED
JBO-25223: ApplicationModuleCreateException |
static java.lang.String |
EXC_ROW_INCONSISTENT
JBO-25014: RowInconsistentException |
static java.lang.String |
EXC_ROW_OF_HANDLE_NOT_FOUND
JBO-25034: RowNotFoundException |
static java.lang.String |
EXC_SQL_CREATE_STATEMENT
JBO-27124: SQLStmtException |
static java.lang.String |
EXC_SQL_EXECUTE_COMMAND
JBO-27121: SQLStmtException |
static java.lang.String |
EXC_SQL_EXECUTE_QUERY
JBO-27120: SQLStmtException |
static java.lang.String |
EXC_SQL_PREPARE_CALL
JBO-27123: SQLStmtException |
static java.lang.String |
EXC_SQL_PREPARE_STATEMENT
JBO-27122: SQLStmtException |
static java.lang.String |
EXC_SQLTYPE_NOT_SPECIFIED
JBO-26011: PersistenceException |
static java.lang.String |
EXC_STRING_MISMATCH
JBO-50001: |
static java.lang.String |
EXC_SYSTEM_GET_PROPERTIES
JBO-26025: PersistenceException |
static java.lang.String |
EXC_TOO_MANY_LEFT_PARENS
JBO-50004: |
static java.lang.String |
EXC_TOO_MANY_OBJECTS
JBO-25013: TooManyObjectsException |
static java.lang.String |
EXC_TOO_MANY_RIGHT_PARENS
JBO-50003: |
static java.lang.String |
EXC_TYP_UNKNOWN_SQL_TYPE
JBO-25000: UnknownSQLTypeException |
static java.lang.String |
EXC_UNEXPECTED_EXCEPTION
JBO-29000: JboException |
static java.lang.String |
EXC_UNKNOWN_FILE_ENCODING
JBO-25305: |
static java.lang.String |
EXC_UNRESOLVED_REFERENCE
JBO-26008: PersistenceException |
static java.lang.String |
EXC_VAL_APPMOD_VALIDATE_FAILED
JBO-27005: ValidationException |
static java.lang.String |
EXC_VAL_ATTR_MANDATORY
JBO-27014: AttrValException |
static java.lang.String |
EXC_VAL_ATTR_RESOLVEGET_FAILED
JBO-27019: AttrGetValException |
static java.lang.String |
EXC_VAL_ATTR_RESOLVESET_FAILED
JBO-27020: |
static java.lang.String |
EXC_VAL_ATTR_SET_FAILED
JBO-27011: AttrSetValException |
static java.lang.String |
EXC_VAL_ATTR_SET_TYPE_MISMATCH
JBO-27018: AttrSetValException |
static java.lang.String |
EXC_VAL_ATTRIBUTE_NOT_FOUND
JBO-27006: AttrValException |
static java.lang.String |
EXC_VAL_DOMAIN_FAILED
JBO-25010: oracle.jbo.domain.DomainValidationException |
static java.lang.String |
EXC_VAL_ENTITY_ATTR_SET_FAILED
JBO-27004: ReadOnlyAttrException |
static java.lang.String |
EXC_VAL_ENTITY_VALIDATE_FAILED
JBO-27002: AttrSetValException |
static java.lang.String |
EXC_VAL_INVALID_CONTAINED_ENTITIES
JBO-27015: ValidationException |
static java.lang.String |
EXC_VAL_METHOD_ON_ATTR_SET_FAILED
JBO-27013: ValidationException |
static java.lang.String |
EXC_VAL_METHOD_ON_ROW_FAILED
JBO-27012: ValidationException |
static java.lang.String |
EXC_VAL_PRECISION_VALIDATOR
JBO-27010: ValidatonException |
static java.lang.String |
EXC_VAL_VO_VALIDATE_FAILED
JBO-27003: ValidationException |
static java.lang.String |
EXC_VAL_VR_ATTR_SET_FAILED
JBO-27008: ReadOnlyAttrException |
static java.lang.String |
EXC_VAL_VR_BATCH_ATTR_SET_FAILED
JBO-27009: ValidationException |
static java.lang.String |
EXC_VAL_VR_VALIDATE_FAILED
JBO-27007: ValidationException |
static java.lang.String |
EXC_VALIDATION_THRESHOLD_REACHED
JBO-28200: JboException |
static java.lang.String |
EXC_VAR_INVALID_VARIANT_NAME
JBO-55003: VariantException |
static java.lang.String |
EXC_VAR_INVALID_VARIANT_TYPE
JBO-55002: VariantException |
static java.lang.String |
EXC_VAR_UNEXPECTED_TYPE
JBO-55001: VariantException |
static java.lang.String |
EXC_VIEW_LINK_ALREADY_EXISTS
JBO-25022: ViewLinkAlreadyExistsException |
static java.lang.String |
EXC_VIEW_ROW_CREATE
JBO-25018: RowCreateException |
static java.lang.String |
EXC_VIEW_ROW_NOT_FOUND
JBO-25020: RowNotFoundException |
static java.lang.String |
EXC_VIEWOBJECT_READONLY
JBO-25016: ReadOnlyViewObjectException |
static java.lang.String |
EXC_XML_CONTEXT_BIND
JBO-26014: |
static java.lang.String |
EXC_XML_CONTEXT_LOOKUP
JBO-26013: PersistenceException |
static java.lang.String |
EXC_XML_CREATE_INITIAL_CONTEXT
JBO-26024: PersistenceException |
static java.lang.String |
EXC_XML_MISSING_DTD
JBO-26021: PersistenceException |
static java.lang.String |
STR_APP_MODULE
|
static java.lang.String |
STR_ATTRIBUTE
|
static java.lang.String |
STR_DEF_APP_MODULE
|
static java.lang.String |
STR_DEF_ATTRIBUTE
|
static java.lang.String |
STR_DEF_DOMAIN
|
static java.lang.String |
STR_DEF_ENTITY_ASSOC
|
static java.lang.String |
STR_DEF_ENTITY_OBJECT
|
static java.lang.String |
STR_DEF_PACKAGE
|
static java.lang.String |
STR_DEF_VIEW_LINK
|
static java.lang.String |
STR_DEF_VIEW_OBJECT
|
static java.lang.String |
STR_DML_COMMIT
|
static java.lang.String |
STR_DML_DELETE
|
static java.lang.String |
STR_DML_INSERT
|
static java.lang.String |
STR_DML_ROLLBACK
|
static java.lang.String |
STR_DML_SAVEPOINT
|
static java.lang.String |
STR_DML_UPDATE
|
static java.lang.String |
STR_DOMAIN
|
static java.lang.String |
STR_ENTITY_ASSOC
|
static java.lang.String |
STR_ENTITY_OBJECT
|
static java.lang.String |
STR_ENTITY_ROW
|
static java.lang.String |
STR_ENTITY_ROW_SET
|
static java.lang.String |
STR_ENTITY_ROW_SET_ITERATOR
|
static java.lang.String |
STR_PACKAGE
|
static java.lang.String |
STR_VAL_DESC_COMPARE_VALIDATOR
|
static java.lang.String |
STR_VAL_DESC_GENERIC_VALIDATOR
|
static java.lang.String |
STR_VAL_DESC_LIST_VALIDATOR
|
static java.lang.String |
STR_VAL_DESC_MANDATORY_VALIDATOR
|
static java.lang.String |
STR_VAL_DESC_METHOD_VALIDATOR
|
static java.lang.String |
STR_VAL_DESC_PRECISION_VALIDATOR
|
static java.lang.String |
STR_VAL_DESC_RANGE_VALIDATOR
|
static java.lang.String |
STR_VAL_SCALE_DECIMAL_CHAR
|
static java.lang.String |
STR_VALIDATOR_TYPE
|
static java.lang.String |
STR_VIEW_LINK
|
static java.lang.String |
STR_VIEW_OBJECT
|
static java.lang.String |
STR_VIEW_ROW
|
static java.lang.String |
STR_VIEW_ROW_SET
|
static java.lang.String |
STR_VIEW_ROW_SET_ITERATOR
|
Fields inherited from class java.util.ResourceBundle |
parent |
Constructor Summary | |
CSMessageBundle()
|
Method Summary | |
java.lang.Object[][] |
getContents()
Gets the key-value association table. |
Methods inherited from class java.util.ListResourceBundle |
getKeys,
handleGetObject |
Methods inherited from class java.util.ResourceBundle |
getBundle,
getBundle,
getBundle,
getLocale,
getObject,
getString,
getStringArray,
setParent |
Methods inherited from class java.lang.Object |
clone,
equals,
finalize,
getClass,
hashCode,
notify,
notifyAll,
toString,
wait,
wait,
wait |
Field Detail |
public static final java.lang.String STR_DEF_APP_MODULE
public static final java.lang.String STR_DEF_VIEW_OBJECT
public static final java.lang.String STR_DEF_VIEW_LINK
public static final java.lang.String STR_DEF_ENTITY_OBJECT
public static final java.lang.String STR_DEF_ENTITY_ASSOC
public static final java.lang.String STR_DEF_ATTRIBUTE
public static final java.lang.String STR_DEF_DOMAIN
public static final java.lang.String STR_DEF_PACKAGE
public static final java.lang.String STR_APP_MODULE
public static final java.lang.String STR_VIEW_OBJECT
public static final java.lang.String STR_VIEW_ROW_SET
public static final java.lang.String STR_VIEW_ROW_SET_ITERATOR
public static final java.lang.String STR_VIEW_ROW
public static final java.lang.String STR_VIEW_LINK
public static final java.lang.String STR_ENTITY_OBJECT
public static final java.lang.String STR_ENTITY_ROW_SET
public static final java.lang.String STR_ENTITY_ROW_SET_ITERATOR
public static final java.lang.String STR_ENTITY_ROW
public static final java.lang.String STR_ENTITY_ASSOC
public static final java.lang.String STR_ATTRIBUTE
public static final java.lang.String STR_DOMAIN
public static final java.lang.String STR_PACKAGE
public static final java.lang.String STR_VALIDATOR_TYPE
public static final java.lang.String STR_DML_INSERT
public static final java.lang.String STR_DML_UPDATE
public static final java.lang.String STR_DML_DELETE
public static final java.lang.String STR_DML_ROLLBACK
public static final java.lang.String STR_DML_COMMIT
public static final java.lang.String STR_DML_SAVEPOINT
public static final java.lang.String STR_VAL_DESC_RANGE_VALIDATOR
public static final java.lang.String STR_VAL_DESC_COMPARE_VALIDATOR
public static final java.lang.String STR_VAL_DESC_LIST_VALIDATOR
public static final java.lang.String STR_VAL_DESC_METHOD_VALIDATOR
public static final java.lang.String STR_VAL_DESC_GENERIC_VALIDATOR
public static final java.lang.String STR_VAL_DESC_PRECISION_VALIDATOR
public static final java.lang.String STR_VAL_DESC_MANDATORY_VALIDATOR
public static final java.lang.String STR_VAL_SCALE_DECIMAL_CHAR
public static final java.lang.String EXC_TYP_UNKNOWN_SQL_TYPE
Cause:: SQLType name passed to NullValue constructor is invalid.
Action:: Provide a valid SQLType name. See oracle.jbo.server.OracleTypeMapEntries for a list of valid SQLType names. Names are like "VARCHAR", "CHAR", "NUMBER", etc.
public static final java.lang.String EXC_NAME_CLASH
Cause:: A business component of this name already exists in the application module.
Action:: Provide a different name for the business component. If you provide a null value or null string for the name, the framework will create a unique name within the scope of the application module.
public static final java.lang.String EXC_NO_DEFINITION
Cause:: No business component definition found with the given name in the project classpath.
Action:: Provide a correct name for the business component definition.
If the definition is not in the classpath, you must include it there.
Names are of the format myProjectPackage.BusinessPackage.BusinessComponent
.
This error can also occur if there is a case conflict, as when the database expects "DEPTNO"
and receives "Deptno" instead.
public static final java.lang.String EXC_NO_OBJECT
Cause:: No business component object found with the given name in the application module.
Action:: Provide a different name for the business component object or create a new business component with the given name.
public static final java.lang.String EXC_INVALID_DEFINITION_NAME
Cause:: An attempt has been made to associate a definition name with a type for which it is not valid.
Action:: The name should be a valid java-identifier with no spaces or punctuation.
Names are of the format myProjectPackage.BusinessPackage.BusinessComponent
public static final java.lang.String EXC_INVALID_OBJECT_NAME
Cause:: An attempt has been made to associate a business component name with an object for which it is not valid.
Action:: The name should be a valid java-identifier with no spaces or punctuation.
Names are of the format myProjectPackage.BusinessPackage.BusinessComponent
public static final java.lang.String EXC_INVALID_PARAMETER
Cause:: The parameters passed to a business component method are invalid.
Action:: See the Javadoc for the method that throws this exception. Expand the call-stack for the correct parameters. e.g., DBTransactionImpl.executeCommand() throws this exception when command parameter is null or an empty String.
public static final java.lang.String EXC_INVALID_OPER_SET_ROW_VALIDATION
Cause:: Resetting row validation for a default RowIterator of a view object or a RowSet is not permitted.
Action:: Reset the RowValidation flag for the RowSet or view object. This will create another iterator for the RowSet or view object to navigate to another row without validating.
public static final java.lang.String EXC_CANNOT_REMOVE_REFERENCED_OBJ
Cause:: An attempt has been made to remove a view object that is participating in a view link.
Action:: Remove the view link before removing the view object.
public static final java.lang.String EXC_DATA_CREATION_FROM_VALUE
Cause:: A domain object could not be created with the given value. Either a domain constructor that accepts the given value does not exist, or there is no conversion method in the domain object for the given value type, or the domain's constructor threw an unexpected exception.
Action:: Confirm that the value being passed is valid with respect to the domain-type being created. e.g., passing a String value like "One" to the oracle.jbo.domain.Number constructor will throw this exception.
public static final java.lang.String EXC_VAL_DOMAIN_FAILED
Cause:: Validation failed with the given value in a domain constructor. This exception is thrown in the validate() method of a domain type.
Action:: Provide a valid value for the domain type.
public static final java.lang.String EXC_INVALID_OPER_FORWARD_ROWSET
Cause:: An attempt has been made to invoke an invalid navigation method for a forward-only view object or RowSet.
Action:: Either remove the forward-only setting for the view object or RowSet, or do not invoke navigation methods other than next() on the forward-only view object or RowSet.
public static final java.lang.String EXC_EO_NOT_PRIMARY_BASE
Cause:: The client has attempted to locate view rows that has the given entity row as the primary entity row. However, it has been discovered that the entity row's entity definition does not match the entity definition of the view object's primary EO base.
Action:: The entity row used to locate view rows must have be based on the same entity definition.
public static final java.lang.String EXC_TOO_MANY_OBJECTS
Cause:: Attempting to add a new entity to the cache with the primary key the same as an existing entity. This exception is thrown when uniquing a newly fetched/created entity with the cached set of entities.
Action:: The primary key value may not be unique for this entity-type. Fix by adding more attributes to the Key definition for this entity type, so that each row for this entity is uniquely identifiable. Or fix the primary key value so that this entity has a unique key identifier.
public static final java.lang.String EXC_ROW_INCONSISTENT
Cause:: Comparison of the cached entity failed with the values in the database for that entity. This could happen when another user or operation has committed modifications to the same entity-row in the database. This exception can also be thrown if the equals() method on one of the domain-type attributes in the entity fails.
Action:: Choose from the following options:
public static final java.lang.String EXC_QUERY_COLLECTION_CLOSED
Cause: Attempting to execute a query for a view object or RowSet after closing or removing the view object or RowSet.
Action: Verify that the view object or RowSet is not removed or closed.
public static final java.lang.String EXC_VIEWOBJECT_READONLY
Cause:: Attempting to modify data for a view object which is declared to be read only. This includes creating a new row for this view object, removing a Row or modifying attributes of a ViewRow for this view object.
Action: Create a ViewObject with ReadOnly flag set to false to modify the data.
public static final java.lang.String EXC_ENTITY_ROW_CREATE
Cause:: An unexpected exception occurred while creating a new entity instance.
Action: The entity may not have a public default constructor. Fix the cause for InstantiationException or IllegalAccessException that appears in the details of this exception.
public static final java.lang.String EXC_VIEW_ROW_CREATE
Cause: An unexpected exception occurred while creating a new ViewRow instance.
Action: The ViewRow may not have a public default constructor. Fix the cause for InstantiationException or IllegalAccessException that appears in the details of this exception.
public static final java.lang.String EXC_ENTITY_ROW_NOT_FOUND
Cause: Attempting to lock a non-existing row in the database. This could occur when the cache has an entity which was subsequently deleted from the database by another user or operation.
Action: Remove the current entity from the entity-cache by calling remove(). Or re-synchronize the cache with the database, by rolling-back the current transaction or by committing the existing set of changes and then dropping the entity-cache.
public static final java.lang.String EXC_VIEW_ROW_NOT_FOUND
Cause: Attempting to find a referenced entity in the ViewRow failed due to a changed foreign-key value.
Action: Provide a valid foreign key value or remove the current
public static final java.lang.String EXC_DATA_CREATION
Cause: A domain object could not be created with the given value. Either a domain-constructor that accepts the given value does not exist, or there is no conversion method in the domain object for the given value type, or the domain's constructor threw an unexpected exception.
Action: Confirm that the value being passed is valid with respect to the domain-type being created. e.g., passing a String value like "One" to oracle.jbo.domain.Number constructor will throw this exception.
public static final java.lang.String EXC_VIEW_LINK_ALREADY_EXISTS
Cause: Attempting to set the Master RowSet for this RowSet more than once.
Action: Do not invoke setMasterRowSetIterator more than once on a RowSet.
public static final java.lang.String EXC_DOMAIN_OPERATION
Cause: An expected domain exception occurred.
Action: Contact BC4J Technical Support.
public static final java.lang.String EXC_OBSOLETE_METHOD
Cause: Attempting to use an obsolete TypeMap constructor.
Action: Verify that the TypeMaps in use for this version of framework is compatible. See example TypeMaps in oracle.jbo.server.OracleTypeMapEntries
public static final java.lang.String EXC_READ_ROWSET_XML
Cause: An error occurred during reading the XML data for a view object. This exception may contain other ReadXMLExceptions.
Action: Fix the contained Row- or Attribute-level exceptions in the details for this exception.
public static final java.lang.String EXC_READ_ROW_XML
Cause: An error occurred during reading the XML data for a ViewRow. This exception may contain other ReadXMLExceptions for contained RowSets or Attributes.
Action: Fix the RowSet- or Attribute-level exceptions in the details for this exception.
public static final java.lang.String EXC_READ_ATTRIBUTE_XML
Cause: An error occurred during reading the XML data for an attribute of a ViewRow. This exception may contain other JboExceptions thrown from the set method for this attribute.
Action: Fix the JboException in the details for this exception.
public static final java.lang.String EXC_DATA_CREATION_WITH_MSG
Cause: A domain object could not be created with the given value. Either a domain-constructor that accepts the given value does not exist, or there is no conversion method in the domain object for the given value type, or the domain's constructor threw an unexpected exception.
Action: Confirm that the value being passed, is valid with respect to the domain-type being created. e.g., passing a String value like "One" to oracle.jbo.domain.Number constructor will throw this exception.
public static final java.lang.String EXC_DATA_CREATION_CLASS_NOT_FOUND
Cause: The named data class (may be a domain) could not be found.
Action: Make sure that the data class is accessible from the CLASSPATH and is a valid data class.
public static final java.lang.String EXC_NO_ENTITY_OWNER
Cause: Could not find the container entity for this entity, as this entity is a detail in a composition association. This could occur while creating a new entity instance by passing a non-existing master key value, or when updating the foreign-key value in this entity and there is no master entity with that foreign-key value.
Action: Provide a valid foreign-key value to the create() method or setAttribute() method so that an appropriate master row is found for this entity.
public static final java.lang.String EXC_ENTITY_ROW_MISSING
Cause: The client has attempted to access an attribute of a view which is mapped to an entity row, but the corresponding entity row is null. If the VO consists of multiple EO bases and if the secondary EO bases are reference-only, the entity rows may be null if the FK linking the primary EO to secondary EOs is null.
Action: In such a situation, the user is not allowed to access attributes of missing entity rows.
public static final java.lang.String EXC_AM_PASSIVATE
Cause: Failure trying to make the application module state or transaction state passive.
Action: The passivation target store (Database, File or Memory) may have reported an exception. See the details of this exception for errors from the target store.
public static final java.lang.String EXC_AM_ACTIVATE
Cause: Trying to activate the application module state or transaction state failed.
Action: The passivation target store (Database, File or Memory) may have reported an exception. See the details of this exception for errors from the target store. The given ID (in case of activation) may be invalid/not found.
public static final java.lang.String EXC_ROW_OF_HANDLE_NOT_FOUND
Cause: The client has attempted to locate a row with a
row handle, but the row is not found. This error may
be raised if the client tries to take a row out of one query collection and
use its handle to find a row in another query collection. Note that if the
client calls executeQuery
on a RowSet, it may receive a
new query collection. Thus, you may get this error if the client retrieves a row
from a RowSet, takes its row handle, calls executeQuery
, and
then tries to locate the row using the saved handle.
Action: Make sure that your row handle is not stale.
public static final java.lang.String EXC_INVALID_PASSIVATION_STORE
Cause: An application attempted to change an application module's passivation store after it had been initialized.
Action:The passivation store (Database, File or Memory) may only be initialized once. If the customer application logic has not specified a passivation store when the serialization framework is invoked, the passivation store is initialized by the BC4J framework. Check the client application logic for invocations of:
ApplicationModuleImpl.setStoreForPassiveState
which are invoked after the AM passivation store has been initialized.
public static final java.lang.String EXC_INVALID_OBJECT_ACCESS
Cause: An application invoked an object operation that is not supported in the object's current state.
Action:Remove the invalid operation invocation or provide exception handling logic.
public static final java.lang.String EXC_NOT_CONNECTED
Cause: The application module is not connected to the database.
Action: Provide a valid set of connection credentials to connect to a database.
public static final java.lang.String EXC_ALREADY_CONNECTED
Cause: Trying to re-establish a database connection.
Action: Disconnect the current database connection before trying to re-establish the JDBC connection.
public static final java.lang.String EXC_INVALID_METHOD_CALL
Cause: Attempting to call a method that is either not implemented or not supported.
Action: This method is not available on the called object. e.g. setAttribute() in oracle.jbo.Key class is not implemented and will throw this exception.
public static final java.lang.String EXC_APPMODULE_CREATE
Cause: There are a number of reasons the application module could not be created:
Action: Depending on the cause, chose from the following actions:
If your business components are deployed in local mode, they may not be on the classpath.
If this is the cause of the error, the exception will usually be followed by a different exception,
JBO-25002: Application Module not found. If this occurs, make sure
you've done all of the following:
You may have unresolved classes on the server.
Try the following procedure to resolve any unresolved classes on Oracle8i.
You may not have granted Java2 permissions.
If this is the cause of the error, there will be permissions errors in the database trace file.
To correct the problem, see the help topic "Granting Permissions on a Business Components EJB" for
information on granting Java2 permissions.
Note: The location of the database trace file varies from installation to installation, but in a default Windows NT installation, the file will be in the directory ORACLE_HOME\admin\orcl\ udump and will have the form orcl????.trc.
Your Java pool size may be too small
Business Components for Java deployed as EJBs work best with a Java pool size of at least 50MB.
Edit your init.ora file and check the java_pool_size parameter. If it is under 50MB, change it,
restart your database, and try your connection again.
public static final java.lang.String EXC_ROOT_APPMOD_ALREADY_CREATED
Cause: When business components are running inside JServer, only one root application module may be created. This is because JServer (already) provides one transaction context.
Action: It is illegal to attempt to create multiple root transactions when running inside JServer.
public static final java.lang.String EXC_DATABASE_STATE_EXISTS
Cause: Trying to retain the application module state during a transaction disconnect failed.
Action: The disconnect and retain application module state target requires that no database state exist before the transaction connection is closed. Examples of database state include open database cursors in non-forward only view objects, database locks, and uncommitted database changes. The client should clean up this state by fetching or resetting any open view objects and committing any uncommitted changes.
public static final java.lang.String EXC_RECURSIVE_AM_INCLUSION
Cause: This application module definition contains recursive references to child application modules. For example, if application module definition appMod1 contains a child application module of appMod2, and appMod2 contains appMod1,this error will be raised.
Action: Remove recursive application module definition references.
public static final java.lang.String EXC_CHILD_AM_WITH_NO_PARENT
Cause: While traversing the parenthood chain for application modules, a child application module was found with no container (parent) application module.
Action: If this application has added custom business component classes, it may be that the application code is attempting to access a child application module before it is fully initialized. If this is not the case, this error probably represents some internal error in BC4J framework, in which case contact BC4J Technical Support.
public static final java.lang.String EXC_COMP_OBJ_WITH_NO_PARENT
Cause: A business component is found without a container (parent) application module.
Action: If this application has added custom business component classes, it may be that the application code is attempting to access a business component before it is fully initialized. If this is not the case, this error probably represents some internal error in BC4J framework, in which case contact BC4J Technical Support.
public static final java.lang.String EXC_UNKNOWN_FILE_ENCODING
Cause:
Action:
public static final java.lang.String EXC_GENERIC_PERSISTENCE
Cause: Attempting to load metadata objects failed. It may have unexpected data or the XML data may be corrupt.
Action: Verify that the XML metadata for various components is valid.
public static final java.lang.String EXC_LOCATING_XML_FILE
Cause: Could not open the named XML file for read.
Action: 1. Make sure that the file is present. In particular, if the file is to be found in a zip/jar file, make sure that the Zip/JAR file is included in the CLASSPATH.
2. This error is also reported if the name of the XML file does not match the object Name specified in the XML file. If the file system support case insensitive file names (e.g., Windows NT), make sure that the file name matches the object Name in the XML file in case-sensitive fashion.
3. For a .JPX file, this error is reported if the JPX file is missing the JboProject XML tag. Check the JPX file to make sure that the valid tag is in there.
4. One XML file may be extending another XML file (specified by the Extends element in this XML file). This error is reported if the base XML file is not found.
5. When loading the XML file for a package (JboPackage tag), this error is reported if some unexpected error occurs while loading a containee.
In all of the above cases, a more descriptive message may be printed on Diagnostic. If you are not seeing Diagnostic messages, you can run your application with Diagnostic turned on, as in "java -Djbo.debugoutput=console ...", to see Diagnostic messages.
public static final java.lang.String EXC_PARSING_XML_FILE
Cause: Some XML parsing exception (oracle.xml.parser.v2.XMLParseException) was thrown.
Action: The XMLParseException information is output to Diagnostic. If you are not seeing diagnostic messages, you can run your application with diagnostic turned on, as in "java -Djbo.debugoutput=console ...", to see diagnostic messages.
public static final java.lang.String EXC_ATTRIBUTE_INDEX_MISMATCH
Cause: An error occurred while loading entity object definitions. An attribute index in the Java class for this entity has a mismatch with the index in the definition, or an attribute index is missing in the Java class.
Action: Ensure that the indices of attributes in the definition for this entity match the indices defined in the Java class for this entity.
public static final java.lang.String EXC_RECURSIVE_BASE_DEF
Cause: An attempt was made to set the base definition of another definition object, e.g., setting B's base definition to A (i.e., B Extends A). However, A already extends B. Setting a recursive (circular) subclassing relationship among definition objects is illegal.
Action: Review your subclassing hierarchy of your definition objects and correct errors.
public static final java.lang.String EXC_INVALID_FETCH_MODE
Cause: The fetch mode specified in the view definition XML file is not valid.
Action: Check the content of the XML file for the view definition. Look for an XML element named "FetchMode". Make sure that the value for that element is valid. Valid values are: "FETCH_AS_NEEDED", "FETCH_ALL", and "FETCH_DEFAULT".
public static final java.lang.String EXC_INVALID_FETCH_SIZE
Cause: The fetch size specified in the view definition XML file is not valid.
Action: Check the content of the XML file for the view definition. Look for an XML element named "FetchSize". Make sure that the value for the element is a positive integer.
public static final java.lang.String EXC_INVALID_MAX_FETCH_SIZE
Cause: The maximum fetch size specified in the view definition XML file is not valid.
Action: Check the content of the XML file for the view definition. Look for an XML element named "MaxFetchSize". Make sure that the value for the element is a non-negative integer, or "MAX_FETCH_UNLIMITED", or "MAX_FETCH_DEFAULT". A MaxFetchSize of 0 is the same as MAX_FETCH_UNLIMITED.
public static final java.lang.String EXC_UNRESOLVED_REFERENCE
Cause: A problem is found in resolving a view link definition or an association. In case of a view link, this error may be caused by the fact that the source or destination view object cannot found. Or, if the view link ends have attribute names, this error may indicate that the named attributes cannot be found. Similarly, for an association, this error indicates that either source or destination entity object or attributes involved in the association cannot be found.
Action: Make sure the XML definition for the view link/association has correct view object/entity object/attribute names.
public static final java.lang.String EXC_INVALID_SER_FILE
Cause: This error occurs if the application uses meta object serialization files (.ser files) instead of XML files. It indicates that after the .ser file is deserialized, the top level object returned from deserialization is not an instance of oracle.jbo.server.xml.JboElementImpl.
Action: This probably means that the .ser file is corrupt.
public static final java.lang.String EXC_INVALID_ENTITY_ATTR_NAME
Cause: Entity attribute name in the view definition XML file is invalid or is not found.
Action: Make sure that the entity name is valid. Also, check to make sure that the named attribute does exist in the entity object. The entity object is identified by the EntityUsage element.
public static final java.lang.String EXC_SQLTYPE_NOT_SPECIFIED
Cause: Attribute definition found in XML file is invalid. It is missing SQLType value.
Action: Correct the error in the XML file.
public static final java.lang.String EXC_INVALID_VIEWLINK_DEFN
Cause: The view link definition in the XML file is missing either the source or destination view link end. For a view link XML file, two elements named ViewLinkDefEnd should be found.
Action: Correct the error in the XML file.
public static final java.lang.String EXC_XML_CONTEXT_LOOKUP
Cause: Meta object name passed for lookup is invalid.
Action: Normally, the meta object name is a dot-separated name of the meta object. For an entity object named Emp in package1.example, the correct name would be "package1.example.Emp". To correct, locate where the invalid name is coming from (could be meta object names mentioned in an XML file, or the name of the project, etc.) and change the name to a valid one.
public static final java.lang.String EXC_XML_CONTEXT_BIND
Cause:
Action:
public static final java.lang.String EXC_CANNOT_SET_USER_QUERY_WITH_VL
Cause: You cannot set customer query (calling setQuery()) on a view object if it is the detail view object in a master detail view link.
Action: Do not call setQuery() if the view object is a detail.
public static final java.lang.String EXC_INVALID_ENTITYASSOC_DEFN
Cause: An entity association definition in an XML file is invalid. In particular, this error means that either of the two association ends ("AssociationEnd" elements in the XML file) are missing "Attributes", which lists source or destination attributes.
Action: Correct the error(s) in the XML file.
public static final java.lang.String EXC_INSERT_WITH_NO_ATTR_SET
Cause: An attempt was made to post a row with no attribute set. Some databases (in particular Oracle) do not allow an INSERT statement with no VALUE specified.
Action: Set some attributes on the row before attempting to insert it into the database.
public static final java.lang.String EXC_REMOVE_WITH_DETAILS
Cause: Attempting to remove a master which has detail entities. In the case of a composition, a master cannot be removed if it has details.
Action: Remove all the details of this master by accessing the details via an association and removing all of them.
public static final java.lang.String EXC_NO_MATCHING_EO_BASE
Cause: The application code tried to take a row from one row set (or view object) and insert it into another row set (view object). In response, the framework will make a "copy" of the row in the new row set. This new row will share references to the underlying entity objects. However, if the source and destination row sets do not share any entity object bases at all, this operation will fail as it does not find any entity rows to share.
Action: When attempting to take a row from one row set and insert into another, make sure that they share at least one entity object base.
public static final java.lang.String EXC_XML_MISSING_DTD
Cause: A NullPointerException was thrown while parsing an XML file. A possible cause for this is that the DTD file is missing (oracle.jbo.dtd.jbo*.dtd).
Action: Make sure the appropriate DTD file is present.
public static final java.lang.String EXC_CUSTOM_CLASS_NOT_FOUND
Cause: Custom class could not be found and loaded. The custom class may be for a component (e.g., view object), a definition (e.g., view definition), or a row (e.g., view row, entity row).
Action: Make sure that the named class is reachable from the CLASSPATH. The detail exception (if present) will give you more specific reasons why the attempt to locate and load the custom class failed.
public static final java.lang.String EXC_CUSTOM_CLASS_NOT_ASSIGNABLE
Cause: Custom class was found and loaded, but it is invalid in that it is not assignable to a framework (super) class.
Action: Make sure that the custom class subclasses the appropriate framework (super) class.
public static final java.lang.String EXC_XML_CREATE_INITIAL_CONTEXT
Cause: An error occurred while creating initial context. This error usually carries a detail exception which will give further information on the cause of the error.
Action: If BC4J is running inside JServer, make sure that the database user (schema) has the setContextClassLoader permission. To grant this, the database system administrator can invoke the following PL/SQL procedure: EXEC DBMS_JAVA.GRANT_PERMISSION('&&1', 'SYS:java.lang.RuntimePermission', 'setContextClassLoader', null);
public static final java.lang.String EXC_SYSTEM_GET_PROPERTIES
Cause: An error occurred while trying to get System properties. Specifically, System.getProperties() call failed.
Action: If BC4J is running inside JServer, make sure that the database user (schema) has the proper property permission. To grant this, database system can invoke the following PL/SQL procedure: EXEC DBMS_JAVA.GRANT_PERMISSION('&&1', 'SYS:java.util.PropertyPermission', '*', 'read');
public static final java.lang.String EXC_LOADING_PROPERTIES
Cause: An error occurred while trying to get load properties.
Action: Check to see if the named properties file contains valid Java properties.
public static final java.lang.String EXC_ALREADY_LOCKED
Cause: This row has already been locked by another user or transaction.
Action: Try locking the row again and the operation should succeed after the other user or transaction has released the lock.
public static final java.lang.String EXC_DML_POST_ENTITY
Cause: Some database error occurred while posting (writing) an entity to the database. This error normally carries a detail exception from the database which will give further information about the database failure.
Action: Look at the details of the exception and address the database problem.
public static final java.lang.String EXC_DML_GENERATE_REF_AND_OID
Cause: A database failure occurred while trying to generate an object ID (OID) and
object reference (REF). When a new row is created on an entity which
maps to an Oracle object table, an OID and REF for the
new row are generated. This executes a SQL statement like
select a.oid, make_ref(
Somehow, this statement is failing.
Action: Check the following:
1. Are you using the right version of Oracle database?
2. Is the table in question an object table?
This error normally carries a detail exception from the database, which will give further information about the database failure. Take a look at the detail exception and address the database problem.
public static final java.lang.String EXC_DML_REF_AND_OID_NOT_SUPPORTED
Cause: An attempt was made to generate an object ID (OID) and/or a reference (REF) on a database system that does not support Oracle objects.
Action: Do not try to create OID or REF on a database system that does not support Oracle objects.
public static final java.lang.String EXC_DML_GET_EST_ROW_COUNT
Cause: The application tried to get an estimated row count (getEstimatedRowCount()) on a row set. While building the appropriate query statement, executing it, and retrieving the estimated count, an error occurred. This error is accompanied by the SQL statement that caused the error. Also, it normally carries a detail exception from database, which will give further information about the database failure.
Action: Take a look at the SQL statement and the detail exception and address the database problem.
public static final java.lang.String EXC_DML_GENERATE_PK_BASED_REF
Cause: A database occurred while trying to generate an object ID (OID) from the primary key. This operation is valid only if the table in question is an object table and if the table specifies that the reference (REF) is PK based.
Action: Check the following:
1. Are you using the right version of Oracle database?
2. Is the table in question an object table?
3. Does this object table use a PK-based REF?
This error normally carries a detail exception from database which will give further information about the database failure. Take a look at the detail exception and address the database problem.
public static final java.lang.String EXC_DML_PK_BASED_REF_NOT_SUPPORTED
Cause:
Action:
public static final java.lang.String EXC_JDBC_REGISTER_DRIVER
Cause: A SQLException occurred while trying to register a JDBC driver.
Action: Fix the underlying SQLException.
public static final java.lang.String EXC_JDBC_OPEN_CONNECTION
Cause: A SQLException occurred while trying to open a JDBC connection.
Action: Fix the underlying SQLException.
public static final java.lang.String EXC_JDBC_CLOSE_CONNECTION
Cause: A SQLException occurred while trying to close a JDBC connection.
Action: Fix the underlying SQLException.
public static final java.lang.String EXC_JDBC_CLOSE_STATEMENT
Cause: A SQLException occurred while trying to close a JDBC connection.
Action: Fix the underlying SQLException.
public static final java.lang.String EXC_JDBC_COMMIT
Cause: A SQLException occurred during the commit phase of this transaction.
Action: Fix the underlying SQLException.
public static final java.lang.String EXC_JDBC_ROLLBACK
Cause: A SQLException occurred during the rollback phase of this transaction.
Action: Fix the underlying SQLException.
public static final java.lang.String EXC_JDBC_POOL_SIZE_EXCEEDED
Cause: An exception occurred while adding a JDBC connection to a pool that was already full.
Action: Modify the class that is using the pool to check the pool size before adding a new connection to the pool.
public static final java.lang.String EXC_INVALID_JDBC_POOL_CONNECTION
Cause: The user attempted to return a connection to a pool that was not responsible for managing that connection.
Action: Modify the class that is using the pool to ensure that the connection belongs to the pool before returning the connection to the pool.
public static final java.lang.String EXC_CONNECTION_REQUEST_TIMED_OUT
Cause: A client request was timed out while waiting for a connection to be returned to the pool.
Action: Increase the maximum pool size in order to accommodate 2x the maximum expected active request size.
public static final java.lang.String EXC_JDBC_COLUMN_DEFN
Cause: A SQLException occurred while setting up metadata JDBC statement.
Action: Fix the underlying SQLException. There might be a datatype mismatch between the attributes of the view object and columns in the SQL for it.
public static final java.lang.String EXC_ENTITY_SELECT
Cause: An unexpected exception occurred while executing the SQL to fetch data for an entity instance or lock it.
Action: Fix the cause for the SQLException in the details of this exception.
public static final java.lang.String EXC_JDBC_GET_SQL_DATUM
Cause: A SQLException occurred when converting data from jdbc to oracle.jbo.domain.Struct attributes.
Action: Fix the conversion errors as suggested in SQLException.
public static final java.lang.String EXC_AFTER_COMMIT
Cause: An exception occurred in the afterCommit notification phase of the transaction.
Action: Verify the exception in the details of this exception. Fix the failing afterCommit() overridden methods in the entities or transient TransactionListener objects registered with the transaction to listen into the commit/rollback cycle.
public static final java.lang.String EXC_AFTER_POST
Cause: An exception occurred in the afterPost phase of the transaction.
Action: Verify the exception in the details of this exception. Fix the failing afterPost() overridden methods in the entities or transient TransactionPostListener objects registered with the transaction to listen into the post cycle.
public static final java.lang.String EXC_AFTER_ROLLBACK
Cause: An exception occurred in afterRollback notification phase of the transaction.
Action: Verify the exception in the details of this exception. Fix the failing afterCommit() overridden methods in the entities or transient TransactionListener objects registered with the transaction to listen into the commit/rollback cycle.
public static final java.lang.String EXC_READONLY_ASSOC_ATTR
Cause: This association attribute is marked readonly.
Action: Cannot modify the value of the association attribute as it is marked readonly.
public static final java.lang.String EXC_VAL_ENTITY_VALIDATE_FAILED
Cause: A custom validation rule failed to validate an attribute value.
Action: Fix the attribute value so that it passes the custom validation rule.
public static final java.lang.String EXC_VAL_VO_VALIDATE_FAILED
Cause: Modified or new entities in this view object failed to validate.
Action: Fix the failing entity values and revalidate the view object.
public static final java.lang.String EXC_VAL_ENTITY_ATTR_SET_FAILED
Cause: Attempting to modify a read-only entity-attribute.
Action: DO not modify a readonly attribute value.
public static final java.lang.String EXC_VAL_APPMOD_VALIDATE_FAILED
Cause: Modified or new entities within this application module or nested application module failed to validate.
Action: Fix the failing entities and then re-validate this application module.
public static final java.lang.String EXC_VAL_ATTRIBUTE_NOT_FOUND
Cause: An attribute cannot be found by the given name during validation.
Action: Entity meta-data could be corrupt as there is an attribute which is to be validated but no definition could be found for that attribute in the meta-data.
public static final java.lang.String EXC_VAL_VR_VALIDATE_FAILED
Cause: Attempting to validate a View Row failed.
Action: Fix the failing entities or attributes as found in the details of this exception.
public static final java.lang.String EXC_VAL_VR_ATTR_SET_FAILED
Cause: Attempting to modify a ViewRow attribute that is readonly
Action: Either change the Updateable flag for the View Attribute or do not attempt to update readonly attributes.
public static final java.lang.String EXC_VAL_VR_BATCH_ATTR_SET_FAILED
Cause: Attempting to validate entities and attributes failed during validation of buffered attributes in Deferred Validation mode. (Not available in 3.x)
Action: Fix the failure cases.
public static final java.lang.String EXC_VAL_PRECISION_VALIDATOR
Cause: For strings, the length of the string value provided for an attribute is more than the max-length this attribute expects. For Numeric values, the length of the value (in string form) is more than what the attribute expects.
Action: Fix the attribute value with respect to the precision and scale information for the failing attribute.
public static final java.lang.String EXC_VAL_ATTR_SET_FAILED
Cause: A validation rule for an attribute failed either due to an unexpected exception in validating the attribute with that rule, or due to failure in evaluating the NOT operation on the rule.
Action: Fix the attribute value so that it validates against the failing rule.
public static final java.lang.String EXC_VAL_METHOD_ON_ROW_FAILED
Cause: The custom method validator attached to an entity returned false, indicating a failure in the validation for that entity.
Action: Fix the cause for failure in the custom validation method for this attribute.
public static final java.lang.String EXC_VAL_METHOD_ON_ATTR_SET_FAILED
Cause: The custom method validator attached to an attribute returned 'false' indicating a failure in validation for that attribute in the custom method.
Action: Fix the cause for failure in the custom validator method for this attribute.
public static final java.lang.String EXC_VAL_ATTR_MANDATORY
Cause: The attribute value cannot be null as it has been marked mandatory.
Action: Provide non-null values for mandatory attributes.
public static final java.lang.String EXC_VAL_INVALID_CONTAINED_ENTITIES
Cause: In validating a master, some child entities were found that could not be validated. This occurs only in the case when there is a composition association between the master and detail entities.
Action: Fix the attribute values in the child entities so that they are valid when the child entities are validated by the master
public static final java.lang.String EXC_INVALID_ATTRIBUTE_KIND
Cause: An unexpected attribute kind found in the definition for a view object.
Action: Fix the attribute kind information in the xml-metadata definition for attributes in this view object.
public static final java.lang.String EXC_KEY_NOT_FOUND
Cause: While loading the meta-data definition for this entity, there was no attribute marked as the primary key.
Action: Set at least one attribute as the primary key for this entity type, so that entities of this type can be uniquely identified.
public static final java.lang.String EXC_VAL_ATTR_SET_TYPE_MISMATCH
Cause: The type of attribute value provided as an argument to the set() method for this attribute is not an instance of the Java type that this attribute expects.
Action: Convert the argument to a proper Java type, such that it is an instance of the Java type that this attribute expects.
public static final java.lang.String EXC_VAL_ATTR_RESOLVEGET_FAILED
Cause: An unexpected exception occurred in setAttribute method. Getter methods should throw a subclass of JboException so that custom exception messages are thrown/shown to the caller. This exception could also be thrown if the getter is not a public Java method.
Action: Do not throw any exception other than sub-classes of JboException from any business logic code in the getter method for an attribute. Also verify that the getter method is a public Java method.
public static final java.lang.String EXC_VAL_ATTR_RESOLVESET_FAILED
Cause: An unexpected exception occurred in setAttribute method. Setter methods should throw a subclass of JboException so that custom exception messages are thrown/shown to the caller. This exception could also be thrown if the setter is not a public Java method.
Action: Do not throw any exception other than sub-classes of JboException from any business logic code in the setter method for an attribute. Also verify that the setter method is a public Java method.
public static final java.lang.String EXC_ATTR_LOAD_DATUM_EXCEPTION
Cause: An unexpected exception occurred during fetching values from a JDBC-resultset into an attribute for a row object. There could be conversion errors between the return type from JDBC for the attribute and it's Java type.
Action: Verify that the JDBC-SQL type and Java type for the attribute are compatible. Fix any conversion errors or domain exceptions that are in the details of this exception.
public static final java.lang.String EXC_ATTR_LOAD_EXCEPTION
Cause: An unexpected exception occurred during fetching values from a JDBC-resultset into an attribute for a row object. There could be conversion errors between the return type from JDBC for the attribute and it's Java type.
Action: Verify that the JDBC-SQL type and Java type for the attribute are compatible. Fix any conversion errors or domain exceptions that are in the details of this exception.
public static final java.lang.String EXC_DEAD_ENTITY_ACCESS
Cause: Trying to refer to an invalid/obsolete entity. This could occur if some business logic has held on to an entity reference which was removed and the transaction has been posted or committed. It could also occur if a reference entity has been removed from the cache and any ViewRow is attempting to access it.
Action: Use findByPrimaryKey to find a valid entity of the desired key instead of holding on to a reference to an entity instance.
public static final java.lang.String EXC_DEAD_VIEW_ROW_ACCESS
Cause: Trying to access a ViewRow which is part of an obsolete/invalid collection. This could happen if a reference to the ViewRow is held by some business logic while the containing view object was removed.
Action: Find the referenced ViewRow either by re-querying or using findByKey methods to get a valid reference to the ViewRow.
public static final java.lang.String EXC_SQL_EXECUTE_QUERY
Cause: Failed to execute a query. This could occur when trying to execute a query for a SQLValue domain class or a Sequence domain.
Action: Fix the cause for the SQLException thrown by JDBC found in the details of this exception.
public static final java.lang.String EXC_SQL_EXECUTE_COMMAND
Cause: Failed to execute a SQL statement.
Action: Fix the cause for the SQLException thrown by JDBC found in the details of this exception.
public static final java.lang.String EXC_SQL_PREPARE_STATEMENT
Cause: Failed to prepare a JDBC PreparedStatement.
Action: Fix the cause for the SQLException thrown by JDBC found in the details of this exception.
public static final java.lang.String EXC_SQL_PREPARE_CALL
Cause: Failed to prepare a JDBC CallableStatement.
Action: Fix the cause for the SQLException thrown by JDBC found in the details of this exception.
public static final java.lang.String EXC_SQL_CREATE_STATEMENT
Cause: Failed to create a JDBC Statement object with the given set of parameters.
Action: Fix the cause for the SQLException thrown by JDBC found in the details of this exception.
public static final java.lang.String EXC_PCOLL_NO_PERSIST_MGR_CLASS
Cause: The client specified a custom persistent collection
through the jbo.pcoll.mgr
property. However, the class
specified could not be located or loaded.
Action: Make sure that the name specified for jbo.pcoll.mgr
is for a valid class name. The class name should be fully qualified
with the package name. A special keyword None
represents
no persistent collection manager, i.e., no spilling to disk will occur.
public static final java.lang.String EXC_PCOLL_CONNECT
Cause: An error occurred while attempting to get a JDBC connection for persistent collection management.
Action: Make sure that the database connection URL is correct. The detail to this exception will give further information on the problem.
public static final java.lang.String EXC_PCOLL_CREATE_CONTROL_TAB
Cause: An error occurred while creating "persistent collection control table." Normally, the control table's name is PCOLL_CONTROL.
Action: Check to make sure that the connection has appropriate authority to create a table. The detail to this exception will give further information on the problem.
public static final java.lang.String EXC_PCOLL_LOCK_CONTROL_ROW
Cause: An error occurred while trying to lock the persistent collection control row. This error is thrown in two situations:
null
.
Action: In the first case, see the details of this exception for further information on the database problem. In the second case, make sure that no other user locks the control rows outside the Business Components framework.
public static final java.lang.String EXC_PCOLL_UPDATE_CONTROL_ROW
Cause: An unexpected error occurred while attempting to update the persistent collection control row.
Action: Look at the details of this exception for further information on the problem and how to address it.
public static final java.lang.String EXC_PCOLL_CREATE_TAB
Cause: An error occurred while attempting to create a database table to store persistent collection material.
Action: Look at the details of this exception for further information on the problem and how to address it.
public static final java.lang.String EXC_PCOLL_COMMIT
Cause: An unexpected error occurred while attempting to commit persistent collection changes.
Action: Look at the details of this exception for further information on the problem and how to address it.
public static final java.lang.String EXC_PCOLL_GETCURTIME
Cause: An unexpected error occurred while attempting to get the system date from the database. For the Oracle persistent manager, the SQL statement used for this would be "select sysdate from dual".
Action: Look at the details of this exception for further information on the problem and how to address it.
public static final java.lang.String EXC_PCOLL_PASSIVATE
Cause: An unexpected error occurred while passivating objects into the persistent store. An exception may have been thrown during serialization.
Action: Look at the details of this exception for further information on the problem and how to address it.
public static final java.lang.String EXC_PCOLL_ACTIVATE
Cause: An unexpected error occurred while activating objects from the persistent store. An exception may have been thrown during deserialization.
Action: Look at the details of this exception for further information on the problem and how to address it.
public static final java.lang.String EXC_PCOLL_INSERT_ROW
Cause: An unexpected error occurred while inserting a passivation row into the persistent store table.
Action: Look at the details of this exception for further information on the problem and how to address it.
public static final java.lang.String EXC_PCOLL_UPDATE_ROW
Cause: An unexpected error occurred while updating a passivation row in the persistent store table.
Action: Look at the details of this exception for further information on the problem and how to address it.
public static final java.lang.String EXC_PCOLL_DELETE_ROW
Cause: An unexpected error occurred while deleting a passivation row from the persistent store table.
Action: Look at the details of this exception for further information on the problem and how to address it.
public static final java.lang.String EXC_PCOLL_RETRIEVE_ROW
Cause: An unexpected error occurred while retrieving a passivation row from the persistent store table.
Action: Look at the details of this exception for further information on the problem and how to address it.
public static final java.lang.String EXC_PCOLL_RETRIEVE_BY_ID
Cause: The client attempted to retrieve a row in a persistent collection by an id, but the by-id access is not enabled on the persistent collection.
Action: Enable by-id access by calling
PCollection.enableIdAccess
.
public static final java.lang.String EXC_PCOLL_INVALID_ID
Cause: The client attempted to retrieve a row by an id, but the id value is invalid. The id must be greater than 0.
Action: Give a valid id.
public static final java.lang.String EXC_PCOLL_OBJ_ALREADY_ACTIVE
Cause: While attempting to activate an object of a given id, an internal integrity problem was found. In particular, a node which was thought to be passivated was found to be active.
Action: Contact BC4J Technical Support with how you ran into the problem.
public static final java.lang.String EXC_PCOLL_CHILD_ID_NOT_FOUND
Cause: While attempting to activate an object of a given id, an internal integrity problem was found. In particular, a child node/element expected to be found in a node is missing.
Action: Contact BC4J Technical Support with how you ran into the problem.
public static final java.lang.String EXC_PCOLL_DELETE_ALL
Cause: An unexpected error occurred while deleting all passivation rows from the persistent store table.
Action: Look at the details of this exception for further information on the problem and how to address it.
public static final java.lang.String EXC_PCOLL_INVALID_ROOT_NODE
Cause: While attempting to activate an object of a given id,
an internal integrity problem was found. In particular, the root
node of the persistent collection is no good. It is either (1) null
,
(2) has younger or older sibling, or (3) has a parent node.
None of these should apply to the root node.
Action: Contact BC4J Technical Support with how you ran into the problem.
public static final java.lang.String EXC_VALIDATION_THRESHOLD_REACHED
Cause: Invalid entities still found in the validation list of the transaction after attempting to validate all invalid entities for the VALIDATION_THRESHOLD 10 times (by default).
Action: Fix any logic that invalidates entity instances in the validation cycle (perhaps in overridden validateEntity() methods) such that all entities are valid before the VALIDATION_THRESHOLD limit is reached.
public static final java.lang.String EXC_POST_THRESHOLD_REACHED
Cause: There are invalid entities or entities in the post list of the transaction after trying to post all changes for the POST_THRESHOLD 10 times (by default).
Action: Fix any logic that places entities in the transaction's list of entities to be validated or posted in the post cycle, such that all entities get posted before the POST_THRESHOLD is reached.
public static final java.lang.String EXC_ENTITIES_INV_IN_B4_COMMIT
Cause: Invalid entity instances found in the transaction in the beforeCommit phase.
Action: Fix any business logic that invalidates entity instances in postChanges() such that there are no more invalid entities after all changes are posted during the commit cycle.
public static final java.lang.String EXC_UNEXPECTED_EXCEPTION
Cause: If an unexpected exception occurs during a framework operation, this exception is thrown, with the unexpected exception included in the details of this exception.
Action: Fix the cause for the exception in the details for this JboException.
public static final java.lang.String EXC_STRING_MISMATCH
Cause:
Action:
public static final java.lang.String EXC_IDENT_MISMATCH
Cause:
Action:
public static final java.lang.String EXC_TOO_MANY_RIGHT_PARENS
Cause:
Action:
public static final java.lang.String EXC_TOO_MANY_LEFT_PARENS
Cause:
Action:
public static final java.lang.String EXC_VAR_UNEXPECTED_TYPE
Cause: Unexpected type was provided to Variant utility.
Action: Provide an expected type as reported in the exception.
public static final java.lang.String EXC_VAR_INVALID_VARIANT_TYPE
Cause: The data-type passed to the Variant utility from a Validation rule is invalid. This could be due to a corrupt XML-metadata definition in the component's XML file.
Action: Fix the component XML for the offending validation rule.
public static final java.lang.String EXC_VAR_INVALID_VARIANT_NAME
Cause: The name of the variant type passed to the Variant utility from a Validation rule is invalid. This could be due to a corrupt XML meta data definition in the component's XML file.
Action: Fix the component XML for the offending validation rule.
Constructor Detail |
public CSMessageBundle()
Method Detail |
public java.lang.Object[][] getContents()
|
Business Components | |||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |