Author: awhite
Date: Mon Feb 5 08:01:09 2007
New Revision: 503744
URL: http://svn.apache.org/viewvc?view=rev&rev=503744
Log: (empty)
Modified:
incubator/openjpa/trunk/openjpa-jdbc/src/main/resources/org/apache/openjpa/jdbc/meta/strats/localizer.properties
Modified:
incubator/openjpa/trunk/openjpa-jdbc/src/main/resources/org/apache/openjpa/jdbc/meta/strats/localizer.properties
URL:
http://svn.apache.org/viewvc/incubator/openjpa/trunk/openjpa-jdbc/src/main/resources/org/apache/openjpa/jdbc/meta/strats/localizer.properties?view=diff&rev=503744&r1=503743&r2=503744
==============================================================================
---
incubator/openjpa/trunk/openjpa-jdbc/src/main/resources/org/apache/openjpa/jdbc/meta/strats/localizer.properties
(original)
+++
incubator/openjpa/trunk/openjpa-jdbc/src/main/resources/org/apache/openjpa/jdbc/meta/strats/localizer.properties
Mon Feb 5 08:01:09 2007
@@ -90,8 +90,8 @@
class-crit-owner: Field "{0}" declares that it uses class criteria for joins, \
and this field is not owned by an inverse field. As a result, it is \
impossible to correctly null the inverse foreign keys when the field is
\
- deleted. OpenJPA may leave orphan key values in the database if you do
not \
- provide an owning inverse relation using the "mapped-by" attribute.
+ deleted. OpenJPA may leave orphan key values in the database if you do
\
+ not provide an owning inverse relation using the "mapped-by" attribute.
not-map: Field "{0}" declares a map mapping strategy, but is not a map type.
mapped-by-key: Map field "{0}" is attempting to use a map table, but its key \
is mapped by another field. Use an inverse key or join table mapping.
@@ -110,9 +110,9 @@
cant-init-subs: The discriminator for type "{0}" cannot compute the list of \
its subclasses on its own. You should either use a discriminator
strategy \
that has this ability (such as the class-name strategy), include the
set \
- of persistent classes in the "org.apache.openjpa.MetaDataFactory"
property so that OpenJPA \
- can discover all persistent classes at startup, or make sure that all \
- subclasses of this type have had their class instantiated in the JVM \
+ of persistent classes in the "openjpa.MetaDataFactory" property so that
\
+ OpenJPA can discover all persistent classes at startup, or make sure that \
+ all subclasses of this type have had their class instantiated in the JVM \
before performing any persistent operations on this class or its \
subclasses. If this class does not have any subclasses, consider
making \
the class final or changing its discriminator strategy to "final".
