Apache
/
openjpa
mirror of https://github.com/apache/openjpa.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

improved error message. Yes, this message discusses concrete means for configuration that are not really in the purview of openjpa-kernel. But the benefit of directly mentioning the causes of the problem outweigh the coupling to the underlying configuration mechanisms, at least until we decide to move the error message generation to spec-dependent subtypes. 

git-svn-id: https://svn.apache.org/repos/asf/incubator/openjpa/trunk@499317 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Patrick Linskey 2007-01-24 08:55:26 +00:00
parent d1d0ef0260
commit 6e079939b5
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
openjpa-kernel/src/main/resources/org/apache/openjpa/meta/localizer.properties
View File

@ -276,10 +276,12 @@ not-non-mapped: Type "{0}" cannot be a non-mapped interface as the class is \
non-mapped-pc: A non-mapped interface cannot also be mapped. non-mapped-pc: A non-mapped interface cannot also be mapped.
no-metadatafactory: MetaDataFactory could not be configured \ no-metadatafactory: MetaDataFactory could not be configured \
(conf.newMetaDataFactoryInstance() returned null). This might mean that \ (conf.newMetaDataFactoryInstance() returned null). This might mean that \
no configuration properties were found. If you are \ no configuration properties were found. Ensure that you have a \
using Ant, please see the <properties> or <propertiesFile> attributes \ META-INF/persistence.xml file, that it is available in your classpath, or \
of the task''s nested <config> element. This can also occur if your \ that the properties file you are using for configuration is available. \
OpenJPA distribution jars are corrupt, or if your security policy is \ If you are using Ant, please see the <properties> or <propertiesFile> \
attributes of the task''s nested <config> element. This can also occur if \
your OpenJPA distribution jars are corrupt, or if your security policy is \
overly strict. overly strict.
scanning-directory: Scanning directory "{0}" for persistent types. scanning-directory: Scanning directory "{0}" for persistent types.
scanning-jar: Scanning jar "{0}" for persistent types. scanning-jar: Scanning jar "{0}" for persistent types.