Kodo Subsystem Messages

BEA-2000000

Dynamic: Found duplicate generator "{0}" in "{1}". Overriding previous definition.

BEA-2000001

Dynamic: Invalid EntityManager properties passed to createEntityManager. See nested exceptions for details.

BEA-2000002

Dynamic: "{0}" is not a recognized query hint.

BEA-2000003

Dynamic: Parsing query "{0}".

BEA-2000004

Dynamic: Query did not return any results: "{0}".

BEA-2000005

Dynamic: "{0}" declares an unnamed fetch group. All fetch groups must have names.

BEA-2000006

Dynamic: An error occurred invoking system entity listener callback on instance "{0}".

BEA-2000007

Dynamic: Object "{0}" is not managed by this context.

BEA-2000008

Dynamic: OpenJPA does not yet support "{1}" as used in "{0}".

BEA-2000009

Dynamic: The named query "{0}" in "{1}" must declare a query string.

BEA-2000010

Dynamic: Could not load id class "{1}" for type "{0}".

BEA-2000011

Dynamic: OpenJPA does not currently support XML element "{0}". Ignoring.

BEA-2000012

Dynamic: Found duplicate query "{0}" in "{1}". Ignoring.

BEA-2000013

Dynamic: Writing query "{1}" in class "{0}".

BEA-2000014

Dynamic: There is no managed transaction in progress to sync this EntityManager with.

BEA-2000015

Dynamic: Setting the following properties from "{0}" into configuration: {1}

BEA-2000016

Dynamic: Parsing package "{0}".

BEA-2000017

Dynamic: The named native query "{0}" in "{1}" must declare a query string.

BEA-2000018

Dynamic: Found duplicate generator "{0}" in "{1}". Ignoring.

BEA-2000019

Dynamic: Writing query "{1}".

BEA-2000020

Dynamic: Fetch group "{0}" in type "{1}" sets a non-zero fetch-depth for field "{2}". OpenJPA currently only supports a fetch depth of zero. Resetting depth to 0.

BEA-2000021

Dynamic: Fields "{0}" are not a default persistent type, and do not have any annotations indicating their persistence strategy. If you do not want these fields to be persisted, annotate them with @Transient.

BEA-2000022

Dynamic: Field "{0}" is included in fetch group "{1}", but is also in the default fetch group. OpenJPA currently limits fields to one fetch group. Set the field''s "fetch" attribute to "FetchType.LAZY" to exclude it from the default fetch group.

BEA-2000023

Dynamic: No class attribute was specified.

BEA-2000024

Dynamic: Parsing sequence "{0}".

BEA-2000025

Dynamic: Parsing class "{0}".

BEA-2000026

Dynamic: The type of field "{0}" isn''t supported by declared persistence strategy "{1}". Please choose a different strategy.

BEA-2000027

Dynamic: Found duplicate metadata or mapping for "{0}". Ignoring.

BEA-2000028

Dynamic: The jar resource "{0}" cannot be loaded.

BEA-2000029

Dynamic: Cannot perform a select on update or delete query: "{0}".

BEA-2000030

Dynamic: Type "{0}" does not have a managed field named "{1}".

BEA-2000031

Dynamic: Cannot perform this operation on removed entity "{0}".

BEA-2000032

Dynamic: "{0}" declares generator name "{1}", but uses the AUTO generation type. The only valid generator names under AUTO are "uuid-hex" and "uuid-string".

BEA-2000033

Dynamic: The named query in "{0}" must declare a name.

BEA-2000034

Dynamic: The parameter index {0} is invalid. Parameters must be integers starting at 1.

BEA-2000035

Dynamic: Found duplicate query "{0}" in "{1}". Overriding previous definition.

BEA-2000036

Dynamic: You must provide a SQL string when creating a native query.

BEA-2000037

Dynamic: When using a persistence context type of TRANSACTION, you can only perform this operation during an active transaction.

BEA-2000038

Dynamic: Cannot perform an update or delete operation on select query: "{0}".

BEA-2000039

Dynamic: There is no known entity class for entity name "{0}". It is possible that the corresponding class has not yet been registered in the JVM.

BEA-2000040

Dynamic: Query returned multiple results: "{0}".

BEA-2000041

Dynamic: Invalid EntityManager property passed to createEntityManager. Key: "{0}", Value: "{1}".

BEA-2000042

Dynamic: Writing class "{0}".

BEA-2000043

Dynamic: Field "{0}" is included in fetch group "{1}", but is already in fetch group "{2}". OpenJPA currently limits fields to one fetch group.

BEA-2000044

Dynamic: The class "{0}" is not an entity.

BEA-2000045

Dynamic: The named native query in "{0}" must declare a name.

BEA-2000046

Dynamic: The parameter "{0}" is of type "{1}", but the declaration in the query is for type "{2}".

BEA-2000047

Dynamic: Parsing native query "{0}".

BEA-2000048

Dynamic: Fetch group "{0}" in type "{1}" includes field "{2}", but this field is not declared in "{1}", or is not persistent. Currently, OpenJPA only supports declared fields in fetch groups.

BEA-2000049

Dynamic: Could not find property/field with the name "{0}" in type "{1}".

BEA-2000050

Dynamic: Writing sequence "{0}".

BEA-2000051

Dynamic: The sequence generator in "{0}" must declare a name.

BEA-2000052

Dynamic: The specified XML resource "{0}" for persistence unit "{1}" can''t be found in your class path.

BEA-2000053

Dynamic: You cannot access the EntityTransaction when using managed transactions.

BEA-2000054

Dynamic: Cannot perform operation with no transaction.

BEA-2000055

Dynamic: A NamingException was thrown while obtaining the factory at "{0}" from JNDI.

BEA-2000056

Dynamic: Cannot mix named and positional parameters in query "{0}".

BEA-2000057

Dynamic: The specified XML resource "{0}" for persistence unit "{1}" can''t be parsed.

BEA-2000058

Dynamic: Field "{0}" cannot be annotated by two persistence strategy annotations.

BEA-2000059

Dynamic: Cannot perform this operation on detached entity "{0}".

BEA-2000060

Dynamic: Your configuration is missing the required "{0}" property naming the concrete store manager to use to interact with your data store.

BEA-2000061

Dynamic: The options supplied to the {0} are not valid. Please check your ant build file.

BEA-2000062

Dynamic: java.util.Map

BEA-2000063

Dynamic: use a DataSource bound to JNDI

BEA-2000064

Dynamic: org.apache.openjpa.lib.remote.Transport

BEA-2000065

Dynamic: Cache.Queries

BEA-2000066

Dynamic: true

BEA-2000067

Dynamic: General

BEA-2000068

Dynamic: JDO.Remote

BEA-2000069

Dynamic: Your system is missing product derivations. Product derivations provide configuration options for supported data stores and specifications. You must have a META-INF/services/{0} file in your classpath listing the available derivation classes, and some listed class must be instantiable. Typically this file is bundled as part of the distribution. Have you unbundled it, or unbundled its listed classes?

BEA-2000070

Dynamic: General

BEA-2000071

Dynamic: Query compilation cache

BEA-2000072

Dynamic: 50

BEA-2000073

Dynamic: Attempt to configure for multiple specifications. Was configured for "{0}". Attempt to now configure for "{1}". This attempt will be ignored.

BEA-2000074

Dynamic: true

BEA-2000075

Dynamic: Remote persistence support

BEA-2000076

Dynamic: Plugin used to cache query compilation data. Must implement java.util.Map. Does not need to be thread-safe -- it will be wrapped via the Collections.synchronizedMap() method if it does not extend org.apache.openjpa.util.CacheMap.

BEA-2000077

Dynamic: 50

BEA-2000078

Dynamic: Define the remote persistence server.

BEA-2000079

Dynamic: Usage statistics for cache {0}: hits: {1}; misses: {2}; hit ratio: {3}

BEA-2000080

Dynamic: The cache "{0}" does not support per-class pinning.

BEA-2000081

Dynamic: Put key "{0}" into query cache.

BEA-2000082

Dynamic: This thread has been interrupted.

BEA-2000083

Dynamic: More than one of the data cache instances in the configuration string "{0}" are configured to be the default data cache. There must be one and only one cache whose name is "{1}", or whose name is not specified.

BEA-2000084

Dynamic: Query cache hit while removing key "{0}".

BEA-2000085

Dynamic: Unpinning key "{0}". Key is currently not in the cache.

BEA-2000086

Dynamic: Query cache miss while looking up key "{0}".

BEA-2000087

Dynamic: Put key "{0}" into cache.

BEA-2000088

Dynamic: Cannot invoke this method, as the cache has already been configured.

BEA-2000089

Dynamic: Cache schedule thread will check every "{0}" min.

BEA-2000090

Dynamic: This operation failed for some instances. See the nested exceptions array for details.

BEA-2000091

Dynamic: The token "{0}" is not in the valid range ({1}, {2}).

BEA-2000092

Dynamic: Cache removing class "{0}".

BEA-2000093

Dynamic: Token "{0}" is not a valid number or wildcard (*) for schedule.

BEA-2000094

Dynamic: Unable to register Datastore Cache {0} MBean.

BEA-2000095

Dynamic: Cache hit while removing key "{0}".

BEA-2000096

Dynamic: Pinning key "{0}". Key is currently in the cache.

BEA-2000097

Dynamic: Clearing query cache.

BEA-2000098

Dynamic: Query cache miss while looking up key "{0}". The key was in the cache, but the results have expired.

BEA-2000099

Dynamic: Query cache miss while removing key "{0}".

BEA-2000100

Dynamic: Invalid cache type "{0}". Allowed types are "distributed", "replicated", or "named".

BEA-2000101

Dynamic: Key "{0}" was expired from the cache.

BEA-2000102

Dynamic: Pinning key "{0}". Key is currently not in the cache.

BEA-2000103

Dynamic: Cache scheduler thread unexpectedly interrupted. Stopping scheduler.

BEA-2000104

Dynamic: Cache miss while looking up key "{0}".

BEA-2000105

Dynamic: OpenJPA Cache Scheduler

BEA-2000106

Dynamic: Query Cache

BEA-2000107

Dynamic: Cache miss while removing key "{0}".

BEA-2000108

Dynamic: Invalid schedule string: "{0}"

BEA-2000109

Dynamic: Invalid number of tokens in string "{0}" for cache schedule. There should be five tokens (minute, hour, dom, month, dow).

BEA-2000110

Dynamic: Stopping scheduled cache eviction thread.

BEA-2000111

Dynamic: None of the data cache instances in the configuration string "{0}" are configured to be the default data cache. There must be one and only one cache whose name is "{1}", or whose name is not specified.

BEA-2000112

Dynamic: Starting cache scheduler thread "{0}"...

BEA-2000113

Dynamic: The cache "{0}" does not supper per-class pinning. All pinned keys will be un-pinned.

BEA-2000114

Dynamic: Key "{0}" has expired from the query cache.

BEA-2000115

Dynamic: An exception was thrown while executing an expiration listener callback method. It was intercepted. The event framework consumes any exceptions that an ExpirationListener may throw.

BEA-2000116

Dynamic: Key "{0}" has been removed from the query cache.

BEA-2000117

Dynamic: Registered MBean ({0}).

BEA-2000118

Dynamic: Clearing datastore cache "{0}".

BEA-2000119

Dynamic: Query cache hit while looking up key "{0}".

BEA-2000120

Dynamic: The value corresponding to key "{0}" has timed out.

BEA-2000121

Dynamic: Deserialization error, unable to find class.

BEA-2000122

Dynamic: Scheduled cache eviction at time "{1}" for cache:"{0}"

BEA-2000123

Dynamic: This operation cannot be performed on this list, as the list has been closed.

BEA-2000124

Dynamic: Performing a commit on the cache. Adding {0}, updating {1} and {2}, and removing {3}.

BEA-2000125

Dynamic: The cache "{0}" does not support per-class pinning.

BEA-2000126

Dynamic: Unpinning key "{0}". Key is currently in the cache.

BEA-2000127

Dynamic: The datacache does not support automatic removal of subclasses.

BEA-2000128

Dynamic: Cache hit while looking up key "{0}".

BEA-2000129

Dynamic: This operation is not supported.

BEA-2000130

Dynamic: Could not perform automatic lookup of EJB container''s javax.transaction.TransactionManager implementation. Please ensure that you are running the application from within an EJB 1.1 compliant EJB container, and then set the org.apache.openjpa.ManagedRuntime property to the appropriate value to obtain the TransactionManager.

BEA-2000131

Dynamic: Expected object to be of type Reference, but instead was "{0}".

BEA-2000132

Dynamic: An IllegalAccessException occured when trying to obtain the serialVersionUID field for the class "{0}". This is a known bug in JDK 1.4+ when using a custom ClassLoader to enhance a class that implements java.io.Serializable. If compatibility with non-enhanced versions of "{0}" is not needed, this warning can be ignored.

BEA-2000133

Dynamic: Type "{0}" is already persistence capable; skipping.

BEA-2000134

Dynamic: Dynamic PCData created: name="{0}", for type="{1}"

BEA-2000135

Dynamic: Type "{0}" requires a public constructor to support detach on serialize. Making default constructor public.

BEA-2000136

Dynamic: Generating dynamic PCData for type: "{0}"

BEA-2000137

Dynamic: Enhancing type "{0}".

BEA-2000138

Dynamic: The type "{0}" must have a no-args constructor. Adding a {1} no-args constructor.

BEA-2000139

Dynamic: The member for for persistent property "{0}" was not a method: "{1}".

BEA-2000140

Dynamic: Type "{0}" does not declare an id class.

BEA-2000141

Dynamic: "{0}" requires runtime enhancement: {1}

BEA-2000142

Dynamic: Bytecode analysis of the setter and getter methods for persistent property "{0}" indicates that the two methods might be acting on different backing fields. The setter method assigns to field "{1}", while the getter method returns field "{2}".

BEA-2000143

Dynamic: Application identity class for: {0}

BEA-2000144

Dynamic: Attempt to run the application id tool under metadata configuration that does not support it. The application id tool can only run under certain metadata factory settings.

BEA-2000145

Dynamic: Usage: java org.apache.openjpa.enhance.ApplicationIdTool [-properties/-p ] [- ]* [-ignoreErrors/-i ]* [-directory/-d

] [-name/-n ] [-suffix/-s ] [-token/-t ] [-codeFormat/-cf. ]* +

BEA-2000146

Dynamic: Detected the following possible violations of the restrictions placed on property access persistent types: {0}

BEA-2000147

Dynamic: An error occurred trying to instantiate a custom storage class.

BEA-2000148

Dynamic: Type "{0}" does not have metadata, does not use application identity, or inherits the identity class from its superclass; skipping.

BEA-2000149

Dynamic: Auto-generated by:

BEA-2000150

Dynamic: The id type "{0}" specfied by persistent type "{1}" does not have a public string or class + string constructor.

BEA-2000151

Dynamic: The type "{0}" must have a no-args constructor.

BEA-2000152

Dynamic: Generating an application id for type "{0}".

BEA-2000153

Dynamic: Type "{0}" has no metadata; enhancing as persistence aware. If you intended for "{0}" to be persistence-capable, then this means that OpenJPA could not find any metadata for "{0}". This can happen if the directory containing your metadata is not in your CLASSPATH, or if your metadata files are not named properly. See the documentation on metadata placement for more information.

BEA-2000154

Dynamic: Type "{0}" is set to detach on serialize, but implements a custom readExternal and/or writeExternal method. You cannot use custom serialization with detachment.

BEA-2000155

Dynamic: The class does not have metadata - enhanced as persistence-aware.

BEA-2000156

Dynamic: No getter method found for persistent property "{0}". All persistent properties must have getter methods.

BEA-2000157

Dynamic: You have enabled runtime enhancement, but have not specified the set of persistent classes. OpenJPA must look for metadata for every loaded class, which might increase class load times significantly.

BEA-2000158

Dynamic: Writing application identity class to file "{0}".

BEA-2000159

Dynamic: When you supply the -name option, you must run the tool on exactly one class. Attempt to run on multiple classes: {0}

BEA-2000160

Dynamic: The class is already persistence capable - no enhancement performed.

BEA-2000161

Dynamic: An exception was thrown while attempting to perform class file transformation on "{0}":

BEA-2000162

Dynamic: No setter method found for persistent property "{0}", and bytecode analysis of the getter did not reveal a clear backing field. Please create a setter method for this property (it may be private).

BEA-2000163

Dynamic: Type "{0}" does not declare any primary key fields.

BEA-2000164

Dynamic: Application identity tool running on type "{0}".

BEA-2000165

Dynamic: The type "{0}" implements Cloneable but does not call super.clone (). Adding protected super.clone () invocation.

BEA-2000166

Dynamic: Type "{0}" is set to detach on serialize, but implements a custom readObject and/or writeObject method. You cannot use custom serialization with detachment.

BEA-2000167

Dynamic: No targets were given. Running on all classes listed in org.apache.openjpa.PersistentClasses, or all metadata files in classpath directories if the property is not specified.

BEA-2000168

Dynamic: Enhancer running on oid: {0}

BEA-2000169

Dynamic: Enhancing object id type "{0}" to allow member access.

BEA-2000170

Dynamic: Enhancer running on type "{0}".

BEA-2000171

Dynamic: "{1}" uses property access, but its field "{2}" is accessed directly in method "{3}" defined in "{0}".

BEA-2000172

Dynamic: Type "{0}" does not have metadata, does not use application identity, uses a built-in identity type, or inherits the identity class from its superclass.

BEA-2000173

Dynamic: No identity class was generated for this type.

BEA-2000174

Dynamic: Usage: java org.apache.openjpa.enhance.PCEnhancer [-properties/-p ] [- ]* [-directory/-d

] [-addDefaultConstructor/-adc ] [-jdoEnhance/-jdo ] [-enforcePropertyRestrictions/-epr ] [-tmpClassLoader/-tcl ] +

BEA-2000175

Dynamic: The statically initialized provider listener is null. This means that the provider startup failed.

BEA-2000176

Dynamic: Could not instantiate class {0}.

BEA-2000177

Dynamic: Sent JMS update to topic "{0}".

BEA-2000178

Dynamic: Still unable to send TCP update to "{0}".

BEA-2000179

Dynamic: Error when attempting to accept connection from remote host.

BEA-2000180

Dynamic: Attempting to reconnect after JMS failure on topic "{0}". Attempt number: {1}

BEA-2000181

Dynamic: Received notification of a JMS failure on topic "{0}".

BEA-2000182

Dynamic: Error closing connection for topic "{0}".

BEA-2000183

Dynamic: Error creating a publisher or subscriber for JMS topic "{0}". TopicConnectionFactory JNDI name: "{1}".

BEA-2000184

Dynamic: You have attempted to access the added object Ids for this event, however the RemoteCommitProvider isn't configured to send them. You need to either update your RemoteCommitEventListerner, or change your org.apache.openjpa.RemoteCommitProvider property so that it includes the option TransmitAddedObjectIds.

BEA-2000185

Dynamic: Stopped listening for remote commit information on topic "{0}".

BEA-2000186

Dynamic: Identified address of "{0}", which is equal to ourself.

BEA-2000187

Dynamic: The provider configuration for this TCPRemoteCommitProvider is not the same as for another provider in the current JVM that is listening on the same port. Port: "{0}".

BEA-2000188

Dynamic: You have attempted to access extent information for an event that only carries information as object Ids.

BEA-2000189

Dynamic: Started listening for remote commit information on port "{0}".

BEA-2000190

Dynamic: Error creating data to send to TCP provider.

BEA-2000191

Dynamic: Exception thrown while receiving TCP update.

BEA-2000192

Dynamic: Closing transmission connection to "{0}" that was using local port "{1}".

BEA-2000193

Dynamic: Successfully reconnected to JMS topic "{0}" after failure.

BEA-2000194

Dynamic: An exception occurred while configuring the TCPRemoteCommitProvider configured to listen on port "{0}".

BEA-2000195

Dynamic: Error sending TCP update to "{0}".

BEA-2000196

Dynamic: Received new connection from "{0}"

BEA-2000197

Dynamic: Detected possible orphaned reference to deleted object "{0}" in "{1}" of instance "{2}".

BEA-2000198

Dynamic: Exceptions were thrown while executing remote commit listener callback methods. They were consumed: {0}

BEA-2000199

Dynamic: Detected possible orphaned reference to deleted object "{0}" in "{1}".

BEA-2000200

Dynamic: Configured to send to peer "{0}"

BEA-2000201

Dynamic: You have attempted to use a RemoteCommitListener without also specifying a RemoteCommitProvider. In order to use a remote commit listener, you must configure a remote commit provider to use through the org.apache.openjpa.RemoteCommitProvider configuration property.

BEA-2000202

Dynamic: You have attempted to access object Ids for an event that only carries information as extents for the modified objects.

BEA-2000203

Dynamic: All attempts to reconnect to JMS topic "{0}" failed. Giving up after {1} attempts.

BEA-2000204

Dynamic: Exception thrown while closing connection from "{0}".

BEA-2000205

Dynamic: Started listening for remote commit information on topic "{0}".

BEA-2000206

Dynamic: Attempt to reconnect to JMS topic "{0}" failed.

BEA-2000207

Dynamic: Sent TCP update to "{0}" using local port "{1}".

BEA-2000208

Dynamic: Exception thrown while closing connection pool.

BEA-2000209

Dynamic: Received packet from "{0}" with invalid version number. Check if a prior release of OpenJPA is being used on this host.

BEA-2000210

Dynamic: Received event from peer "{0}"

BEA-2000211

Dynamic: Error broadcasting JMS update to topic "{0}". Remote BrokerFactories may be out-of-date.

BEA-2000212

Dynamic: Closing connection from "{0}".

BEA-2000213

Dynamic: Exception thrown while closing TCP remote commit provider.

BEA-2000214

Dynamic: Received an unexpected message type on topic "{0}". Message class: "{1}".

BEA-2000215

Dynamic: Received JMS update on topic "{0}".

BEA-2000216

Dynamic: Creating new socket connection to "{0}", using local port "{1}".

BEA-2000217

Dynamic: Received an unexpected object of type "{0}" on topic "{1}".

BEA-2000218

Dynamic: Stopped listening for remote commit information on port "{0}".

BEA-2000219

Dynamic: Exception thrown while setting NODELAY option for TCP remote commit provider.

BEA-2000220

Dynamic: JMSException thrown while retrieving object from an ObjectMessage.

BEA-2000221

Dynamic: Method "{1}" not found in class "{0}".

BEA-2000222

Dynamic: Received TCP update from "{0}".

BEA-2000223

Dynamic: The regular expression string "{0}" is invalid.

BEA-2000224

Dynamic: value of type {0}

BEA-2000225

Dynamic: The wildcard string "{0}" is invalid.

BEA-2000226

Dynamic: field {0} of type {1}

BEA-2000227

Dynamic: An error occurred while parsing the query filter "{1}". Error message: {0}

BEA-2000228

Dynamic: Subqueries are not supported for queries that execute in-memory. If you do not intend for this query to execute in-memory, consider setting IgnoreCache to true for the query.

BEA-2000229

Dynamic: The evaluation of the ordering expression of this query produced non-comparable values "{0}" and "{1}". Please check that the ordering clause is valid.

BEA-2000230

Dynamic: Filter invalid. Cannot compare {0} to {1}. Numeric comparisons must be between numeric types only. To enable such comparisons for backwards-compatibility, add "QuotedNumbersInQueries=true" to the org.apache.openjpa.Compatibility setting in your configuration.

BEA-2000231

Dynamic: If you use an aggregate function in a query filter, you must make sure to only invoke the aggregate on collections.

BEA-2000232

Dynamic: Cannot determine the type of field "{0}".

BEA-2000233

Dynamic: The variable "{0}" was found where a constant or field value was expected.

BEA-2000234

Dynamic: No "from" clause in expression.

BEA-2000235

Dynamic: Wrong number of arguments to expression of type "{1}": should have been {0}, but the following arguments were specified: "{2}".

BEA-2000236

Dynamic: Alias "{0}" was declared twice.

BEA-2000237

Dynamic: No field named "{1}" in class "{0}".

BEA-2000238

Dynamic: The JPQL string "{0}" is not valid. Make sure all parentheses are matched and that you use proper JPQL syntax.

BEA-2000239

Dynamic: The positional parameter "{0}" is invalid. Positional parameters must be integers greater than zero.

BEA-2000240

Dynamic: Expressions of type "{0}" are not yet supported.

BEA-2000241

Dynamic: The entity "{0}" cannot be resolved; please ensure that the entity name has been declared for the class.

BEA-2000242

Dynamic: Could not resolve result class named "{0}".

BEA-2000243

Dynamic: An error occurred while parsing the query filter ''{1}''. Error message: {0}

BEA-2000244

Dynamic: Unknown query operation "{0}".

BEA-2000245

Dynamic: Expression "{0}" does not allow mutliple children ("{1}").

BEA-2000246

Dynamic: The alias "{0}" was not declared in the statement (declared aliases are: {1}). All aliases must be declared in the "from" section of the JPQL statement.

BEA-2000247

Dynamic: The field named "{1}" in class "{0}" could not be accessed.

BEA-2000248

Dynamic: The specified node ("{0}") is not a valid identifier.

BEA-2000249

Dynamic: Could not resolve entity named "{0}".

BEA-2000250

Dynamic: Unknown comparison operator "{0}".

BEA-2000251

Dynamic: Attempt to query field "{0}" from non-entity class "{1}".

BEA-2000252

Dynamic: An alias is required for the schema name "{0}" in the expression.

BEA-2000253

Dynamic: The JPQL statement is not valid: encountered a node of type "{0}".

BEA-2000254

Dynamic: The name "{0}" is not a recognized entity or identifier.

BEA-2000255

Dynamic: Undeclared identifier "{0}".

BEA-2000256

Dynamic: Expression "{0}" requires at least one child.

BEA-2000257

Dynamic: JPQL does not support declared parameters.

BEA-2000258

Dynamic: Encountered "{0}" at character {1}, but expected: {2}.

BEA-2000259

Dynamic: Update expression "{0}" may only use literals or parameters as update values.

BEA-2000260

Dynamic: A savepoint with the name "{0}" already exists. Each savepoint name must be unique.

BEA-2000261

Dynamic: Attempt to construct a query from an extent or class. You must pass a (possibly null) query string or template to the query factory method when creating the query.

BEA-2000262

Dynamic: Executing query: [{0}] with parameters: {1}

BEA-2000263

Dynamic: Unable to execute a query on type "{0}". This class or interface is not mapped, and does not have any mapped implementors.

BEA-2000264

Dynamic: Some of the object ids passed to getObjectsById were null.

BEA-2000265

Dynamic: Cannot perform find using null object id.

BEA-2000266

Dynamic: Encountered unmanaged object "{0}" in persistent field "{1}" of managed object "{2}" during flush. However, this field does not allow cascade persist. You cannot flush unmanaged objects.

BEA-2000267

Dynamic: The file named "{0}" could not be found.

BEA-2000268

Dynamic: Parameter "{0}" was declared with a primtive type, but has been given a null value.

BEA-2000269

Dynamic: Could not invoke the static getInstance method on the named factory class "{0}".

BEA-2000270

Dynamic: To perform writes on persistent data outside of a transaction, the "NontransactionalWrite" property must be set to true.

BEA-2000271

Dynamic: The instance "{0}" has an unknown state manager which prevents field inspection.

BEA-2000272

Dynamic: The type "{0}" as used in the parameter declarations could not be found in the imports.

BEA-2000273

Dynamic: Detected attempt to modify field "{0}" with value strategy "restrict".

BEA-2000274

Dynamic: Query hint value "{0}" ({1}) cannot be converted into an aggregate listener.

BEA-2000275

Dynamic: Bulk update queries when executed in memory may only change the value of primitives and simple Object fields.

BEA-2000276

Dynamic: This broker is not configured to use managed transactions.

BEA-2000277

Dynamic: The factory has been closed. The stack trace at which the factory was closed is held in the embedded exception.

BEA-2000278

Dynamic: There was an error packing the projection and/or aggregate results of the query into result type "{0}". See the nested throwable for details.

BEA-2000279

Dynamic: The parameter name or position "{0}" passed to execute() is not valid. All map keys must be a declared parameter name or a number matching the parameter position.

BEA-2000280

Dynamic: This operation failed for some instances. See the nested exceptions array for details.

BEA-2000281

Dynamic: Attempt to change a primary key field of an instance that already has a final object id. Only new, unflushed instances whose id you have not retrieved can have their primary keys changed.

BEA-2000282

Dynamic: OpenJPA cannot provide the initial value for field "{0}" because the field was never loaded before being changed.

BEA-2000283

Dynamic: Attempted to attach deleted instance type "{0}" with oid "{1}". If the instance is new, the version field should be left to its default value.

BEA-2000284

Dynamic: Cannot convert object "{0}" of type "{1}" into an instance of "{2}".

BEA-2000285

Dynamic: The specified type "{0}" could not be loaded. Please ensure that the class exists in the project class path.

BEA-2000286

Dynamic: Attempt to set an embedded value for unembeddable field "{0}". Please report this error to OpenJPA support.

BEA-2000287

Dynamic: Attempt to persist detached object "{0}".

BEA-2000288

Dynamic: Queries of this type ("{0}") cannot be executed in-memory. Either set IgnoreCache to true, set the org.apache.openjpa.FlushBeforeQueries property to true, or execute the query before changing any instances in the transaction.

BEA-2000289

Dynamic: Attempt to cast instance "{0}" to PersistenceCapable failed. Ensure that it has been enhanced.

BEA-2000290

Dynamic: The class "{0}" does not declare the "detachable" metadata extension, so cannot be detached.

BEA-2000291

Dynamic: You are attempting to access an embedded object reference that was obtained before the last transaction status change. After transactions begin and end, all references to embedded objects become invalid; you have to re-acquire the reference from the owning persistent object.

BEA-2000292

Dynamic: Cannot create an instance of "{0}": abstract classes and interfaces are not yet supported.

BEA-2000293

Dynamic: This operation is illegal when called during transaction completion.

BEA-2000294

Dynamic: The query cannot be executed because it has no valid expressions.

BEA-2000295

Dynamic: You cannot make a property access object created with "new" nontransactional.

BEA-2000296

Dynamic: Method "{0}" named in the org.apache.openjpa.MethodQL query must be static.

BEA-2000297

Dynamic: You are attempting to directly mutate a persistent second class object (such as a collection or map field) that you obtained before the transaction began. After beginning a datastore transaction, you must re-obtain any references to mutable second class objects from the owning persistent object. Detected attmpt to mutate value of field "{0}" in instance "{1}". This instance may not be locked correctly.

BEA-2000298

Dynamic: The given value "{0}" cannot be converted into an identity for "{2}". The value is the wrong type ({1}).

BEA-2000299

Dynamic: To perform this operation, you must be withing a transaction, or your settings must allow nontransactional writes and must not detach all nontransactional reads.

BEA-2000300

Dynamic: An error occured processing callbacks for instance of type "{0}".

BEA-2000301

Dynamic: An exception occurred while ending the transaction. This exception will be re-thrown.

BEA-2000302

Dynamic: Detected reentrant flush. Make sure your flush-time instance callback methods or event listeners do not invoke any operations that require the in-progress flush to complete.

BEA-2000303

Dynamic: This query on candidate type "{0}" with filter "{1}" involves combining the results of multiple queries in memory. You have chosen to order the results on "{2}", but you have not selected this data in your setResult() clause. Please include this ordering data in setResult() so that OpenJPA can extract it for in-memory ordering.

BEA-2000304

Dynamic: This lock manager does not recognize lock level "{0}".

BEA-2000305

Dynamic: Queries that have been serialized do not support this operation.

BEA-2000306

Dynamic: Attempt to initialize a state manager with a null persistence-capable instance for type "{0}". This is often caused by attempting to load an instance of an abstract class, or neglecting to use a class indicator when the base persistence-capable class in an inheritance tree is abstract.

BEA-2000307

Dynamic: More parameters were passed to execute() than were declared: {1} parameters were specified for query execution, but only {0} parameters were declared in the query.

BEA-2000308

Dynamic: Encountered unknown dependent instance "{0}". This error is often caused by either removing a dependent instance from one dependent field, but not other dependent fields that reference it, or by removing a dependent instance from its owning field, flushing (causing the unreferenced dependent instance to be deleted), and then trying to assign the deleted instance to another field before commit. The instance cannot be un-deleted, resulting in an error. Make sure not to leave dangling dependent references to objects, and to reassign dependent objects before flush so that OpenJPA does not think they are unreferenced and therefore safe to delete.

BEA-2000309

Dynamic: There was an error creating an instance of type "{0}" when packing the projection and/or aggregate results of the query. Ensure that you have defined a public no-args constructor in "{0}".

BEA-2000310

Dynamic: This query on type "{0}" must load the entire candidate class extent and evaluate the query in-memory. This may be very slow. The query must be executed in memory because OpenJPA is configured with IgnoreCache=false and FlushBeforeQueries=false and there are dirty instances that may affect the query''s outcome in the cache.

BEA-2000311

Dynamic: The context has been closed. The stack trace at which the context was closed is held in the embedded exception.

BEA-2000312

Dynamic: Released lock "{0}".

BEA-2000313

Dynamic: A candidate Class must be specified before executing a query.

BEA-2000314

Dynamic: Queries with aggregates or projections using variables currently cannot be executed in-memory. Either set IgnoreCache to true, set the org.apache.openjpa.FlushBeforeQueries property to true, or execute the query before changing any instances in the transaction. The offending query was on type "{0}" with filter "{1}".

BEA-2000315

Dynamic: Attempt to add null/empty field name to fetch configuration.

BEA-2000316

Dynamic: A query that declares unique results cannot be used to perform bulk updates.

BEA-2000317

Dynamic: The RestoreValues option is off, so initial values are not available. Turn on RestoreValues to be able to obtain initial values.

BEA-2000318

Dynamic: This query on candidate type "{0}" with filter "{1}" involves combining the results of multiple sub-queries. However, because this query is for aggregate data, OpenJPA cannot combine the sub-query aggregates into correct final values.

BEA-2000319

Dynamic: Could not invoke the static newInstance method on the named factory class "{0}".

BEA-2000320

Dynamic: You have modified the object id field of "{2}". Its old value was "{0}", and its new value is "{1}". Object id fields are immutable once the object id of the instance has been assigned.

BEA-2000321

Dynamic: This operation cannot be performed while a Transaction is active.

BEA-2000322

Dynamic: Attempt to initialize a state manager with an instance that is already managed ("{0}"). You might be trying to persist this instance in two threads at the same time.

BEA-2000323

Dynamic: Method "{0}(StoreContext, ClassMetaData, boolean, Map, FetchConfiguration)" is not declared in type "{1}". Check the method name supplied in your org.apache.openjpa.MethodQL query filter. OpenJPA is attempting to execute this query against the datastore; if you implemented the in-memory method instead (a method with the same signature but with an Object argument) and want this query to execute in-memory, supplly a Collection of candidates to filter.

BEA-2000324

Dynamic: Attempt to add null/empty fetch group name to fetch configuration.

BEA-2000325

Dynamic: Illegal operation attempted on a newly persisted instance: new objects cannot be evicted or made transient or non-transactional.

BEA-2000326

Dynamic: You must set the query filter to the name of the method to execute for this org.apache.openjpa.MethodQL query instance.

BEA-2000327

Dynamic: A query that declares a result range cannot be used to perform bulk updates.

BEA-2000328

Dynamic: The query on candidate type "{0}" with filter "{1}" was configured to have a unique result, but more than one instance matched the query.

BEA-2000329

Dynamic: The RestoreValues option is not set to "all", initial values of mutable fields are not available. Set RestoreValues to "all" in your properties to be able to obtain initial mutable values.

BEA-2000330

Dynamic: Invoking the setter for hint key "{0}" on "{1}" with value "{2}" caused an error.

BEA-2000331

Dynamic: Cannot access the detached object id of class "{0}". Ensure that the class has the "detachable" metadata extension, and the class has been re-enhanced.

BEA-2000332

Dynamic: The field "{0}" of instance "{1}" contained a null value; the metadata for this field specifies that nulls are illegal.

BEA-2000333

Dynamic: Cannot instantiate abstract class of type "{0}" with object id "{1}"; this may indicate that the inheritance discriminator for the class is not configured correctly.

BEA-2000334

Dynamic: A query that declares a result class cannot be used to perform bulk updates.

BEA-2000335

Dynamic: The instance "{0}" is managed by another context and cannot be inspected for field values.

BEA-2000336

Dynamic: The object "{0}" with id "{1}" has been deleted and cannot be attached.

BEA-2000337

Dynamic: Attempt to assign id "{0}" to new instance "{1}" failed; there is already an object in the L1 cache with this id. You must delete this object (in a previous transaction or the current one) before reusing its id. This error can also occur when a horizontally or vertically mapped classes uses auto-increment application identity and does not use a hierarchy of application identity classes.

BEA-2000338

Dynamic: Attempted to attach instance "{0}" of type "{1}", but this instance is already in the datastore as type "{2}".

BEA-2000339

Dynamic: Attempt to modify a read-only query object.

BEA-2000340

Dynamic: Operation attempted on a deleted instance.

BEA-2000341

Dynamic: You cannot perform operation {0} on detached object "{1}". This operation only applies to managed objects.

BEA-2000342

Dynamic: Acquired an exclusive lock on oid "{0}": "{1}".

BEA-2000343

Dynamic: A NamingException was thrown while obtaining the factory at "{0}" from JNDI.

BEA-2000344

Dynamic: You cannot use the modulo operator (%) on numbers of type BigDecimal.

BEA-2000345

Dynamic: You cannot refresh an instance that has been flushed to the data store.

BEA-2000346

Dynamic: Unable to copy field "{0}" for savepoint.

BEA-2000347

Dynamic: An inverse inconsistency in the object model was detected while flushing the field "{0}" of the instance with id "{1}" in context "{2}".

BEA-2000348

Dynamic: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred.

BEA-2000349

Dynamic: Encountered deleted object "{0}" in persistent field "{1}" of managed object "{2}" during flush.

BEA-2000350

Dynamic: Query projections cannot include array, collection, or map fields. Invalid query: "{0}"

BEA-2000351

Dynamic: Query hint value "{0}" ({1}) cannot be converted into a filter listener.

BEA-2000352

Dynamic: Attempt to access an unloaded field of detached instance "{0}".

BEA-2000353

Dynamic: Cannot manipulate identity of type "{0}": it''s identity type is unknown.

BEA-2000354

Dynamic: You cannot assign managed object "{0}" to the primary key field of "{1}". Embedded primary key values must be transient objects.

BEA-2000355

Dynamic: Method "{0}(StoreContext, ClassMetaData, boolean, Object, Map, FetchConfiguration)" is not declared in type "{1}". Check the method name supplied in your MethodQL query filter. OpenJPA is attempting to execute this query in-memory; if you implemented the datastore method instead (a method with the same signature but without the Object argument) and want this query to execute in the datastore, either make the query before modifying objects in the current transaction, set IgnoreCache to true, or set the openjpa.FlushBeforeQueries property to true.

BEA-2000356

Dynamic: The "{0}" transaction property cannot be set during an active transaction.

BEA-2000357

Dynamic: This savepoint has already been initialized.

BEA-2000358

Dynamic: The named BrokerFactory "{0}" is not valid.

BEA-2000359

Dynamic: The given instance "{0}" is not managed by this context.

BEA-2000360

Dynamic: Attempt to commit a null javax.transaction.Transaction. Some application servers set the transaction to null if a rollback occurs.

BEA-2000361

Dynamic: Cannot load object with id "{0}". Instance "{1}" with the same id already exists in the L1 cache. This can occur when you assign an existing id to a new instance, and before flushing attempt to load the existing instance for that id.

BEA-2000362

Dynamic: Result type "{0}" does not have any public fields or setter methods for the projection or aggregate result element "{1}", nor does it have a generic put(Object,Object) method that can be used, nor does it have a public constructor that takes the types {2}.

BEA-2000363

Dynamic: Invoking the getter for hint key "{0}" on "{1}" caused an error.

BEA-2000364

Dynamic: There was an error when invoking the static newInstance method on the named factory class "{0}". See the nested exception for details.

BEA-2000365

Dynamic: The range of the query is too big. Start index: "{0}", end index: "{1}". The range must be less than Integer.MAX_VALUE.

BEA-2000366

Dynamic: There was an error invoking method "{0}" with arguments "{1}".

BEA-2000367

Dynamic: "{0}" is not the index of any managed field in "{1}".

BEA-2000368

Dynamic: This datastore does not support optimistic transactions. Set the Optimistic property to false.

BEA-2000369

Dynamic: The query range from {0} to {1} is not valid.

BEA-2000370

Dynamic: Can only perform operation while a transaction is active.

BEA-2000371

Dynamic: You have not set a savepoint with the name "{0}"

BEA-2000372

Dynamic: Illegal operation attempted on a dirty instance: dirty objects cannot be evicted or made transient or non-transactional.

BEA-2000373

Dynamic: Cannot create new application identity instance for abstract class "{0}".

BEA-2000374

Dynamic: Illegal operation attempted on a transient instance.

BEA-2000375

Dynamic: There was an error when invoking the static getInstance method on the named factory class "{0}". See the nested exception for details.

BEA-2000376

Dynamic: This data store does not support nontransactional reads. Set the NontransactionalRead property to false.

BEA-2000377

Dynamic: Starting OpenJPA {0}

BEA-2000378

Dynamic: The "{0}" query type does not support this operation.

BEA-2000379

Dynamic: Properties: {0}

BEA-2000380

Dynamic: To perform reads on persistent data outside of a transaction, the "NontransactionalRead" property must be set on the Transaction.

BEA-2000381

Dynamic: Encountered new object "{0}" in persistent field "{1}" of managed object "{2}" during attach. However, this field does not allow cascade attach. You cannot attach a reference to a new object without cascading.

BEA-2000382

Dynamic: This data store cannot return connections.

BEA-2000383

Dynamic: Encountered object "{0}" without a version field during attach. In order to attach an object, it must either be enhanced or must have a version field.

BEA-2000384

Dynamic: Field "{0}" is not declared in "{1}", or is not managed.

BEA-2000385

Dynamic: The transaction cannot be committed, because it was already marked for rollback only. The transaction will be rolled back instead.

BEA-2000386

Dynamic: You did not name the factory class with the required property org.apache.openjpa.BrokerFactory.

BEA-2000387

Dynamic: Cannot execute query; some declared parameters were not given values. You must supply a value for each of the following parameters, in the given order: {0}

BEA-2000388

Dynamic: The configured SavepointManager does not support incremental flushing when a savepoint has been set. You must release your savepoints before flushing.

BEA-2000389

Dynamic: Cannot rollback/release last savepoint as no savepoint has been set.

BEA-2000390

Dynamic: The {1} declaration "{0}" is not valid. Variables and imports must be delimited with ";". Parameters and orderings must be delimited with ",". Imports require the "import" keyword, and orderings require the "ascending" or "descending" keyword.

BEA-2000391

Dynamic: There is no conversion between query projection type "{0}" and result type "{1}".

BEA-2000392

Dynamic: Attempt to copy field "{0}" failed. The field is not copyable. This can occur with custom SCO types or with large result set fields. Only standard or immutable SCO types can be attached and detached.

BEA-2000393

Dynamic: Cannot execute query; the declared parameter "{0}" was not given a value.

BEA-2000394

Dynamic: An object of type "{0}" with oid "{1}" already exists in this context; another cannot be persisted.

BEA-2000395

Dynamic: The instance of type "{0}" with oid "{1}" no longer exists in the data store. This may mean that you deleted the instance in a separate transaction, but this context still has a cached version.

BEA-2000396

Dynamic: The type "{0}" declares datastore identity but the value passed to lookup of type "{1}" is not a OpenJPA id instance.

BEA-2000397

Dynamic: You set the method name of this openjpa.MethodQL query to "{1}", but class "{0}" is not a valid class name. Make sure to fully qualify the class name or to import its package into this query if the class is not in the query candidate class'' package.

BEA-2000398

Dynamic: Executing query: {0}

BEA-2000399

Dynamic: This data store does not support incremental flushing. If you got this error while performing a query, make sure that you have not set the FlushBeforeQueries option to true, either by setting that option in your configuration file, or by programmatically setting the current FetchConfiguration''s FlushBeforeQueries property to QueryFlushModes.FLUSH_TRUE.

BEA-2000400

Dynamic: Type "{0}" and its persistent superclass "{1}" declare different access types. All persistent classes in an inheritance hierarchy must use the same access type (field vs. property access).

BEA-2000401

Dynamic: Concrete type "{0}" with application identity does not declare any primary key fields.

BEA-2000402

Dynamic: A potentially serious error occurred while processing registered class "{0}". Deferring processing of this class until next opportunity.

BEA-2000403

Dynamic: The metadata for some of the following classes may not have been dropped: {0}

BEA-2000404

Dynamic: Field "{0}" is not a type that is persistent by default. If you want this field to be persistent, you have to explicitly set it to persistent in your metadata.

BEA-2000405

Dynamic: Array fields do not support large result sets. Remove the "lrs" extension from field "{0}".

BEA-2000406

Dynamic: Generating default metadata for type "{0}".

BEA-2000407

Dynamic: Type "{0}" is an interface and therefore cannot be made persistent.

BEA-2000408

Dynamic: There was an error invoking the factory for field "{0}" on datastore value "{1}": {2}

BEA-2000409

Dynamic: Field "{0}" is named as the detach state field in type "{1}", but is a managed field. Detach state fields cannot be managed.

BEA-2000410

Dynamic: Attempt to add an unnamed fetch group to "{0}".

BEA-2000411

Dynamic: "{0}" declares a read only value of "{1}". This is not a recognized strategy. Available strategies are: {2}

BEA-2000412

Dynamic: The identity class specified by type "{0}" is not valid, as the hashCode method is not overridden. Implement hashCode so that two instances with the same primary key values have the same hash code.

BEA-2000413

Dynamic: The extension key "{1}" for "{0}" is not recognized and will be ignored, although the name closely matches the valid key "{3}". Valid extension keys are "{2}".

BEA-2000414

Dynamic: Could not locate metadata for the class using alias "{0}". Registered alias mappings: "{1}"

BEA-2000415

Dynamic: Attempt to include non-existent fetch group "{1}" in fetch group "{0}".

BEA-2000416

Dynamic: The map value type of field "{0}" a derived key must be a persistent class with exactly one primary key field.

BEA-2000417

Dynamic: Your configured MetaDataIO cannot create metadata. You must create it by hand.

BEA-2000418

Dynamic: Metadata tool running on type "{0}" with action "{1}".

BEA-2000419

Dynamic: The class name "{0}" used in a metadata extension on field "{1}" is not valid.

BEA-2000420

Dynamic: The class "{0}" listed in the openjpa.MetaDataFactory configuration property could not be loaded; ignoring.

BEA-2000421

Dynamic: Type "{0}" with application identity and no superclass does not declare an id class. This type is not eligible for builtin identity, so it must declare an id class.

BEA-2000422

Dynamic: Field "{0}" attempts to recursively embed its declaring type.

BEA-2000423

Dynamic: Large result set fields must be of type java.util.Collection or java.util.Map. No concrete classes or other interfaces are allowed. Remove the "lrs" extension from field "{0}" or change it to one of these types.

BEA-2000424

Dynamic: An invalid null external-value was declared for field "{0}".

BEA-2000425

Dynamic: The identity class specified by type "{0}" is not valid, as the equals method is not overridden. Implement the equals method so that two two instances will compare equal if and only if they have the same primary key values.

BEA-2000426

Dynamic: Field "{0}" is marked as embedded, but the store manager in use cannot embed first-class object fields. Treating as non-embedded.

BEA-2000427

Dynamic: Superclass field "{0}" is mapped in the metadata for subclass "{1}", but is not a persistent field.

BEA-2000428

Dynamic: Field "{0}" declares a logical inverse of "{1}", but that is a not a field of the related type.

BEA-2000429

Dynamic: Initializing mapping for "{0}".

BEA-2000430

Dynamic: Attempt to include fetch group "{1}" in fetch group "{0}" creates an inclusion cycle.

BEA-2000431

Dynamic: The data store does not support application identity. Alter "{0}" to use datastore identity.

BEA-2000432

Dynamic: An error occurred while processing registered class "{0}".

BEA-2000433

Dynamic: Type "{0}" uses application identity; it cannot also declare a datastore identity strategy.

BEA-2000434

Dynamic: Field "{0}" named as the detach state field for type "{1}" does not exist.

BEA-2000435

Dynamic: Field "{0}", named as the detach state field for type "{1}", must be of type Object.

BEA-2000436

Dynamic: The map value type of field "{0}" with a derived key must be a persistent class.

BEA-2000437

Dynamic: Named sequence "{0}" declares an invalid class "{1}".

BEA-2000438

Dynamic: "{0}" declared that it is mapped by "{1}", but that is a not a field of the related type.

BEA-2000439

Dynamic: Type "{0}" declares a detach object id field, but uses application identity. Detach object id fields are only used for datastore identity classes.

BEA-2000440

Dynamic: Field "{0}" cannot be ordered. Ordering is only supported for collection and array fields.

BEA-2000441

Dynamic: Resolving field "{0}".

BEA-2000442

Dynamic: Fetch group "{0}" specifies invalid recursion depth "{2}" for field "{1}". Recursion depth must be greater than or equal to -1.

BEA-2000443

Dynamic: Could add the following callback adapters to "{0}", as the lifecycle metadata is already resolved: {1}

BEA-2000444

Dynamic: No method was found for the persistent property "{0}" declared in "{1}" or one of its superclasses. Searched for methods called "{2}" and "{3}".

BEA-2000445

Dynamic: Field "{0}" cannot be a primary key. Primary key fields can only be declared in base persistent classes that also declare their identity-type to be "application".

BEA-2000446

Dynamic: jdbc-

BEA-2000447

Dynamic: "{0}" declares that it is mapped by "{1}", but that field also declares that it is mapped by another. Only one side of a relation can declare that it is mapped by another field.

BEA-2000448

Dynamic: Field "{0}", named as the detach object id field for type "{1}", must be of type String.

BEA-2000449

Dynamic: The id class specified by type "{0}" does not match the primary key fields of the class. Make sure your identity class has the same primary keys as your persistent type, that the access types are the same, and if you are getting this error at runtime, that you have your persistent class since last compiling your identity class.

BEA-2000450

Dynamic: No metadata was found for type "{0}". The class does not appear in the list of persistent types: {1}.

BEA-2000451

Dynamic: Guessing persistence-capable class name for identity class "{0}".

BEA-2000452

Dynamic: Field "{0}" is marked as embedded, but OpenJPA is unable to embed the field. OpenJPA cannot embed first-class object fields produced through an externalizer. Treating as non-embedded.

BEA-2000453

Dynamic: Errors encountered while resolving metadata. See nested exceptions for details.

BEA-2000454

Dynamic: There was an error instantiating named sequence "{0}".

BEA-2000455

Dynamic: Resolving embedded metadata for "{0}".

BEA-2000456

Dynamic: Preparing mapping for "{0}".

BEA-2000457

Dynamic: No metadata was found for type "{0}". The class is not enhanced.

BEA-2000458

Dynamic: Clearing metadata repository "{0}".

BEA-2000459

Dynamic: Unable to resolve type "{0}" due to previous errors resolving related type "{1}".

BEA-2000460

Dynamic: Externalized fields do not support large result sets. Remove the "lrs" extension from field "{0}".

BEA-2000461

Dynamic: Processing registered persistence-capable class "{0}".

BEA-2000462

Dynamic: Field "{0}" cannot be a primary key. It is of an unsupported type.

BEA-2000463

Dynamic: Usage: java org.apache.openjpa.meta.MetaDataTool [-properties/-p ] [- ]* [-verbose/-v ] [-file/-f ] [-action/-a ] +

BEA-2000464

Dynamic: The factory method supplied for field "{0}" does not exist or is not a valid constructor or method. If the factory is a method of the owning class and not the field type, make sure you have declared the method in the form ".". Also, make sure the specified factory method is static.

BEA-2000465

Dynamic: No metadata was found for type "{0}". Ensure that the class is enhanced (if necessary), that the class has appropriate metadata, and that if you list your persistent classes, the class is included in your list.

BEA-2000466

Dynamic: Type "{0}" is an enumeration and therefore cannot be made persistent.

BEA-2000467

Dynamic: No method was found for the persistent property "{0}" declared in "{1}" or one of its superclasses. Searched for a method called "{2}".

BEA-2000468

Dynamic: The metadata for "{0}" sets its value or identity strategy to sequence, but does not name the sequence to use.

BEA-2000469

Dynamic: Loading mapping for "{0}" under mode "{1}".

BEA-2000470

Dynamic: Could not locate the sequence with name "{0}". It is possible that the metadata file containing the sequence has not been parsed yet. Make sure to use a persistent class whose metadata is in the same file somewhere in your application before requesting the sequence.

BEA-2000471

Dynamic: The externalizer method "{1}" on field "{0}" is not valid. If this is a method of the owning class type and not the field type, make sure you have declared the method in the form ".", and that the method is static.

BEA-2000472

Dynamic: The ClassMetaData access type must be set to either ClassMetaData.ACCESS_FIELD or ClassMetaData.ACCESS_PROPERTY. Attempt to set it to "{0}" failed.

BEA-2000473

Dynamic: Type "{0}" declares an id class "{1}" that does not match or extend its persistent superclass "{2}" identity class "{3}".

BEA-2000474

Dynamic: The field "{0}" cannot use the external-values property. External values can only be declared for fields of primitives, primitive wrappers, or strings.

BEA-2000475

Dynamic: Type "{0}" declares field "{1}" as a primary key, but keys of type "{2}" are not supported.

BEA-2000476

Dynamic: Field "{0}" uses an invalid combination of in-memory and datastore ordering for its values. If a combination is used, all in-memory orderings must appear in the ordering declaration before datastore orderings.

BEA-2000477

Dynamic: Recording metadata changes.

BEA-2000478

Dynamic: "{0}" declares an unsupported strategy of "{1}" for its {2}.

BEA-2000479

Dynamic: Type "{0}" declares an invalid data-cache-timeout value. Valid timeout values are -1 (to disable timeouts), or positive integers. Timeout was set to {1}.

BEA-2000480

Dynamic: Resolving mapping for "{0}".

BEA-2000481

Dynamic: There was an error invoking the externalizer for field "{0}" on Java value "{1}": {2}

BEA-2000482

Dynamic: The field "{0}" cannot declare both an externalizer method and external values.

BEA-2000483

Dynamic: Type "{0}" declares a detach object id field, but is not the least-derived detachable class in the inheritance tree. Only the least-derived detachable class can name the detach object id and state fields.

BEA-2000484

Dynamic: Type "{0}" is mapped to the data store, but does not have an identity type. Alter its metadata to declare datastore identity or to have at least one primary key field.

BEA-2000485

Dynamic: You cannot declare that "{0}" is mapped by another field. Only direct field values and map keys can be mapped by another field.

BEA-2000486

Dynamic: Type "{0}" declares a cache name of "{1}", but its persistent superclass "{2}" uses a different cache name ("{3}").

BEA-2000487

Dynamic: Could not locate metadata for the class using oid "{0}" of type "{1}". Registered oid type mappings: "{2}"

BEA-2000488

Dynamic: The field "{0}" declares an external-values property but does not declare any values in the string: "{1}".

BEA-2000489

Dynamic: Type "{0}" declares a detach state field, but is not the least-derived detachable class in the inheritance tree. Only the least-derived detachable class can name the detach object id and state fields.

BEA-2000490

Dynamic: Type "{0}" has multiple version fields: [{1}, {2}]

BEA-2000491

Dynamic: "{0}" declares an identity or value strategy of "{1}". This is not a recognized strategy, though it closely resembles the standard strategy "{2}". Available strategies are: {3}

BEA-2000492

Dynamic: Cannot order "{0}" on "{1}", because {0} is not a relation to another persistent type. For non-relation fields, you can only order on the field element values themselves, represented by "#element".

BEA-2000493

Dynamic: The data store does not support datastore identity. Alter "{0}" to use application identity.

BEA-2000494

Dynamic: Cannot order "{0}" on "{1}", because that is not a persistent field in the related type.

BEA-2000495

Dynamic: The type "{0}" has not been enhanced.

BEA-2000496

Dynamic: Field "{0}" named as the detach object id field for type "{1}" does not exist.

BEA-2000497

Dynamic: Field "{0}" is marked as having an embedded element or value type, but the store manager in use cannot embed collection/map elements. Treating as non-embedded.

BEA-2000498

Dynamic: There is no named query defined for the class "{0}" with the name "{1}".

BEA-2000499

Dynamic: Field "{0}" declares that it is mapped by a field that is different from its logical inverse field. You do not need to name the logical inverse if you''ve already declared that the field is mapped by another, but if you do, then the logical inverse must point to the mapping field.

BEA-2000500

Dynamic: Loading metadata for "{0}" under mode "{1}".

BEA-2000501

Dynamic: The extension key "{1}" for "{0}" is not recognized and will be ignored. Valid extension keys are "{2}".

BEA-2000502

Dynamic: Field "{0}" is marked as having an embedded key type, but the store manager in use cannot embed map keys. Treating as non-embedded.

BEA-2000503

Dynamic: The id class specified by type "{0}" does not have public a no-args constructor.

BEA-2000504

Dynamic: Resolving metadata for "{0}".

BEA-2000505

Dynamic: Type "{0}" attempts to use both field and property access. Only one access method is permitted.

BEA-2000506

Dynamic: Set persistence-capable superclass of "{0}" to "{1}".

BEA-2000507

Dynamic: "{0}" declares an identity or value strategy of "{1}". This is not a recognized strategy. Available strategies are: {2}

BEA-2000508

Dynamic: The data store does not support fields of type {0}.

BEA-2000509

Dynamic: Using reflection for metadata generation.

BEA-2000510

Dynamic: Field "{0}" is named as the detach object id field in type "{1}", but is a managed field. Detach object id fields cannot be managed.

BEA-2000511

Dynamic: Type "{0}" does not declare the same identity-type as its persistent superclass.

BEA-2000512

Dynamic: No field was found for the persistent property "{0}" declared in "{1}" or one of its superclasses.

BEA-2000513

Dynamic: Found {0} classes with metadata in {1} milliseconds.

BEA-2000514

Dynamic: Attempt to add fetch group "{0}" to type field "{1}" failed. This fetch group has not been defined.

BEA-2000515

Dynamic: "{0}" declares a read only value of "{1}". This is not a recognized strategy, though it closely resembles the standard strategy "{2}". Available strategies are: {3}

BEA-2000516

Dynamic: A unique constraint violation has occurred.

BEA-2000517

Dynamic: Missing getter for property "{1}" in type "{0}".

BEA-2000518

Dynamic: Unable to create second class object proxy for type: "{0}".

BEA-2000519

Dynamic: Encountered object id "{0}" in serialized data, but the corresponding persistent object no longer exists. Substituting null into the deserialization stream.

BEA-2000520

Dynamic: Could not obtain a lock on object "{0}" in {1} milliseconds.

BEA-2000521

Dynamic: The instance "{0}" cannot be persisted, because it conflicts with an existing instance.

BEA-2000522

Dynamic: No store-specific facade found matching "{0}". Using default.

BEA-2000523

Dynamic: A duplicate object id exception has occurred. Each object you insert into the data store must have unique primary key field values.

BEA-2000524

Dynamic: The given type "{0}" does not use single field identity.

BEA-2000525

Dynamic: While creating datastore identity for "{0}", unknown id value "{1}" of type "{2}" encountered. Cannot convert to org.apache.openjpa.util.Id.

BEA-2000526

Dynamic: Nested:

BEA-2000527

Dynamic: An exception was thrown while creating a new instance of custom proxy collection type "{0}". This could mean that there is no public no-args constructor for this type.

BEA-2000528

Dynamic: Bad single primary key field "{0}"

BEA-2000529

Dynamic: The follwing instnaces do not exist in the data store: {0}

BEA-2000530

Dynamic: A referential integrity constraint has occurred.

BEA-2000531

Dynamic: The instance "{0}" does not exist in the data store.

BEA-2000532

Dynamic: The given element does not meet the requirements for this field. The container requires that all non-null objects are of the type declared in the XML metadata for this container. "{1}(loader={0}).isAssignableFrom ({3}(loader={2}))" failed.

BEA-2000533

Dynamic: You cannot transfer large result set fields from one object or field to another.

BEA-2000534

Dynamic: Missing setter for property "{1}" in type "{0}".

BEA-2000535

Dynamic: An optimistic lock violation was detected when flushing object instance "{0}" to the data store. This indicates that the object was concurrently modified in another transaction.

BEA-2000536

Dynamic: Unable to copy array: {0}.

BEA-2000537

Dynamic: An invalid key was found in a CacheMap while flushing data from it. CacheMap: "{0}". Key: "{1}". All unpinned objects were cleared from the CacheMap in order to re-establish a consistent cache.

BEA-2000538

Dynamic: Optimistic locking errors were detected when flushing to the data store. The following objects may have been concurrently modified in another transaction: {0}

BEA-2000539

Dynamic: Invalid single identity declaration for type "{0}". Only a single field can be declared for single field identity.

BEA-2000540

Dynamic: Unable to obtain an object lock on "{0}".

BEA-2000541

Dynamic: Optimistic locking errors were detected when flushing to the data store. This indicates that some objects were concurrently modified in another transaction. Each exception in the nested throwables array contains a failed object representing a concurrently modified object.

BEA-2000542

Dynamic: Failed:

BEA-2000543

Dynamic: Null id value encountered while creating datastore identity for "{0}".

BEA-2000544

Dynamic: Unable to create a valid id from string "{0}".

BEA-2000545

Dynamic: No filesets specified.

BEA-2000546

Dynamic: An exception occurred while invoking close() on "{0}". This exception will be consumed.

BEA-2000547

Dynamic: Instantiation of plugin "{0}" with value "{1}" caused an error "{2}". The alias or class name may have been misspelled (as it closely matches the valid plugin alias "{4}"), or the class may not be available in the class path. Valid aliases for this plugin are: {3}

BEA-2000548

Dynamic: An instance of the class "{0}" could not be instantiated. Make sure the class has a public no-args constructor.

BEA-2000549

Dynamic: The configuration is read only; it cannot be modified.

BEA-2000550

Dynamic: There was an error while setting up the configuration option "{0}", and it was set to "{1}". All possible values for this setting are: {2}.

BEA-2000551

Dynamic: The property named "{0}" was not recognized and will be ignored.

BEA-2000552

Dynamic: Errors occurred while creating property descriptors for the following properties: {0}.

BEA-2000553

Dynamic: Configuration information loaded via "{0}".

BEA-2000554

Dynamic: You cannot set the value of property "{0}" as an object. The property cannot use a single value; it must be recreated on each request.

BEA-2000555

Dynamic: An exception occurred while creating a plugin for value {0}. This exception will be consumed.

BEA-2000556

Dynamic: There was an error duing JNDI lookup of the name "{0}".

BEA-2000557

Dynamic: An exception occurred while invoking afterConfigurationLoad() on "{0}". This exception will be consumed.

BEA-2000558

Dynamic: An exception occurred while invoking beforeConfigurationLoad() on "{0}". This exception will be consumed.

BEA-2000559

Dynamic: You cannot supply a configuration unit name only. You must also supply the name of the resource in which the unit appears.

BEA-2000560

Dynamic: Instantiation of plugin "{0}" with value "{1}" caused an error "{2}". The alias or class name may have been misspelled, or the class may not be available in the class path.

BEA-2000561

Dynamic: Found multiple properties with different valid prefixes. Properties: {0}, {1}.

BEA-2000562

Dynamic: No registered configuration provider could load "{0}".

BEA-2000563

Dynamic: Default configuration information couldn''t be loaded from any configuration provider.

BEA-2000564

Dynamic: Your system is missing configuration providers. Configuration providers load configuration information for supported specifications. You must have a META-INF/services/{0} file in your classpath listing the available provider classes, and some listed class must be instantiable. Typically this file is bundled as part of the distribution. Have you unbundled it, or unbundled its listed classes?

BEA-2000565

Dynamic: There was an error parsing the properties string "{0}". Please check that the format is: "= = ...".

BEA-2000566

Dynamic: The property named "{0}" was not recognized and will be ignored, although the name closely matches a valid property called "{1}".

BEA-2000567

Dynamic: Configuration property "{0}" cannot be set from a string. You must supply the object value.

BEA-2000568

Dynamic: There was an error while setting up the configuration plugin option "{0}". The plugin was of type "{1}". Setter methods for the following plugin properties were not available in that type: {2}. Possible plugin properties are: {3}. Ensure that your plugin configuration string uses key values that correspond to setter methods in the plugin class.

BEA-2000569

Dynamic: There were errors initializing your configuration: {0}

BEA-2000570

Dynamic: Instantiation of plugin "{0}" with value "{1}" caused an error "{2}". The alias or class name may have been misspelled, or the class may not have be available in the class path. Valid aliases for this plugin are: {3}

BEA-2000571

Dynamic: There was an error while setting up the configuration plugin option "{0}". The plugin was of type "{1}". The plugin property "{2}" had no corresponding setter method or accessible field. The plugin property closely matches "{3}"; perhaps the property was misspelled. Ensure that your plugin configuration string uses key values that correspond to setter methods in the plugin class. All possible plugin properties are: {4}.

BEA-2000572

Dynamic: FATAL

BEA-2000573

Dynamic: UNKNOWN

BEA-2000574

Dynamic: ERROR

BEA-2000575

Dynamic: The file name "{0}" is not valid.

BEA-2000576

Dynamic: An error occurred while trying to create a LogFactory of type "{0}", as specified by the openjpa.Log system property. Created a org.apache.openjpa.lib.log.LogFactoryImpl instead.

BEA-2000577

Dynamic: INFO

BEA-2000578

Dynamic: TRACE

BEA-2000579

Dynamic: The log level string "{0}" is not valid. Valid values are TRACE, INFO, WARN, ERROR or FATAL.

BEA-2000580

Dynamic: {0}

BEA-2000581

Dynamic: WARN

BEA-2000582

Dynamic: Source file locations:

BEA-2000583

Dynamic: Serializing contents: {0}

BEA-2000584

Dynamic: Too many files to scan for metadata. Reached limit of {0} files.

BEA-2000585

Dynamic: Parsing class "{0}".

BEA-2000586

Dynamic: An exception occurred while parsing {0} at location {1}. This exception has been translated to a SAXException, and will be re-thrown. The original exception is being logged along with this message.

BEA-2000587

Dynamic: An error was encountered while parsing element "{0}". Make sure the metadata file is correctly formatted.

BEA-2000588

Dynamic: {0}: {1}

BEA-2000589

Dynamic: Skipping resource "{0}"; it was parsed previously.

BEA-2000590

Dynamic: Writing to file "{0}".

BEA-2000591

Dynamic: XML schema validation is disabled due to bugs detected in the SAX parser.

BEA-2000592

Dynamic: Writing object "{0}".

BEA-2000593

Dynamic: No source file found for "{0}".

BEA-2000594

Dynamic: Adding parse result: "{0}"

BEA-2000595

Dynamic:

BEA-2000596

Dynamic: Location:

BEA-2000597

Dynamic: Error extracting class information from "{0}".

BEA-2000598

Dynamic: Finished parsing metadata resource "{0}".

BEA-2000599

Dynamic: Clearing cache of parsed files in "{0}".

BEA-2000600

Dynamic: Parsing resource "{0}".

BEA-2000601

Dynamic: Type "{0}" could not be instantiated.

BEA-2000602

Dynamic: Unable to differentiate between given package and class elements for class arg parsing. No element can be a complete prefix of another.

BEA-2000603

Dynamic: The result list has been closed.

BEA-2000604

Dynamic: The RangeResultObjectProvider can only be used for ranges that are below Integer.MAX_VALUE. Start index: "{0}", end index: "{1}".

BEA-2000605

Dynamic: Result lists are read-only.

BEA-2000606

Dynamic: Duplicate keys are not allowed in this properties file. Key: {0}, first value: {1}, second value: {2}.

BEA-2000607

Dynamic: Illegal load value of {0} specified.

BEA-2000608

Dynamic: Illegal initial value of {0} specified.

BEA-2000609

Dynamic: Line: {0}, C: {1}

BEA-2000610

Dynamic: Unknown