org.datanucleus.Localisation.properties Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of datanucleus-core Show documentation
Show all versions of datanucleus-core Show documentation
DataNucleus Core provides the primary components of a heterogenous Java persistence solution.
It supports persistence API's being layered on top of the core functionality.
################################################################################
# Copyright (c) 2003 Andy Jefferson and others. All rights reserved.
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
# Contributors:
# 2007 Xuan Baldauf - Make error message "023011" a little bit more verbose
# ...
#
# Resources for org.datanucleus package
################################################################################
#
# ClassLoader
#
001000=Class "{0}" was not found in the CLASSPATH. Please check your specification and your CLASSPATH.
001001=Persistence process has been specified to use a ClassLoaderResolver of name "{0}" yet this has not been found by the DataNucleus plugin mechanism. Please check your CLASSPATH and plugin specification.
001002=ClassLoaderResolver specified to use class "{0}" yet this class is not found! Please check your CLASSPATH and plugin specification.
001003=ClassLoaderResolver for class "{0}" gave error on creation : {1}
001004=Class "{0}" was not found in the CLASSPATH [Class resolver called from {1} (line={2})]
001005=Class "{0}" was not found in the CLASSPATH when trying to resolve classes
001006=Class "{0}" was not present in the CLASSPATH. You need to have "{1}" in the CLASSPATH!
#
# DatastoreIdentity
#
002001=Persistence process has been specified to use datastore-identity of name "{0}" yet this has not been found by the DataNucleus plugin mechanism. Please check your CLASSPATH and plugin specification.
002002=datastore-identity "{0}" specified to use class "{1}" yet this class is not found! Please check your CLASSPATH and plugin specification.
#
# L1 Cache
#
003001=Level 1 Cache "{0}" is not registered. Please check your CLASSPATH and specification.
003002=Level 1 Cache "{0}" is registered to use class "{1}" yet this is not found. Please check your CLASSPATH and plugin specification.
003003=Level 1 Cache of type "{0}" initialised
003004=Object "{0}" (id="{1}") added to Level 1 cache (loadedFlags="{2}")
003005=Object "{0}" (id="{1}") updated in Level 1 cache (loadedFlags="{2}")
003006=Attempt to add null object to Level 1 cache. Rejected.
003007=Object with id "{0}" not found in Level 1 cache [cache size = {1}]
003008=Object "{0}" (id="{1}") taken from Level 1 cache (loadedFlags="{2}") [cache size = {3}]
003009=Object with id="{0}" being removed from Level 1 cache [current cache size = {1}]
003010=Object with id="{0}" couldnt be removed from Level 1 cache - wasnt present.
003011=Level 1 Cache cleared
003012=Object "{0}" (id="{1}") being changed to be referenced by id="{2}" in Level 1 cache
#
# L2 Cache
#
004000=Level 2 Cache "{0}" is not registered. Please check your CLASSPATH and specification.
004001=Level 2 Cache "{0}" is registered to use class "{1}" yet this is not found. Please check your CLASSPATH and plugin specification.
004002=Level 2 Cache of type "{0}" initialised
004003=Object "{0}" (id="{1}") added to Level 2 cache (fields="{2}", version="{3}")
004004=Attempt to add null object to Level 2 cache. Rejected.
004005=Object with id "{0}" not found in Level 2 cache
004006=Object with id="{0}" taken from Level 2 cache (fields="{1}", version="{2}") - represented as "{3}"
004007=Object "{0}" (id="{1}") removed from Level 2 cache
004008=Object "{0}" (id="{1}") couldnt be removed from Level 2 cache - wasnt present.
004009=Level 2 Cache cleared
004010=Object "{0}" (id="{1}") being changed to be referenced by id="{2}" in Level 2 cache
004011=Attempt to put a null object into the cache.
004012=Unable to add object with id "{0}" to L2 Cache since it is still attached to a PersistenceManager.
004014=Object with id="{0}" removed from Level 2 cache since was updated yet object has been GCed
004015=Object "{0}" (id="{1}") updated in Level 2 cache (fields="{2}", version="{3}") - fields updated="{4}"
004016=Object with id="{0}" removed from Level 2 cache
#
# Enhancer
#
005000=DataNucleus Enhancer (version {0}) for API "{1}"
005001=DataNucleus Enhancer : Classpath
005002=>> {0}
005003=Input file "{0}" doesnt exist!
005004=DataNucleus Enhancer completed with success for {0} classes. Timings : input={1} ms, enhance={2} ms, total={3} ms. Consult the log for full details
005005=DataNucleus Enhancer completed with success for {0} classes.
005006=DataNucleus Enhancer completed with an error. Please review the enhancer log (at DEBUG level) for full details. Some classes may have been enhanced but some caused errors
005007=DataNucleus Enhancer completed and no classes were enhanced. Consult the log for full details
005008=No "persistence.xml" files were found in the CLASSPATH yet you specified as input the name ("{0}") of a "persistence-unit" to enhance. You must have a valid "persistence.xml" file in the CLASSPATH in a valid location to use this option.
005009=No "persistence-unit" of name "{0}" was found in the CLASSPATH. Please check the "persistence.xml" files available
005010=Enhance of class "{0}" starting ...
005011=Enhance of class "{0}" completed
005012=Validation of enhancement of class "{0}" starting ...
005013=Validation of enhancement of class "{0}" completed
005014=Class "{0}" is already enhanced.
005015=Writing class file "{0}" with enhanced definition
005016=Class "{0}" needs a primary-key class generating, of name {1}
005017=Writing primary-key class file "{0}"
005018=An error was encountered whilst enhancing class "{0}" : {1}
005019=Adding method "{0}"
005020=Adding constructor "{0}"
005021=Adding field "{0}"
005022=Adding interface: {0}
005023=Enhancing original method {0} changing field "{1}" for call to "{2}"
005024=Enhancing original method {0} : omitting enhance of {1} of field "{2}"
005025=You have just attempted to access field "{0}" yet this field was not detached when you detached the object. Either dont access this field, or detach it when detaching the object.
005026=You have just attempted to access property "{0}" yet this property was not detached when you detached the object. Either dont access this property, or detach it when detaching the object.
005027=Class "{0}" doesnt implement the interface "{1}" but is required
005028=Class "{0}" doesnt have field "{1}" but is required
005029=Class "{0}" has field "{1}" but has incorrect access!
005030=Class "{0}" has field "{1}" but has incorrect type "{2}" (should be "{3}")
005031=Class "{0}" doesnt have method "{1}" but is required
005032=Class "{0}" has method "{1}" but has incorrect access!
#
# FetchPlan
#
006000=Field "{0}" declared in the fetch-group "{1}" was not found in the class "{2}
006001=Fetch-group "{0}" nested in the fetch-group "{1}" was not found in class "{2}"
006002=Maximum FetchDepth cannot be given the value {0}. You must specify either -1 (no limit on fetching) or a positive integer.
006003=Detachment roots cannot be changed once set until commit is reached.
006004=Attempt to add the field "{0}" to a fetch group for the class "{1}", but the field doesnt exist in that class!
#
# Reachability
#
007000=Object "{0}" (id="{1}") lifecycle state "{2}" added to the list of reachables on commit.
007002=Performing reachability on multi-valued (collection/map) relation field "{0}"
007003=Performing reachability on multi-valued (array) relation field "{0}"
007004=Performing reachability on single-valued relation field "{0}"
007005=Could not find StateManager for PC object "{0}" at field "{1}" - ignoring for reachability
007006=Field "{0}" has been specified to not use "cascade-persist". Not persisting this field.
007007=Field "{0}" is being persisted for "cascade-persist".
007008=Field "{0}" has been specified to not use "cascade-update". Not updating this field.
007009=Field "{0}" is being updated for "cascade-update".
#
# NucleusContext
#
008000=DataNucleus Context : Version "{0}" with JRE "{1}" on "{2}"
008003=There is no available API adapter "{0}". Using existing adapter.
008004=There is no available StoreManager of type "{0}". Make sure that you have put the relevant DataNucleus 'store' plugin in your CLASSPATH and if defining a connection via JNDI or DataSource you also need to provide persistence property "datanucleus.storeManagerType"
008005=No available StoreManager found for the datastore URL key "{0}". Please make sure you have all relevant plugins in the CLASSPATH (e.g datanucleus-rdbms?, datanucleus-db4o?), and consider setting the persistence property "datanucleus.storeManagerType" to the type of store you are using e.g rdbms, db4o
008009=The MetaDataManager associated with the API "{0}" is not registered. Please check that you have the relevant plugin in your CLASSPATH.
008010=Error creating the MetaDataManager for API "{0}" : {1}
008011=Property "{0}" specified yet cannot be used since the datastore schema is ReadOnly/Fixed
008012=Property "{0}" specified with value "{1}" but this value is invalid. Please check the documentation for valid values
008013=The properties file "{0}" has already been loaded. Ignoring the newly specified properties file "{1}"
008014=Could not load property file "{0}"
008015=Property {0} unknown - will be ignored
008016=GenerateSchema : could not run schema generation step since this datastore ("{0}") doesn't support schema operations
008017=Compiling NamedQuery {0} : "{1}"
#
# Connections
#
009000=The Connection was acquired by the developer and must be closed before using the persistence API.
009001=Connection factory ({0}) not supported - must be a javax.sql.DataSource
009002=Connection Factory "{0}" not found
009003=A database connection is already in use for this manager - perhaps a Query is still running ? The JDO spec (12.6) states that a Persistence Manager can have one datastore connection open at any one time. As a result if you want to perform multiple operations you should use mutliple PersistenceManagers
009004=ManagedConnection found in the pool : "{0}" for key="{1}" in factory="{2}"
009005=ManagedConnection found in the pool : "{0}" for key="{1}" in factory="{2}" but owner object closing so closing connection
009006=ManagedConnection removed from the pool : "{0}" for key="{1}" in factory="{2}"
009007=ManagedConnection added to the pool : "{0}" for key="{1}" in factory="{2}"
009010=Failure to open a connection for datasource "{0}" - check your datasource specification and/or driver
009011=ManagedConnection(non-enlisted) "{0}" opened
009012=ManagedConnection(non-enlisted) "{0}" opened with isolation level "{1}" and auto-commit={2}
009013=ManagedConnection(non-enlisted) "{0}" closed
009014=ManagedConnection(non-enlisted) "{0}" is already closed
009015=ManagedConnection(non-enlisted) "{0}" is being committed.
009016=ManagedConnection(non-enlisted) "{0}" is being rolled back.
009017=ManagedConnection(enlisted) "{0}" starting for transaction "{1}" with flags "{2}"
009018=ManagedConnection(enlisted) "{0}" is preparing for transaction "{1}"
009019=ManagedConnection(enlisted) "{0}" committing for transaction "{1}" with onePhase="{2}"
009020=ManagedConnection(enlisted) "{0}" failed to commit connection for transaction "{1}" with onePhase="{2}"
009021=ManagedConnection(enlisted) "{0}" rolling back for transaction "{1}"
009022=ManagedConnection(enlisted) "{0}" failed to rollback connection for transaction "{1}"
009023=ManagedConnection(enlisted) "{0}" ending for transaction "{1}" with flags "{2}"
#
# ExecutionContext
#
010000=ExecutionContext "{0}" opened for datastore "{1}" with txn="{2}"
010001=ExecutionContext "{0}" closed
010002=ExecutionContext has been closed
010003=ExecutionContext.internalFlush() process started using ordered flush - {0} enlisted objects
010004=ExecutionContext.internalFlush() process finished
010005=Attempt to access HOLLOW nondurable object via getObjectById!
010006=No nondurable object with this id accessible via the cache - maybe for a different manager?
010007=Object with id "{0}" is managed by a different persistence manager
010008=Object is not detached. The operation requires a detached object.
010009=Detaching object from persistence : "{0}" (depth={1})
010010=Detaching copy of object "{0}" (depth={1}) as "{2}" with detached-fields {3} and fields-to-load={4}
010011=DetachOnClose : Closing manager so detaching all current objects ...
010012=DetachOnClose : completed detach
010013=Unable to detach object "{0}" (id="{1}") on commit since it no longer exists in the datastore. Maybe you have datastore constraints that have deleted it
010014=detachCopy cannot be called outside of a transaction when there are transient instances reachable.
010015=Making object persistent : "{0}"
010016=(Re)attaching object to persistence : "{0}"
010017=Attempt to attach object "{0}" to persistence yet another persistent object with this identity already exists enlisted in this transaction
010018=(Re)attaching object to persistence : "{0}" - attaching to be "{1}"
010019=Deleting object from persistence : "{0}"
010020=Transient instances cant be deleted.
010021=Transient-Transactional instances cant be deleted. Object id = {0}
010022=Making object transient : "{0}"
010024=Transient dirty instances can't change to the non transactional state.
010025=Cant call makeNontransactional on Transient non transactional instances
010026=No such object
010027=Failed to find the object of with id "{0}"
010028=Unable to create Object Identity for class when class is null!
010029=Unable to create Object Identity for class "{0}" since key is of an unsupported type ({1})
010030=Error whilst creating new objectId instance of type "{0}" for abstract class "{1}"
010031=Some instances failed to flush successfully due to optimistic verification problems.
010032=Performing check of objects for "persistence-by-reachability" (commit) ...
010033=Object with id "{0}" was reachable when a makePersistent() was called on another object but is no longer reachable (at commit). The object will be removed from the datastore.
010034=Completed check of objects for "persistence-by-reachability" (commit).
010035=Cannot perform operation since ImplementationCreator doesnt exist in the CLASSPATH (put datanucleus-enhancer.jar in the CLASSPATH).
010036=One or more instances could not be evicted
010037=One or more instances could not be refreshed
010038=One or more instances could not be retrieved
010039=One or more instances could not be made persistent
010040=One or more instances could not be deleted
010041=One or more instances could not be made transient
010042=One or more instances could not be made transactional
010043=One or more instances could not be made non-transactional
010044=Unable to find the object with a null id!
010045=Unable to find object with id "{0}" of type "{1}" since this is abstract and you requested no validation
010046=ExecutionContext.internalFlush() process started using optimised flush - {0} to delete, {1} to insert and {2} to update
010047=Object "{0}" was detached before its changes could be flushed. Changes will not reach the datastore. This is likely the result of a JPA detach() call before flush(), which is a stupid thing to do anyway, but it was your choice.
010048=Object "{0}" (id="{1}") passed to '{2}' is not managed by a StateManager! The object needs to be managed.
010050=Attempt to start optimistic transaction yet StoreManager for this datastore doesn't support optimistic locking! Set "datanucleus.Optimistic" to false.
010051=Attempt to find persistable object with class "{0}" and key "{1}"!
010052=Attempt to find object of type "{0}" yet no metadata exists for that class, hence not an available persistable type
#
# ImplementationCreator
#
011000=Instance implements persistable loaded by "{0}" but target persistable has classloader "{1}".
011001=A new instance of "{0}" was created, but it is not assignable to PersistenceCapble. Perhaps a classloading problem. "{1}" The instance implements "{2}"
011002=Abstract class "{0}" has abstract method "{1}" but this is not defined as a persistent property in MetaData
011003=Interface "{0}" has method "{1}" but this is not defined as a persistent property in MetaData
#
# Managed Relationships
#
013000=Management of relations : starting
013001=Management of relations : completed
013002=Management of relations : Object "{0}" field "{1}" was changed to "{2}" but field "{3}" of that object was changed to "{4}"! You can disable this check using "datanucleus.manageRelationshipsChecks"
013003=Management of relations : Object "{0}" field "{1}" was changed to "{2}" but field "{3}" of that object was nulled! You can disable this check using "datanucleus.manageRelationshipsChecks"
013004=Management of relations : Object "{0}" has bidirectional field "{1}" currently set to "{2}" but this is now to be related to "{3}" so nulling this field.
013005=Management of relations : Object "{0}" has bidirectional field "{1}" and object "{2}" has just been set to this object, so updating this objects link across to that object.
013006=Management of relations : Object "{0}" has bidirectional field "{1}" and was related to field "{2}" of object "{3}" but now has been changed. Removing it from the container.
013007=Management of relations : Object "{0}" has a bidirectional field "{1}" and is now related to field "{2}" of object "{3}" but isnt in the container. Adding it.
013008=Management of relations : Object "{0}" has a bidirectional field "{1}" and the object "{2}" was added to this field, but it is in deleted state! You can disable this check using "datanucleus.manageRelationshipsChecks"
013009=Management of relations : Object "{0}" has a bidirectional field "{1}" and the object "{2}" was added to this field, but this field has had its owner set to "{3}"! You can disable this check using "datanucleus.manageRelationshipsChecks"
013010=Management of relations : Object "{0}" has a bidirectional field "{1}" and the object "{2}" was removed from this field, but this field has had its owner set to this one! You can disable this check using "datanucleus.manageRelationshipsChecks"
#
# SchemaTool
#
014000=DataNucleus SchemaTool : Creation of the schema for classes
014001=DataNucleus SchemaTool : Deletion of the schema for classes
014002=DataNucleus SchemaTool : Validation of the schema for classes
014003=DataNucleus SchemaTool : Database information
014004=DataNucleus SchemaTool : Schema information
014005=DataNucleus SchemaTool : Classpath
014006=>> {0}
014007=No valid input (either a set of metadata/class files, or the name of a persistence-unit) was specified!
014008=An error was encountered creating a PersistenceManagerFactory : {0} - please consult the log for more information.
014009=DataNucleus SchemaTool : Input Files
014010=>> {0}
014011=Reading {0} input (metadata/class) files ...
014012=Completed read of {0} input (metadata/class) files
014013=Error processing class file ("{0}"), converting to a URL. Please check your specification and CLASSPATH
014014=An error was encountered reading the specified input files. Please consult the log for details. The following may help : {0}
014015=DataNucleus SchemaTool : Handling schema for persistence-unit "{0}"
014016=No "persistence.xml" files were found in the CLASSPATH yet you specified as input the name ("{0}") of a "persistence-unit" to use in SchemaTool. You must have a valid "persistence.xml" file in the CLASSPATH in a valid location to use this option.
014017=No "persistence-unit" of name "{0}" was found in the CLASSPATH. Please check the "persistence.xml" files available
014018=Outputting Schema DDL to "{0}" for all specified classes
014019=Outputting Schema DDL to "{0}" for classes which dont have existing schema
014020=DataNucleus SchemaTool : Persistence Properties
014021=No MetaData was encountered to generate the schema!
014022=>> {0}={1}
014023=DataNucleus : Help\n>> SchemaTool [options] [mapping-files] [class-files]\nwhere "options" can be\n{0}\n"mapping-files" (and classes specified therein) must be present in the CLASSPATH\n"class-files" must be present in the CLASSPATH
014024=-createSchema : create the actual schema (if supported by the datastore)
014025=-deleteSchema : delete the actual schema (if supported by the datastore)
014026=-create : Create the DB tables for the classes specified by the mapping-files/class-files
014027=-delete : Delete the DB tables for the classes specified by the mapping-files/class-files
014028=-validate : Validate the DB tables for the classes specified by the mapping-files/class-files
014029=-dbinfo : Display the database info (Database version, supported options, datastore types, etc)
014030=-schemainfo : Display the schema info (DDL statements)
014031=-ddlFile : write all DDL statements to the given file instead of sending them to the DB
014032=-completeDdl : write the DDL for all tables not just the missing ones (when using ddlFile)
014033=-help : Write this message
014034=DataNucleus SchemaTool : Creation of the schema {0}
014035=DataNucleus SchemaTool : Deletion of the schema {0}
014036=DataNucleus SchemaTool : The mode parameter only accepts values of "create", "delete", "validate", "dbinfo", "schemainfo"
014037=An exception was thrown during the operation of SchemaTool. Please refer to the log for full details. The following may help : {0}
014038=Error parsing JDO meta-data files : {0}
014039=No classes specified !
014040=Class {0} not found ! Please check that the class is in the CLASSPATH.
014041=Database driver/URL not specified !
014042=Error : No JDO MetaData files specified !
014043=SchemaTool completed successfully
014044=-delete-create : Delete the DB tables for the classes specified by the mapping-files/class-files and recreate them
014045=DataNucleus SchemaTool : Deletion+Creation of the schema
014046=Datastore script "{0}" was not a valid script; has to be a filename, or a URL string
#
# Transactions
#
015000=Transaction begun for ExecutionContext {0} (optimistic={1})
015001=Transaction committing for ExecutionContext {0}
015002=Transaction rolling back for ExecutionContext {0}
015003=Transaction begun with connection {0}
015004=Transaction failed to start
015005=Transaction failed to flush
015006=Transaction committing with connection {0}
015007=Transaction failed to commit
015008=Transaction rolling back with connection {0}
015009=Transaction failed to commit
015012=Invalid isolation level : {0}
015013=Connection {0} started for pessimistic transaction
015014=Connection {0} closed for pessimistic transaction
015015=Connection {0} started for optimistic transaction
015016=Connection {0} closed for optimistic transaction
015017=Object "{0}" (id="{1}") enlisted in transactional cache
015018=Object "{0}" (id="{1}") enlisted in transactional cache is now enlisted using id="{2}"
015019=Object "{0}" (id="{1}") was evicted from transactional cache
015020=Transaction has been marked as "rollback-only". Commit cannot be performed in this state.
015021=Couldnt obtain a connection.
015022=Transaction committed in {0} ms
015023=Transaction rolled back in {0} ms
015024=Use of JTA transactions requires use of a managed datasource since it relies on the TransactionManager to commit datastore connections.
015025=We have already synchronised with the JTA transaction, yet another request was raised to do this!
015026=User requested JTA transactions yet an error occurred while obtaining the JTA transaction.
015027=JTA transaction is marked for rollback, probably had a timeout. Any subsequent operation requiring a database connection will fail.
015028=Error while trying to interrogate JTA Transaction's status!
015029=JTA transaction required to synchronise with the JTA transaction manager, yet we could not access the NamingService. Please check your environment.
015030=JTA transaction required to synchronise with JTA transaction manager, yet we couldnt find the TransactionManager (only WebLogic, JBoss supported)
015031=A database transaction has been rolled back, but the following exceptions were thrown while transitioning the state of the JDO objects participating in the transaction.
015032=Transaction is already active.
015033=Transaction is already active.
015034=Transaction is still active. You should always close your transactions correctly using commit() or rollback().
015035=Transaction is not active. You either need to define a transaction around this, or run your PersistenceManagerFactory with 'NontransactionalRead' and 'NontransactionalWrite' set to 'true'
015036=Transaction is commiting or rolling back. This operation is not available at the moment.
015037=A database transaction has been committed, but the following exceptions were thrown while transitioning the state of the JDO objects participating in the transaction.
015038=Operation {0} failed on resource: {1}, error code {2} and transaction: {3}
015039=Running {0} operation on resource: {1}, error code {2} and transaction: {3}
015040=Transaction is not active. You need to define a transaction around this
015041=Impossible to perform operation since it either requires an active transaction or 'NontransactionalRead' enabled. You have neither of these.
015042=Impossible to perform operation since it either requires an active transaction or 'NontransactionalWrite' enabled. You have neither of these.
015043=The datastore doesnt support the selected transaction isolation level "{0}"
015044=Exception flushing work in JTA transaction. Mark for rollback. Look at the nested exception for details
015045=Cannot mark transaction for rollback after exception in beforeCompletion. PersistenceManager/EntityManager might be in inconsistent state
015046=Exception during afterCompletion in JTA transaction. PersistenceManager/EntityManager might be in inconsistent state
015047=Received unexpected transaction status "{0}"
015048=Transaction.afterCompletion called on {0} but is already closed. This is likely because you're using a JavaEE container (e.g JBoss) that has closed the EntityManager before calling afterCompletion on the transaction of that EntityManager. The JPA spec is totally inadequate in that it does not define the order of such afterCompletion calls and really should state in BOLD that the EntityManager should only be closed after all JTA afterCompletions have been called; try requesting that of the JPA EG. Any statistics gathering is rendered incorrect as a result.
#
# Types
#
016001=Java type {0} using the support for {1}
016002=Exception thrown in converting "{0}" into object of type "{1}"
016003=Java types support initialising ...
016004=User-defined type mapping class "{0}" was not found. Please check the mapping file class specifications and your CLASSPATH. The class must be in the CLASSPATH.
016005=User-defined SCO wrapper class "{0}" was not found. Please check the mapping file class specifications and your CLASSPATH. The class must be in the CLASSPATH.
016006=Java types support loaded : supported java types={0}
016007=Type converter support initialising ...
016008=Type converter support loaded
#
# Sequence
#
017000=The requested sequence "{0}" could not be found. Please make sure that it is specified in a valid Meta-Data file.
017001=The factory class "{0}" for the sequence "{1}" was not found. Please check that it is in the CLASSPATH.
017002=Error when invoking the static method newInstance() on the factory class "{0}" : {1}
017003=The sequence "{0}" has been created, and uses id generator "{1}"
017004=The sequence "{0}" does not have any values allocated. Please call the "allocate(int)" method first to allocate some values.
017005=The sequence "{0}" does not generate numeric values. Please use the "next()" method to access the Object value.
017006=Error while obtaining connection for value generation : {0}
017007=Error while closing connection for value generation : {0}
#
# Exceptions
#
018000=The class "{0}" is not persistable. This means that it either hasn't been enhanced, or that the enhanced version of the file is not in the CLASSPATH (or is hidden by an unenhanced version), or the Meta-Data/annotations for the class are not found.
018001=The class "{0}" is required to be persistable yet no Meta-Data/Annotations can be found for this class. Please check that the Meta-Data/annotations is defined in a valid file location.
018002=The class "{0}" is not persistable. This means that it either hasn't been enhanced, or that the enhanced version of the file is not in the CLASSPATH (or is hidden by an unenhanced version), or the Meta-Data for the class is not found.
018003=The class "{0}" is required to be persistable yet no Meta-Data can be found for this class. Please check that the Meta-Data is defined in a valid file location for JDO.
018004=The class "{0}" is not Detachable. This means that the MetaData for the class did not have the "detachable" attribute set to true.
018005=Some of the specified objects are of classes that are not Detachable. This means that the MetaData for the classes did not have the "detachable" attribute set to true. The nested exceptions contains the details for these objects.
018006=Object of type "{0}" is detached. Detached objects cannot be used with this operation.
018007=Persistent class "{0}" has no extent (defined in the Meta-Data). Please check the specification of the MetaData for this class is you require an Extent.
018008=Field "{0}" contains a persistable object that isnt persistent, but the field doesnt allow cascade-persist!
018009=Field "{0}" does not exist in {1} or is not persistent
018010=Field number {0} does not exist in {1} or is not persistent
#
# Primary Key
#
019000=Class "{0}" has been specified with an object-id class {1} which is an inner class but is not static. The ObjectId class MUST be sttaic if it is defined as an inner class.
019001=Class "{0}" has been specified with an object-id class {1} which is not public. The ObjectId class MUST be public.
019002=Class "{0}" has been specified with an object-id class {1} which is not Serializable. The ObjectId class MUST be Serializable.
019003=Class "{0}" has been specified with the JDO SingleFieldIdentity object-id class, but there are more than 1 primary key field specified for the class. Only one field can be specified as primary key.
019004=Class "{0}" has been specified with an object-id class {1} which doesn't have a default constructor. All objectId classes MUST have a default constructor.
019005=Class "{0}" has been specified with an object-id class {1} which doesn't have a String constructor. All objectId classes MUST have a String constructor.
019006=Class "{0}" has been specified with an object-id class {1} which doesn't override the toString() method. All objectId classes MUST override the toString() method.
019007=Class "{0}" has been specified with an object-id class {1} which doesn't override the hashCode() method. All objectId classes MUST override the hashCode() method and return a value based on the values of all PK fields.
019008=Class "{0}" has been specified with an object-id class {1} which doesn't override the equals() method. All objectId classes MUST override the equals() method and return a value based on the values of all PK fields.
019009=Class "{0}" has been specified with an object-id class {1} which has a field {2} which isn't Serializable. All non static fields of an objectId class must be serializable.
019010=Class "{0}" has been specified with an object-id class {1} which has a field {2} which isn't public. All non static fields of an objectId class must be public.
019011=Class "{0}" has been specified with an object-id class {1} which has a field {2}, but this field was not found in Class {0}.
019012=Class "{0}" has been specified with an object-id class {1} which has a field {2}. The field {0}.{2} has type {3} which is persistence capable. All non static fields of an objectId class must include the names of the primary key fields in the JDO class, and the types of the corresponding fields must be identical.
019013=Class "{0}" has been specified with an object-id class {1} which has a field {2}. The field {1}.{2} has type {3} but should be {4}. All non static fields of an objectId class must include the names of the primary key fields in the JDO class, and the types of the corresponding fields must be identical.
019014=Class "{0}" has been specified with an object-id class {1} which has a field {2}. The field {1}.{2} has type {3} that must be specified in the metadata /jdo/package/class/@objectid-class attribute for type {4}. e.g Meta-Data definition.
044126=Class "{0}" defines a discriminator column, yet so does a superclass! In the vast majority of cases this declaration will be ignored (unless you are having a discriminator column in multiple tables down an inheritance tree).
044129=Class "{0}" field "{1}" has been specified to embed an object of type "{2}", yet this type is an interface and has been specified with an embedded FIELD "{2}". This should be a PROPERTY.
044130=Class "{0}" field "{1}" has . The attribute "table" is not applicable within when it is specified under .
044131=Class "{0}" field "{1}" : has and the element-type has more than 1 value. DataNucleus supports a single value only. If you want to specify many implementations you should use "implementation-classes" DataNucleus extension.
044132=Class "{0}" field "{1}" has been defined with "collection" MetaData yet is not a Collection Field.
044133=Class "{0}" field "{1}" has been defined as a Collection but the element type has not been specified!
044134=Class "{0}" field "{1}" has been defined as a Collection with elements of type {2}. This element type is not found.
044135=Class "{0}" field "{1}" has been defined as a Collection with elements of type {2}. This type has been resolved to {3}
044137=Class "{0}" field "{1}" : has been specified with an order mapped-by yet the mapped-by field ("{2}.{3}") doesnt exist
044138=Class "{0}" field "{1}" : has been specified with an ordering with a field ("{2}.{3}") that doesnt exist
044139=Class "{0}" field "{1}" : has been specified with an ordering with an invalid direction ("{2}"). Should be either ASC or DESC
044140=Class "{0}" field "{1}" : has and the element-type has more than 1 value. DataNucleus supports a single value only. If you want to specify many implementations you should use "implementation-classes" DataNucleus extension.
044141=Class "{0}" field "{1}" : has been defined with "array" MetaData yet is not an array field.
044142=Class "{0}" field "{1}" is an array of (non-serialised) elements of type "{2}" yet no has been specified. You must have a join table to store an array of non-persistable elements, or serialise the array.
044143=Class "{0}" field "{1}" has