*
|
BEA-2002072
|
Dynamic: Result path "{2}" in result type "{1}" of mapping "{0}" attempts to map a field that does not have exactly 1 column.
|
|
BEA-2002073
|
Dynamic: The type for "{0}" is mapped to custom strategy "{1}", but this strategy cannot be instantiated.
|
|
BEA-2002074
|
Dynamic: No targets were given. Running on all classes listed in your configuration, or all persistent classes in the classpath if no classes are configured.
|
|
BEA-2002075
|
Dynamic: No null-indicator column name was given for "{0}".
|
|
BEA-2002076
|
Dynamic: Table "{0}" could not be reverse mapped. This means that the table does not have a primary key (primary keys are required to establish unique identifiers for all persistent objects) and does not match a known pattern for a table used for cross-reference or value collections.
|
|
BEA-2002077
|
Dynamic: "{0}" declares a column in table "{1}", but all columns must be in table "{2}".
|
|
BEA-2002078
|
Dynamic: No mapping information found for type "{0}".
|
|
BEA-2002079
|
Dynamic: "{0}" does not supply a name for at least one declared join column. Since this join can involve multiple columns or uses constant joins, each column must give either its name or a non-constant target.
|
|
BEA-2002080
|
Dynamic: Cannot use "{0}" as the mapped-by value for a field in "{1}". The target-field "{2}" for column "{3}" is mapped to multiple columns.
|
|
BEA-2002081
|
Dynamic: Writing generated class source code.
|
|
BEA-2002082
|
Dynamic: "{0}" is marked as having a unique constraint, but OpenJPA does not support a constraint on this mapping in this context.
|
|
BEA-2002083
|
Dynamic: "{0}" defines a target of "{1}" for column "{2}", but that target does not exist in table "{3}".
|
|
BEA-2002084
|
Dynamic: "{0}" is marked as having a foreign key, but OpenJPA does not support a foreign key on this mapping in this context.
|
|
BEA-2002085
|
Dynamic: When mapping "{0}" to table "{1}", found a column mapped to illegal table "{2}".
|
|
BEA-2002086
|
Dynamic: Cannot use "{0}" as the mapped-by value for a field in "{1}". There is no target-field "{2}" for column "{3}" in this subclass.
|
|
BEA-2002087
|
Dynamic: "{0}" declares a join index, but has no join columns.
|
|
BEA-2002088
|
Dynamic: Could not instantiate custom version strategy "{1}" for type "{0}". Make sure this is a valid VersionStrategy implementation.
|
|
BEA-2002089
|
Dynamic: Cannot order "{0}" on "{1}", because that field is not in the default fetch group. You can only order on fields that will be selected when the related object is loaded.
|
|
BEA-2002090
|
Dynamic: "{0}" is being mapped with a handler that may not be able to store values over {1} bytes/chars long.
|
|
BEA-2002091
|
Dynamic: "{0}" marks its join columns as having a deferred foreign key, but the database dictionary "{1}" reports that it does not support deferred constraints. Creating an undeferred constraint.
|
|
BEA-2002092
|
Dynamic: "{0}" marks its columns as having a unique index, but the existing index on those columns is not unique.
|
|
BEA-2002093
|
Dynamic: Type "{0}" does not supply a name for at least one declared superclass join column.
|
|
BEA-2002094
|
Dynamic: "{0}" uses an unsupported foreign key delete or update action on its columns. Reverting to a logical foreign key.
|
|
BEA-2002095
|
Dynamic: "{0}" declares an inverse self-join on table "{1}", but this mapping does not allow inverse joins. If you did not intend to make this an inverse join, take the table name out of the column names for this mapping.
|
|
BEA-2002096
|
Dynamic: When mapping "{0}", found join with a target-field in class "{1}". This class does not match the expected source or target mappings for the join ("{2}", "{3}").
|
|
BEA-2002097
|
Dynamic: Attempt to map "{0}" failed: the owning entity is not mapped.
|
|
BEA-2002098
|
Dynamic: "{0}" declares invalid constant value target "{1}" for join column with name "{2}".
|
|
BEA-2002099
|
Dynamic: "{0}" defines target field "{1}" for join column "{2}", but that field is either unmapped or has multiple columns.
|
|
BEA-2002100
|
Dynamic: OpenJPA cannot map field "{0}" efficiently. It is of an unsupported type. The field value will be serialized to a BLOB by default.
|
|
BEA-2002101
|
Dynamic: "{0}" uses an unsupported foreign key delete or update action on its join columns. Reverting to a logical foreign key.
|
|
BEA-2002102
|
Dynamic: Could not instantiate library to import or export mapping information.
|
|
BEA-2002103
|
Dynamic: "{0}" marks its columns as having a unique constraint, but your database does not support unique constraints. Include "SupportsUniqueConstraints=true" in the org.apache.openjpa.jdbc.DBDictionary configuration property to override this default.
|
|
BEA-2002104
|
Dynamic: Writing generated metadata.
|
|
BEA-2002105
|
Dynamic: "{0}" has columns with targets, but OpenJPA does not support any joins on this mapping in this context.
|
|
BEA-2002106
|
Dynamic: "{0}" uses columns from multiple different tables: "{1}", "{2}"
|
|
BEA-2002107
|
Dynamic: "{0}" declares a column that is not compatible with the expected type "{1}". Column details: {2}
|
|
BEA-2002108
|
Dynamic: "{0}" marks its join columns as explicitly not indexed, but an index exists.
|
|
BEA-2002109
|
Dynamic: The system has detected an incomplete join on column "{0}". When you specify a join between tables, join to all the columns of any fields involved.
|
|
BEA-2002110
|
Dynamic: No order column name was given for "{0}".
|
|
BEA-2002111
|
Dynamic: "{0}" declares an order column "{1}" whose jdbc-type is not compatible with the expected type "{2}".
|
|
BEA-2002112
|
Dynamic: "{0}" declares a join column in table "{1}", but all join columns must be in table "{2}".
|
|
BEA-2002113
|
Dynamic: Field "{0}" declares both a synthetic ordering column and order-by values. You cannot use both.
|
|
BEA-2002114
|
Dynamic: "{0}" declares order column "{1}", but this column does not exist in table "{2}".
|
|
BEA-2002115
|
Dynamic: Missing table name for field "{0}". This field cannot reside in the owning class table.
|
|
BEA-2002116
|
Dynamic: No overridden type mapping for column of type name "{0}".
|
|
BEA-2002117
|
Dynamic: No column name was given for "{0}".
|
|
BEA-2002118
|
Dynamic: No customized name found for class "{0}" of table "{1}".
|
|
BEA-2002119
|
Dynamic: Type "{0}" marks its superclass join columns as having a deferred foreign key, but the database dictionary "{1}" reports that it does not support deferred constraints. Creating an undeferred constraint.
|
|
BEA-2002120
|
Dynamic: "{0}" marks its columns as explicitly not unique, but a unique constraint exists.
|
|
BEA-2002121
|
Dynamic: "{0}" declares a column "{1}" whose jdbc-type is not compatible with the expected type "{2}".
|
|
BEA-2002122
|
Dynamic: "{0}" declares column "{1}", but this column does not exist in table "{2}".
|
|
BEA-2002123
|
Dynamic: "{0}" does not supply a name for at least one declared column.
|
|
BEA-2002124
|
Dynamic: "{0}" declares a null-indicator column column that is not compatible with the expected type "{1}". Column details: {2}
|
|
BEA-2002125
|
Dynamic: The tool is now reading existing schema information; this process may take some time. Enable the org.apache.openjpa.jdbc.Schema logging category to see messages about schema data. Also see the -readSchema tool flag.
|
|
BEA-2002126
|
Dynamic: Could not instantiate custom discriminator strategy "{1}" for type "{0}". Make sure this is a valid DiscriminatorStrategy implementation.
|
|
BEA-2002127
|
Dynamic: "{0}" has an invalid mapping strategy in this context. Expected "{1}" but found "{2}".
|
|
BEA-2002128
|
Dynamic: "{0}" marks its columns as explicitly not indexed, but an index exists.
|
|
BEA-2002129
|
Dynamic: No customized name found for field "{0}" in type "{1}".
|
|
BEA-2002130
|
Dynamic: "{0}" is marked as indexed, but OpenJPA does not support an index on this mapping in this context.
|
|
BEA-2002131
|
Dynamic: "{0}" marks its join columns as having a unique constraint, but your database does not support unique constraints. Include "SupportsUniqueConstraints=true" in the org.apache.openjpa.jdbc.DBDictionary configuration property to override this default.
|
|
BEA-2002132
|
Dynamic: Type "{0}" marks its superclass join columns as having a deferred foreign key, but the existing constraint on these columns is not deferred. OpenJPA cannot change the deferrability of a constraint.
|
|
BEA-2002133
|
Dynamic: "{0}" uses join columns from multiple different tables: "{1}", "{2}"
|
|
BEA-2002134
|
Dynamic: Reverse-mapped type "{0}" is configured to use application identity, but has no primary key fields.
|
|
BEA-2002135
|
Dynamic: Column "{0}" cannot be involved in polymorphic table-per-class relationships because its corresponding field is mapped differently in various classes in the hierarchy.
|
|
BEA-2002136
|
Dynamic: "{0}" defines target field of "{1}" for join column "{2}", but that field does not exist in type "{3}".
|
|
BEA-2002137
|
Dynamic: "{0}" declares a target for column "{1}" in table "{3}", but all targets must be in table "{2}".
|
|
BEA-2002138
|
Dynamic: No datastore identity column name was given for "{0}".
|
|
BEA-2002139
|
Dynamic: "{0}" declares a unique constraint, but has no columns.
|
|
BEA-2002140
|
Dynamic: Collection field "{0}" declares that it is mapped by "{1}", but this is not a valid inverse relation.
|
|
BEA-2002141
|
Dynamic: "{0}" defines target field "{1}" for column "{2}", but OpenJPA cannot deterimine the owning class for that field.
|
|
BEA-2002142
|
Dynamic: Initializing mapping for "{0}".
|
|
BEA-2002143
|
Dynamic: You have supplied columns for "{0}", but this mapping cannot have columns in this context.
|
|
BEA-2002144
|
Dynamic: "{0}" declares invalid constant value target "{1}" for column with name "{2}".
|
|
BEA-2002145
|
Dynamic: "{0}" declares a join foreign key, but has no join columns.
|
|
BEA-2002146
|
Dynamic: Type "{0}" defines target field "{1}" for superclass join column "{2}", but that field is either unmapped or has multiple columns.
|
|
BEA-2002147
|
Dynamic: Customized name found for class "{0}": will rename as "{1}".
|
|
BEA-2002148
|
Dynamic: Column "{0}" is type CHAR(1), but OpenJPA cannot reverse map it into a Java char because OpenJPA is currently configured to store Java chars into numeric database columns. To configure OpenJPA to store Java chars into CHAR(1) columns, set the following property: org.apache.openjpa.jdbc.DBDictionary: StoreCharsAsNumbers=false
|
|
BEA-2002149
|
Dynamic: "{0}" declares an inverse self-join on table "{1}", but this mapping does not allow inverse joins. If you did not intend to make this an inverse join, take the table name out of the column names for this mapping.
|
|
BEA-2002150
|
Dynamic: "{0}" does not supply a target for column "{1}". Since this mapping can involve multiple columns and the a target column with the same name doesn''t exist, give a target explicitly.
|
|
BEA-2002151
|
Dynamic: Could not create a backup file for "{0}".
|
|
BEA-2002152
|
Dynamic: No table was given for persistent type "{0}".
|
|
BEA-2002153
|
Dynamic: Result path "{2}" in result type "{1}" of mapping "{0}" contains invalid fields.
|
|
BEA-2002154
|
Dynamic: "{0}" does not supply a target for join column "{1}". Since this join can involve multiple columns and the a target column with the same name doesn''t exist, give a target explicitly.
|
|
BEA-2002155
|
Dynamic: The following customizer properties were not used in the reverse mapping process: {0}.
|
|
BEA-2002156
|
Dynamic: "{0}" declares a target for join column "{1}" in table "{3}", but all join targets must be in table "{2}".
|
|
BEA-2002157
|
Dynamic: Customized name found for field "{0}" in type "{1}": will rename as "{1}".
|
|
BEA-2002158
|
Dynamic: "{0}" declares a foreign key, but has no columns.
|
|
BEA-2002159
|
Dynamic: Removing class "{0}" of table "{1}" from reverse mapped set.
|
|
BEA-2002160
|
Dynamic: Type "{0}" marks its superclass join columns as explicitly not having a foreign key delete action, but a database foreign key exists on these columns.
|
|
BEA-2002161
|
Dynamic: You cannot join on column "{0}". It is not managed by a mapping that supports joins.
|
|
BEA-2002162
|
Dynamic: "{0}" defines target field "{1}" for column "{2}", but that field is either unmapped or has multiple columns.
|
|
BEA-2002163
|
Dynamic: Type "{0}" declares superclass join column "{1}" with a target in table "{3}", but all targets must be in table "{2}".
|
|
BEA-2002164
|
Dynamic: For "{0}", expected {1} column(s), but found {2}.
|
|
BEA-2002165
|
Dynamic: "{0}" declares a unique join constraint, but has no join columns.
|
|
BEA-2002166
|
Dynamic: Type "{0}" declares a superclass join in table "{1}", but all columns must be in table "{2}".
|
|
BEA-2002167
|
Dynamic: "{0}" marks its columns as having a deferred unique constraint, but the database dictionary "{1}" reports that it does not support deferred constraints. Creating an undeferred constraint.
|
|
BEA-2002168
|
Dynamic: Removing field "{0}" in type "{1}" from reverse mapped set.
|
|
BEA-2002169
|
Dynamic: Type "{0}" declares a datastore identity column that is not compatible with the expected type "{1}". Column details: {2}
|
|
BEA-2002170
|
Dynamic: "{0}" marks its columns as having a deferred foreign key, but the existing constraint on these columns is not deferred. OpenJPA cannot change the deferrability of a constraint.
|
|
BEA-2002171
|
Dynamic: Some of the following mappings may not have been dropped: {0}. Undropped mappings will not affect the system.
|
|
BEA-2002172
|
Dynamic: Type "{0}" is missing information on how to join to its superclass.
|
|
BEA-2002173
|
Dynamic: The reverse mapping tool will run on schema file "{0}".
|
|
BEA-2002174
|
Dynamic: "{0}" defines target field "{1}" for join column "{2}", but OpenJPA cannot deterimine the owning class for that field.
|
|
BEA-2002175
|
Dynamic: The schema for type "{0}" may not be dropped, because its mapping could not be parsed.
|
|
BEA-2002176
|
Dynamic: "{0}" marks its join columns as explicitly not unique, but a unique constraint exists.
|
|
BEA-2002177
|
Dynamic: Type "{0}" does not supply a name for at least one declared column in its superclass join. Since this join can involve multiple columns, each column must give either its name or its target.
|
|
BEA-2002178
|
Dynamic: Cannot use "{0}" as the mapped-by value for a field in "{1}". There is no column "{2}" in this subclass'' table.
|
|
BEA-2002179
|
Dynamic: "{0}" declared custom value handler "{1}", but this handler cannot be instantiated.
|
|
BEA-2002180
|
Dynamic: The reverse mapping tool will run on the database. The tool is gathering schema information; this process may take some time. Enable the org.apache.openjpa.jdbc.Schema logging category to see messages about schema data.
|
|
BEA-2002181
|
Dynamic: Type "{0}" declares invalid constant value target "{1}" for the column with name "{2}" in its superclass join.
|
|
BEA-2002182
|
Dynamic: "{0}" does not supply a name for at least one declared join column.
|
|
BEA-2002183
|
Dynamic: For type "{0}", expected {1} datastore identity column(s), but found {2}.
|
|
BEA-2002184
|
Dynamic: Type "{0}" uses an unsupported foreign key delete or update action on its superclass join columns. Reverting to a logical foreign key.
|
|
BEA-2002185
|
Dynamic: "{0}" has a column with target field "{1}", but that is not a primary key field of the related class.
|
|
BEA-2002186
|
Dynamic: Result path "{2}" in result type "{1}" of mapping "{0}" attempts to traverse through a non-relation field.
|
|
BEA-2002187
|
Dynamic: Table "{0}" given for "{1}" does not exist.
|
|
BEA-2002188
|
Dynamic: "{0}" declares an index, but has no columns.
|
|
BEA-2002189
|
Dynamic: Some of the columns on "{0}" are missing target field declarations.
|
|
BEA-2002190
|
Dynamic: The declared discriminator value "{1}" for type "{0}" cannot be parsed as a number, though it starts with a digit.
|
|
BEA-2002191
|
Dynamic: "{0}" attmpts to join a constant value to another constant value.
|
|
BEA-2002192
|
Dynamic: The superclass join on type "{0}" uses columns from multiple different tables: "{1}", "{2}"
|
|
BEA-2002193
|
Dynamic: Type "{0}" defines a target of "{1}" for superclass join column "{2}", but that target does not exist in table "{3}".
|
|
BEA-2002194
|
Dynamic: "{0}" has mapping strategy "{1}".
|
|
BEA-2002195
|
Dynamic: "{0}" does not supply a name for at least one declared column. Since this mapping can involve multiple columns or uses constant joins, each column must give either its name or a non-constant target.
|
|
BEA-2002196
|
Dynamic: "{0}" marks its join columns as having a deferred foreign key, but the existing constraint on these columns is not deferred. OpenJPA cannot change the deferrability of a constraint.
|
|
BEA-2002197
|
Dynamic: "{0}" declares null-indicator column "{1}", but this column does not exist in table "{2}".
|
|
BEA-2002198
|
Dynamic: "{0}" defines target field "{1}" for column "{2}", but that field does not exist in type "{3}".
|
|
BEA-2002199
|
Dynamic: "{0}" defines target field "{1}" for superclass join column "{2}", but OpenJPA cannot deterimine the owning class for that field.
|
|
BEA-2002200
|
Dynamic: Recording mapping and schema changes.
|
|
BEA-2002201
|
Dynamic: Calculating reverse mappings.
|
|
BEA-2002202
|
Dynamic: "{0}" marks its join columns as having a unique index, but the existing index on those columns is not unique.
|
|
BEA-2002203
|
Dynamic: Type "{0}" defines target field of "{1}" for superclass join column "{2}", but that field does not exist in type "{3}".
|
|
BEA-2002204
|
Dynamic: There is no query result mapping for "{0}" with name "{1}".
|
|
BEA-2002205
|
Dynamic: Field "{0}" declares the lock-group extension. In order to use custom lock groups, have a performance pack or enterprise edition license. Contact sales@bea.com for details on upgrading your license.
|
|
BEA-2002206
|
Dynamic: Overriding type mapping for column of type name "{0}" to Java class "{1}".
|
|
BEA-2002207
|
Dynamic: Attempt to add a null or empty path to result type "{1}" in mapping "{0}".
|
|
BEA-2002208
|
Dynamic: "{0}" attmpts to join a constant value to another constant value.
|
|
BEA-2002209
|
Dynamic: "{0}" declares a null-indicator column "{1}" whose jdbc-type is not compatible with the expected type "{2}".
|
|
BEA-2002210
|
Dynamic: "{0}" does not have a valid mapping. It declares that it is mapped by "{2}", but "{1}", a subclass of its declared type, does not inherit that relation field.
|
|
BEA-2002211
|
Dynamic: Resolving mapping for "{0}".
|
|
BEA-2002212
|
Dynamic: "{0}" cannot be mapped without stringifying the oid of the related object to a string column. The related type is unmapped and its "{1}" primary key field does not use a simple mapping.
|
|
BEA-2002213
|
Dynamic: Field "{0}" declares a char array field mapping strategy, but is not a char array field.
|
|
BEA-2002214
|
Dynamic: Attempt to flush an unmapped object of type "{0}" with oid "{1}".
|
|
BEA-2002215
|
Dynamic: Discriminator value "{0}" is used for two different classes in the same inheritance tree: "{1}", "{2}"
|
|
BEA-2002216
|
Dynamic: The discriminator for type "{0}" cannot compute the list of its subclasses on its own. You should either use a discriminator strategy that has this ability (such as the class-name strategy), include the set of persistent classes in the "org.apache.openjpa.MetaDataFactory" property so that OpenJPA can discover all persistent classes at startup, or make sure that all subclasses of this type have had their class instantiated in the JVM before performing any persistent operations on this class or its subclasses. If this class does not have any subclasses, consider making the class final or changing its discriminator strategy to "final".
|
|
BEA-2002217
|
Dynamic: "{0}" species an object id mapping strategy, but it is not an object id field.
|
|
BEA-2002218
|
Dynamic: Map field "{0}" is attempting to use a map table, but its key is mapped by another field. Use an inverse key or join table mapping.
|
|
BEA-2002219
|
Dynamic: Object id data "{0}" loaded from the database for "{1}" is not in the correct format. Please ensure that your database records are in the correct format.
|
|
BEA-2002220
|
Dynamic: Field "{0}" embedded within object id field "{1}" cannot be a primary key value. Its mapping does not it to be a join target.
|
|
BEA-2002221
|
Dynamic: Field "{0}" declares a primitive field mapping strategy, but is not of a primitive type.
|
|
BEA-2002222
|
Dynamic: Map field "{0}" is attempting to use an inverse key or join table mapping, but its key is not mapped by another field. Use a map table mapping.
|
|
BEA-2002223
|
Dynamic: Field "{0}" declares a handler-based mapping strategy, but no value handler is installed.
|
|
BEA-2002224
|
Dynamic: The subclass-join class indicator mapped to "{0}" requires outer joins to function. Your database dictionary is configured to use "traditional" join syntax, which does not support outer joins. To use SQL 92 joins instead, set the following property: org.apache.openjpa.jdbc.DBDictionary: JoinSyntax=sql92
|
|
BEA-2002225
|
Dynamic: The discriminator column "{1}" for type "{1}" contains a null or empty value.
|
|
BEA-2002226
|
Dynamic: Field "{0}" declares a byte array field mapping strategy, but is not a byte array field.
|
|
BEA-2002227
|
Dynamic: Inefficient mapping: You have declared that field "{0}" is mapped by collection "{1}". The mapping would be much more efficient if instead you map "{0}" and declare that "{1}" is mapped by it.
|
|
BEA-2002228
|
Dynamic: Type "{0}" does not have any fields that participate in optimistic locking. Set its version strategy to "none".
|
|
BEA-2002229
|
Dynamic: "{0}" is not a valid mapping. The related type has subclasses that are not reachable via joins, so OpenJPA must be able to construct an oid from the mapped foreign key. But your foreign key does not represent all primary key values of the related type.
|
|
BEA-2002230
|
Dynamic: Type "{0}" specifies a full class mapping strategy, but has a mapped persistence capable superclass or is embedded. Use a valid subclass or embedded strategy instead.
|
|
BEA-2002231
|
Dynamic: Attempt to use an auto-assigned column value in a handler with multiple columns. To use an auto-assigned column value with field "{0}", you will have to write a custom field mapping that implements the org.apache.openjpa.jdbc.meta.Joinable interface.
|
|
BEA-2002232
|
Dynamic: "{0}" declares a relation mapping strategy, but is not a direct, non-embedded relation to another persistence-capable object.
|
|
BEA-2002233
|
Dynamic: Field "{0}" declares "{1}" as its mapped-by field, but this field is not a direct relation.
|
|
BEA-2002234
|
Dynamic: "{0}" declares a to-many relation strategy, but its elements are not direct, non-embedded relations to another mapped persistence-capable object.
|
|
BEA-2002235
|
Dynamic: Field "{0}" cannot declare that it is mapped by another field. Its mapping strategy ({1}) does not support mapping by another field.
|
|
BEA-2002236
|
Dynamic: Could not map disciminator value "{0}" to any known subclasses of the requested class "{1}" (known discriminator values: {2}).
|
|
BEA-2002237
|
Dynamic: Field "{0}" cannot be mapped by "{1}", because the related type is unmapped.
|
|
BEA-2002238
|
Dynamic: Field "{0}" declares a string field mapping strategy, but is not a string field.
|
|
BEA-2002239
|
Dynamic: Field "{0}" declares that it uses class criteria for joins, and this field is not owned by an inverse field. As a result, it is impossible to correctly null the inverse foreign keys when the field is deleted. OpenJPA may leave orphan key values in the database if you do not provide an owning inverse relation using the "mapped-by" attribute.
|
|
BEA-2002240
|
Dynamic: Type "{0}" specifies a discriminator strategy, but has a mapped persistence capable superclass or is embedded. Subclasses and embedded values must use the discriminator strategy of the base or embedding class.
|
|
BEA-2002241
|
Dynamic: Type "{0}" specifies a version strategy, but has a mapped persistence capable superclass or is embedded. Subclasses and embedded values must use the version strategy of the base or embedding class.
|
|
BEA-2002242
|
Dynamic: Loading subclasses from discriminator column of "{0}".
|
|
BEA-2002243
|
Dynamic: This container was loaded in large result set field "{0}", but has been removed from its owning field. Therefore, it can no longer be used.
|
|
BEA-2002244
|
Dynamic: "{0}" cannot be used in a projection, because it can only be loaded as part of its owning object.
|
|
BEA-2002245
|
Dynamic: Field "{0}" declares "{1}" as its mapped-by field, but this field is not a collection of inverse relations.
|
|
BEA-2002246
|
Dynamic: Type "{0}" uses a flat inheritance mapping, but declares a table name of "{1}", which does not match the superclass table "{2}".
|
|
BEA-2002247
|
Dynamic: Field "{0}" declares a blob mapping strategy, but the field''s value is not serialized. Set the field''s "serialized" attribute to true.
|
|
BEA-2002248
|
Dynamic: Type "{0}" specifies a subclass mapping strategy, but does not have a mapped persistence capable superclass or is embedded. Use a valid base or embedded class strategy instead.
|
|
BEA-2002249
|
Dynamic: Field "{0}" declares a map mapping strategy, but is not a map type.
|
|
BEA-2002250
|
Dynamic: "{0}" specifies an embedded mapping strategy, but it is not embedded.
|
|
BEA-2002251
|
Dynamic: Field "{0}" as defined in "{1}" cannot be mapped by "{2}". You cannot use an inverse foreign key to map a superclass field of an unjoined subclass.
|
|
BEA-2002252
|
Dynamic: Field "{0}" declares a collection mapping strategy, but is not a collection or array type.
|
|
BEA-2002253
|
Dynamic: Cannot join across "{0}". The related type has unjoined subclasses.
|
|
BEA-2002254
|
Dynamic: You cannot map a logical foreign key relation to an object with an unknown identity type.
|
|
BEA-2002255
|
Dynamic: "{0}" is not a valid mapping. Inverse foreign key-based relations to types with unjoined subclasses are not supported.
|
|
BEA-2002256
|
Dynamic: Type "{0}" uses the value-map discriminator strategy, but does not declare a discriminator value.
|
|
BEA-2002257
|
Dynamic: "{0}" is mapped as embedded, but embedded field "{1}" is not embeddable. Embedded element/key/value types are limited to simple fields and direct relations to other persistent types.
|
|
BEA-2002258
|
Dynamic: Field "{0}" declares a clob field mapping strategy, but is not a string field.
|
|
BEA-2002259
|
Dynamic: Reading schemas
|
|
BEA-2002260
|
Dynamic: The sequence "{0}" was not added to the database.
|
|
BEA-2002261
|
Dynamic: Reading sequences for schema "{0}"
|
|
BEA-2002262
|
Dynamic: The column "{0}" was not dropped from table "{1}".
|
|
BEA-2002263
|
Dynamic: Reading table information for schema name "{0}", table name "{1}".
|
|
BEA-2002264
|
Dynamic: The column "{1}" specified by foreign key "{0}" on table "{2}" does not exist in that table.
|
|
BEA-2002265
|
Dynamic: Gathering schema information to export; this process may take some time. Enable the org.apache.openjpa.jdbc.Schema logging category to see messages about the collection of schema data.
|
|
BEA-2002266
|
Dynamic: Reading indexes for schema name "{0}", table name "{1}".
|
|
BEA-2002267
|
Dynamic: Existing foreign key "{0}" on table "{1}" is incompatible with the same foreign key in the given schema definition.
|
|
BEA-2002268
|
Dynamic: The specified driver "{0}" is neither a java.sql.Driver nor a javax.sql.DataSource class name.
|
|
BEA-2002269
|
Dynamic: Unable to get index information for table "{0}": "{1}"
|
|
BEA-2002270
|
Dynamic: Your license only permits a maximum of {0} pooled connections; the connection pool will be configured accordingly.
|
|
BEA-2002271
|
Dynamic: The index "{0}" was not created on table "{1}", since it would go beyond the maximum index limit of {2}.
|
|
BEA-2002272
|
Dynamic: The sequence "{0}" was not dropped.
|
|
BEA-2002273
|
Dynamic: The index "{0}" was not dropped from table "{1}".
|
|
BEA-2002274
|
Dynamic: Reading indexes for schema "{0}"
|
|
BEA-2002275
|
Dynamic: Creating table to hold schema information.
|
|
BEA-2002276
|
Dynamic: use a custom DataSource
|
|
BEA-2002277
|
Dynamic: Reading foreign keys for schema "{0}"
|
|
BEA-2002278
|
Dynamic: Dropping schema table.
|
|
BEA-2002279
|
Dynamic: Writing XML representation of schema.
|
|
BEA-2002280
|
Dynamic: Usage: java org.apache.openjpa.jdbc.schema.TableSchemaFactory [-properties ] [- ] -action/-a
|
BEA-2002281
|
Dynamic: You must supply a valid name for this schema component.
|
|
BEA-2002282
|
Dynamic: Schema tool will run on schema file "{0}".
|
|
BEA-2002283
|
Dynamic: Reading schema "{0}"
|
|
BEA-2002284
|
Dynamic: The foreign table "{1}" specified in foreign key "{0}" on table "{2}" does not exist or does not have a primary key.
|
|
BEA-2002285
|
Dynamic: Reading indexes for table "{1}"
|
|
BEA-2002286
|
Dynamic: The index "{0}" was not created on table "{1}".
|
|
BEA-2002287
|
Dynamic: The following error was detected when creating a foreign key: "{0}". The foreign key is being ignored.
|
|
BEA-2002288
|
Dynamic: Existing index "{0}" on table "{1}" is incompatible with the same index in the given schema definition.
|
|
BEA-2002289
|
Dynamic: Existing column "{0}" on table "{1}" is incompatible with the same column in the given schema definition. Existing column: {2}Given column: {3}
|
|
BEA-2002290
|
Dynamic: Reading columns for table "{1}"
|
|
BEA-2002291
|
Dynamic: Reading primary keys for schema "{0}"
|
|
BEA-2002292
|
Dynamic: "{1}" is not a recognized foreign key action. Available actions are: {2}
|
|
BEA-2002293
|
Dynamic: The foreign key "{0}" was not added to table "{1}".
|
|
BEA-2002294
|
Dynamic: Found existing foreign key "{0}" on table "{1} ({2})" linking to table "{3} ({4})". Sequence: "{5}".
|
|
BEA-2002295
|
Dynamic: Reading primary keys for schema name "{0}", table name "{1}".
|
|
BEA-2002296
|
Dynamic: Storing imported schema data in schema factory.
|
|
BEA-2002297
|
Dynamic: Table "{0}" has a foreign key to table "{1}" that has not been generated. You must run the schema generator on all inter-related tables at once.
|
|
BEA-2002298
|
Dynamic: Refresh operation cancelled.
|
|
BEA-2002299
|
Dynamic: The column "{1}" specified as part of index "{0}" on table "{2}" does not exist in that table.
|
|
BEA-2002300
|
Dynamic: Reading foreign keys for table "{1}"
|
|
BEA-2002301
|
Dynamic: Existing primary key "{0}" on table "{1}" is incompatible with the same primary key in the given schema definition.
|
|
BEA-2002302
|
Dynamic: The foreign key "{0}" was not dropped from table "{1}".
|
|
BEA-2002303
|
Dynamic: Reading column information for table "{0}".
|
|
BEA-2002304
|
Dynamic: Reading primary keys for table "{1}"
|
|
BEA-2002305
|
Dynamic: A JDBC Driver or DataSource class name must be specified in the ConnectionDriverName property.
|
|
BEA-2002306
|
Dynamic: Attempt to write the schema information table for the second time failed. See previous log messages for possible reasons.
|
|
BEA-2002307
|
Dynamic: First attempt to write to the schema information table failed; will attempt to create the table in case it has been dropped before re-trying: {0}
|
|
BEA-2002308
|
Dynamic: Found existing column "{0}" on table "{1}".
|
|
BEA-2002309
|
Dynamic: Schema tool running action "{0}". This process may take some time. Enable the org.apache.openjpa.jdbc.Schema logging category to see messages about the collection of schema data, and the org.apache.openjpa.jdbc.SQL category to see generated SQL commands.
|
|
BEA-2002310
|
Dynamic: You cannot perform this action until you set the schema group to act on.
|
|
BEA-2002311
|
Dynamic: Usage: java org.apache.openjpa.jdbc.schema.SchemaTool [-properties/-p ] [- ]* [-file/-f ] [-ignoreErrors/-i ] [-dropTables/-dt ] [-openjpaTables/-kt ] [-dropSequences/-dsq ] [-sequences/-sq ] [-primaryKeys/-pk ] [-foreignKeys/-fk ] [-indexes/-ix ] [-record/-r ] [-action/-a ] <.schema file or resource>*
|
BEA-2002312
|
Dynamic: Reflecting on schemas "{0}". This process may take some time. Enable the org.apache.openjpa.jdbc.Schema logging category to see messages about the collection of schema data.
|
|
BEA-2002313
|
Dynamic: Reading sequence information for schema "{0}", sequence name "{1}".
|
|
BEA-2002314
|
Dynamic: Recording schema changes.
|
|
BEA-2002315
|
Dynamic: Reading foreign keys for schema name "{0}", table name "{1}".
|
|
BEA-2002316
|
Dynamic: The column "{1}" of table "{2}" joined to by foreign key "{0}" on table "{3}" does not exist or is not a primary key column.
|
|
BEA-2002317
|
Dynamic: The primary key "{0}" was not added to table "{1}".
|
|
BEA-2002318
|
Dynamic: Found existing index "{0}" on table "{1} ({2})".
|
|
BEA-2002319
|
Dynamic: You are attempting to link to a primary key column in table "{0}" in a foreign key that is already linked to primary key columns in table "{1}".
|
|
BEA-2002320
|
Dynamic: Found existing primary key "{0}" on table "{1} ({2})".
|
|
BEA-2002321
|
Dynamic: The table "{0}" was not dropped.
|
|
BEA-2002322
|
Dynamic: Writing schema data to XML.
|
|
BEA-2002323
|
Dynamic: The name "{0}" is already taken by a column in this table.
|
|
BEA-2002324
|
Dynamic: The primary key "{0}" was not dropped from table "{1}".
|
|
BEA-2002325
|
Dynamic: The schema information table could not be created: {0}
|
|
BEA-2002326
|
Dynamic: The table "{0}" was not created.
|
|
BEA-2002327
|
Dynamic: Unable to get index metadata for table "{0}": {1}
|
|
BEA-2002328
|
Dynamic: Writing schema "{0}".
|
|
BEA-2002329
|
Dynamic: The column "{0}" was not added to table "{1}".
|
|
BEA-2002330
|
Dynamic: Bad numeric constant for attribute in sequence "{0}".
|
|
BEA-2002331
|
Dynamic: You are attempting to add a column from table "{0}" to a constraint or index on table "{1}".
|
|
BEA-2002332
|
Dynamic: The column "{1}" specified as part of unique constraint "{0}" on table "{2}" does not exist in that table.
|
|
BEA-2002333
|
Dynamic: "{1}" is not a recognized foreign key action, though it closely resembles the standard action "{2}". Available actions are: {3}
|
|
BEA-2002334
|
Dynamic: The column "{0}" specified as a primary key for table "{1}" does not exist in that table.
|
|
BEA-2002335
|
Dynamic: Attempt to read the schema information table failed; continuing on the assumption that the table has not been created yet, and there is no data to read: {0}
|
|
BEA-2002336
|
Dynamic: This version of the DataDirect JDBC driver has a bug that prevents SELECT FOR UPDATE statements from working. Please use version 3.2 or higher of the driver.
|
|
BEA-2002337
|
Dynamic: This database dictionary does not support auto-assigned column values.
|
|
BEA-2002338
|
Dynamic: The database "{0}" does not support the indexOf function.
|
|
BEA-2002339
|
Dynamic: Informix cannot perform FOR UPDATE selects on multiple tables, or when it is a SELECT DISTINCT. The tables used in this select are: "{0}". You should either configure your application to avoid multi-table/distinct selects, use optimistic locking, or set the "SimulateLocking" DBDictionary property to allow non-locking selects within pessimistic transactions.
|
|
BEA-2002340
|
Dynamic: Foreign key "{0}" on table "{1}" references a table ("{2}") that was not found.
|
|
BEA-2002341
|
Dynamic: LOB operations not allowed for batched statement: {0}
|
|
BEA-2002342
|
Dynamic: The database dictionary in use ("{0}") reports that it does not have feature "{1}". This feature is needed to complete the current operation. To force OpenJPA to try to use the feature anyway, set the following property: org.apache.openjpa.jdbc.DBDictionary: {1}=
|
BEA-2002343
|
Dynamic: Oracle 8 does not support SQL92 syntax. You can avoid this message by setting the "JoinSyntax" DBDictionary property to "database".For example: org.apache.openjpa.jdbc.DBDictionary: oracle(JoinSyntax=database)
|
|
BEA-2002344
|
Dynamic: Could not find an OracleConnection instance from this connection class "{0}".
|
|
BEA-2002345
|
Dynamic: The Microsoft JDBC driver has bugs that manifest themselves when prepared statements are pooled. Please disable prepared statement pooling when using the Microsoft JDBC driver by including "MaxCachedStatements=0" in your org.apache.openjpa.ConnectionFactoryProperties configuration property.
|
|
BEA-2002346
|
Dynamic: Cannot outer join tables "{0}" and "{1}" using native join syntax and constant joins. If you are using Oracle 9 or higher, you should instead use SQL92 joins by specifying the JoinSyntax value in the org.apache.openjpa.jdbc.DBDictionary configuration property: org.apache.openjpa.jdbc.DBDictionary: oracle(JoinSyntax=sql92).
|
|
BEA-2002347
|
Dynamic: The Oracle 9.2 JDBC driver has problems with batch statements and has been disabled by default. You can enable batched statements by setting the "BatchLimit" DBDictionary property. You may be able to bypass this problem by disabling prepared statement pooling. The compatible 9.0.1 driver does not have this behavior.
|
|
BEA-2002348
|
Dynamic: The BatchLimit property was set even though the Oracle 9.2 driver may not support this behavior correctly. If you see a number of invalid update count errors, you should disable statement batching by setting the BatchLimit property to 0.
|
|
BEA-2002349
|
Dynamic: Could not outer join the given foreign key "{0}" due to syntax and foreign key limitations. The join was converted to an inner join.
|
|
BEA-2002350
|
Dynamic: You are using NCHAR or NCLOB columns with a data source or driver that doesn't implement OraclePreparedStatement.setFormOfUse(). Storing unicode values may fail or be corrupted.
|
|
BEA-2002351
|
Dynamic: supplied array of result object providers is empty
|
|
BEA-2002352
|
Dynamic: The following error was detected when creating a foreign key: "{0}". The foreign key is being ignored.
|
|
BEA-2002353
|
Dynamic: This dictionary ({0}) does not support locking, so operations may not be performed using a Broker that does not have optimistic locking enabled.
|
|
BEA-2002354
|
Dynamic: DBDictionary configuration: {0}
|
|
BEA-2002355
|
Dynamic: SQLResultSetMapping "{0}" does not map the columns "{1}" that are selected by the SQL query "{2}"
|
|
BEA-2002356
|
Dynamic: Your license does not have SQL batching capabilities.
|
|
BEA-2002357
|
Dynamic: This database dictionary "{0}" does not support auto-assigned column values. The column "{1}" may not behave as desired.
|
|
BEA-2002358
|
Dynamic: Aborting UNION: cannot select placeholder for non-column select SQL.
|
|
BEA-2002359
|
Dynamic: This database dictionary "{0}" is not officially supported by BEA.
|
|
BEA-2002360
|
Dynamic: OpenJPA is now connecting to the database in order to figure out what JDBC driver you are using, as OpenJPA must alter its behavior for this database depending on the driver vendor. To avoid this connection, set the DriverVendor value in your org.apache.openjpa.jdbc.DBDictionary configuration property to one of the following values: oracle, oracle92 (for the 9.2 driver), datadirect, datadirect61 (for driver versions <= 3.1), other For example: org.apache.openjpa.jdbc.DBDictionary: oracle(DriverVendor=oracle92)
|
|
BEA-2002361
|
Dynamic: The JNetDirect JDBC driver has problems when using batch statements. Please disable prepared statement pooling when using the this JDBC driver by including "BatchLimit=0" in your org.apache.openjpa.jdbc.DBDictionary configuration property.
|
|
BEA-2002362
|
Dynamic: Aborting UNION: incompatible ordering columns/sql or direction.
|
|
BEA-2002363
|
Dynamic: Aborting UNION: your database does not support ordering columns/sql that appear at different positions in the SELECTs that make up the UNION.
|
|
BEA-2002364
|
Dynamic: An error occurred when attempting to rollback to an Oracle savepoint "{0}". You must use Oracle driver and database 9.2 or higher.
|
|
BEA-2002365
|
Dynamic: They Sybase connection URL "{0}" may be invalid: it does not contain the parameter "BE_AS_JDBC_COMPLIANT_AS_POSSIBLE=true", which is required for the Sybase JConnect driver to behave in a JDBC-compliant way.
|
|
BEA-2002366
|
Dynamic: Aborting UNION: different numbers of order-by criteria in selects.
|
|
BEA-2002367
|
Dynamic: The last generated key query did not return any results.
|
|
BEA-2002368
|
Dynamic: DB2 cannot perform FOR UPDATE selects on multiple tables. The tables used in this select are: "{0}". You should either configure your application to avoid multi-table selects, use optimistic locking, or set the "SimulateLocking" DBDictionary property to allow non-locking selects within pessimistic transactions.
|
|
BEA-2002369
|
Dynamic: Your database configuration was not recognized as a supported OpenJPA database. The generic dictionary will be used, which may result in limited functionality. This behavior can be overridden by specifying the appropriate dictionary class in the "org.apache.openjpa.jdbc.DBDictionary" property of the OpenJPA configuration.
|
|
BEA-2002370
|
Dynamic: {0}.{1}() is illegal to be invoked
|
|
BEA-2002371
|
Dynamic: The column "{0}" was marked as being auto-assigned, but the server reported that the assigned value was null.
|
|
BEA-2002372
|
Dynamic: You are using CHAR columns with a data source or driver that doesn't implement OraclePreparedStatement.setFixedCHAR(). Comparisons on unpadded string values may fail.
|
|
BEA-2002373
|
Dynamic: This version of the PostgreSQL JDBC driver does not support the Statement.setFetchSize() method. OpenJPA will no longer attempt to set the statement fetch size. To suppress this warning, ensure that the org.apache.openjpa.FetchBatchSize configuration property is set to zero. The original PostgreSQL driver exception is being logged for your reference.
|
|
BEA-2002374
|
Dynamic: supplied array of result object providers is null
|
|
BEA-2002375
|
Dynamic: An error occurred when attempting to set an Oracle savepoint "{0}". You must use Oracle driver and database 9.2 or higher.
|
|
BEA-2002376
|
Dynamic: Individual selects involved in a UNION do not support this operation.
|
|
BEA-2002377
|
Dynamic: supplied result set is null
|
|
BEA-2002378
|
Dynamic: The SQLServer connection URL "{0}" may be invalid: it does not contain the parameter "SelectMethod=cursor", which is necessary for the driver to properly support large result sets.
|
|
BEA-2002379
|
Dynamic: The database "{0}" does not support the substring function.
|
|
BEA-2002380
|
Dynamic: This query cannot be completed. The SQL SELECTs needed to complete the query have incompatible ordering. Their results cannot be merged.
|
|
BEA-2002381
|
Dynamic: The specified parameter of type "{0}" is not a valid query parameter.
|
|
BEA-2002382
|
Dynamic: Using dictionary class "{0}"{1}.
|
|
BEA-2002383
|
Dynamic: Attempt to set column "{0}" to two different values: ({1})"{2}", ({3})"{4}" This can occur when you fail to set both sides of a two-sided relation between objects, or when you map different fields to the same column, but you do not keep the values of these fields in synch.
|
|
BEA-2002384
|
Dynamic: The database "{0}" has restrictions that prevent it from being able to store the value "{1}" of type "{2}". The value will be rounded to "{3}" for storage.
|
|
BEA-2002385
|
Dynamic: min
|
|
BEA-2002386
|
Dynamic: Size
|
|
BEA-2002387
|
Dynamic: The number of milliseconds between runs of the eviction thread. -1 indicates that the thread will never run.
|
|
BEA-2002388
|
Dynamic: Redundant statements
|
|
BEA-2002389
|
Dynamic: Cache hits
|
|
BEA-2002390
|
Dynamic: Force all connections to be rolled back when they are returned to the pool.
|
|
BEA-2002391
|
Dynamic: An error occurred attempting to invoke JDBC 3 method. Your driver or database may not support JDBC 3 features.
|
|
BEA-2002392
|
Dynamic: The maximum number of milliseconds to block for database login.
|
|
BEA-2002393
|
Dynamic: Shutting down connection pool.
|
|
BEA-2002394
|
Dynamic: The JDBC URL for the database.
|
|
BEA-2002395
|
Dynamic: Created statements
|
|
BEA-2002396
|
Dynamic: Attempt to operate on connection "{0}" that has already been returned to the connection pool.
|
|
BEA-2002397
|
Dynamic: Connection opening
|
|
BEA-2002398
|
Dynamic: The maximum number of database connections in use at one time.
|
|
BEA-2002399
|
Dynamic: A connection could not be obtained for driver class "{0}" and URL "{1}". You may have specified an invalid URL.
|
|
BEA-2002400
|
Dynamic: Count
|
|
BEA-2002401
|
Dynamic: total
|
|
BEA-2002402
|
Dynamic: Requests
|
|
BEA-2002403
|
Dynamic: The maximum number of milliseconds to wait for a free database connection to become available before giving up.
|
|
BEA-2002404
|
Dynamic: Size
|
|
BEA-2002405
|
Dynamic: Overflow
|
|
BEA-2002406
|
Dynamic: Error loading JDBC 3 method.
|
|
BEA-2002407
|
Dynamic: Leaked statements
|
|
BEA-2002408
|
Dynamic: {0}
|
|
BEA-2002409
|
Dynamic: occurances
|
|
BEA-2002410
|
Dynamic: The JDBC driver.
|
|
BEA-2002411
|
Dynamic: ResultSet closing
|
|
BEA-2002412
|
Dynamic: The minimum number of milliseconds that must elapse before a connection will ever be re-validated.
|
|
BEA-2002413
|
Dynamic: Number of idle connections in pool.
|
|
BEA-2002414
|
Dynamic: Count
|
|
BEA-2002415
|
Dynamic: max
|
|
BEA-2002416
|
Dynamic: Cached statements
|
|
BEA-2002417
|
Dynamic: Properties applied to the JDBC driver or datasource.
|
|
BEA-2002418
|
Dynamic: Redundant
|
|
BEA-2002419
|
Dynamic: Hits
|
|
BEA-2002420
|
Dynamic: average
|
|
BEA-2002421
|
Dynamic: An unexpected exception of type "{0}" occurred while getting a connection. This exception will be re-thrown as a SQLException.
|
|
BEA-2002422
|
Dynamic: Whether to validate database connections before obtaining them from the pool.
|
|
BEA-2002423
|
Dynamic: Commit execution
|
|
BEA-2002424
|
Dynamic: The minimum number of milliseconds that a database connection can sit idle before it becomes a candidate for eviction from the pool.
|
|
BEA-2002425
|
Dynamic: Statement execution
|
|
BEA-2002426
|
Dynamic: Created
|
|
BEA-2002427
|
Dynamic: Waited {0} milliseconds for connection {1}. This might indicate that you need to increase your connection pool size.
|
|
BEA-2002428
|
Dynamic: slowest statements
|
|
BEA-2002429
|
Dynamic: PreparedStatement execution
|
|
BEA-2002430
|
Dynamic: Number of active connections in pool.
|
|
BEA-2002431
|
Dynamic: Whether to periodically validate idle database connections.
|
|
BEA-2002432
|
Dynamic: Cache requests
|
|
BEA-2002433
|
Dynamic: The prepared statement cache has overflowed. "{0}" was removed. You may want to increase your prepared statement cache size. The maximum number of cached statements is currently set to {1}.
|
|
BEA-2002434
|
Dynamic: The JDBC user name for connecting to the database.
|
|
BEA-2002435
|
Dynamic: Count
|
|
BEA-2002436
|
Dynamic: SQL used to validate connections
|
|
BEA-2002437
|
Dynamic: The maximum number of idle database connections to keep in the pool.
|
|
BEA-2002438
|
Dynamic: Cache overflows
|
|
BEA-2002439
|
Dynamic: The connection "{0}" has already been closed. The embedded stack trace for this exception details the closure point.
|
|
BEA-2002440
|
Dynamic: Statements
|
|
BEA-2002441
|
Dynamic: Rollback execution
|
|
BEA-2002442
|
Dynamic: ms
|
|
BEA-2002443
|
Dynamic: Error caught when issuing close pool SQL: {0}
|
|
BEA-2002444
|
Dynamic: Statements
|
|
BEA-2002445
|
Dynamic: Leaked
|
|
BEA-2002446
|
Dynamic: Attempted to call JDBC 3 method on a non-JDBC 3 JVM.
|
|
BEA-2002447
|
Dynamic: Statements
|
|
BEA-2002448
|
Dynamic: The maximum number of connections ({0}) for the connection pool have been exhausted.
|
|
BEA-2002449
|
Dynamic: Whether to validate database connections before returning them to the pool.
|
|
BEA-2002450
|
Dynamic: Number of connections tested per eviction run.
|
|
BEA-2002451
|
Dynamic: Found duplicate generator "{0}" in "{1}". Overriding previous definition.
|
|
BEA-2002452
|
Dynamic: Detected declared unique constraints on "{0}". OpenJPA does not yet support the @UniqueConstraint annotation.
|
|
BEA-2002453
|
Dynamic: Type "{0}" declares an unnamed @SecondaryTable.
|
|
BEA-2002454
|
Dynamic: Version property "{0}" cannot map to a secondary table column. Version columns must always be in the primary table of the class.
|
|
BEA-2002455
|
Dynamic: Found duplicate generator "{0}" in "{1}". Ignoring.
|
|
BEA-2002456
|
Dynamic: Found duplicate result set mapping "{0}" in "{1}". Ignoring.
|
|
BEA-2002457
|
Dynamic: Expected "{0}" to have "{1}" column(s), but you specified "{2}" column(s).
|
|
BEA-2002458
|
Dynamic: Attempt to declare mapping overrides on non-embedded field "{0}".
|
|
BEA-2002459
|
Dynamic: "{0}" declares inconsistent secondary tables on its join columns.
|
|
BEA-2002460
|
Dynamic: Embedded property "{0}" declares a mapping override for "{1}", but that is not a persistent property in the embedded type.
|
|
BEA-2002461
|
Dynamic: No generated table found at "{0}".
|
|
BEA-2002462
|
Dynamic: OpenJPA does not yet support "{1}" as used in "{0}".
|
|
BEA-2002463
|
Dynamic: The "usePKasFK" attribute is not yet supported. Mapping your OneToOne using JoinColumns that match your id property columns will work.
|
|
BEA-2002464
|
Dynamic: Parsing table generator "{0}".
|
|
BEA-2002465
|
Dynamic: Missing "name" property on mapping override for "{0}".
|
|
BEA-2002466
|
Dynamic: Found duplicate result set mapping "{0}" in "{1}". Overriding previous definition.
|
|
BEA-2002467
|
Dynamic: "{0}" declares a secondary table on columns that do not support this attribute.
|
|
BEA-2002468
|
Dynamic: Detected inconsistent values of "unique" on different columns of "{0}". OpenJPA does not yet support different per-column unique values. All columns for this mapping must use the same values.
|
|
BEA-2002469
|
Dynamic: The table generator in "{0}" must declare a name.
|
|
BEA-2002470
|
Dynamic: Parsing result set mapping "{0}".
| | | |
