Author: mikedd
Date: Mon Feb 7 16:26:20 2011
New Revision: 1068002
URL: http://svn.apache.org/viewvc?rev=1068002&view=rev
Log:
restoring missing message
Modified:
openjpa/branches/2.1.x/openjpa-jdbc/src/main/resources/org/apache/openjpa/jdbc/meta/strats/localizer.properties
Modified:
openjpa/branches/2.1.x/openjpa-jdbc/src/main/resources/org/apache/openjpa/jdbc/meta/strats/localizer.properties
URL:
http://svn.apache.org/viewvc/openjpa/branches/2.1.x/openjpa-jdbc/src/main/resources/org/apache/openjpa/jdbc/meta/strats/localizer.properties?rev=1068002&r1=1068001&r2=1068002&view=diff
==============================================================================
---
openjpa/branches/2.1.x/openjpa-jdbc/src/main/resources/org/apache/openjpa/jdbc/meta/strats/localizer.properties
(original)
+++
openjpa/branches/2.1.x/openjpa-jdbc/src/main/resources/org/apache/openjpa/jdbc/meta/strats/localizer.properties
Mon Feb 7 16:26:20 2011
@@ -134,7 +134,8 @@ bad-unmapped-rel: "{0}" cannot be mapped
its "{1}" primary key field does not use a simple mapping.
unmapped-datastore-value: Instances of type "{0}" are not valid query \
parameters because the type is not mapped.
+cant-set-value: Field "{1}" of "{0}" can not be set to "{2}" value.
multi-column-version-unsupported:You have specified more than one column for \
version data, but the "{1}" version strategy does not support
multi-column \
versioning.
-not-enum-field: Field "{0}" is expected to be a enum but actually is of type
"{1}".
\ No newline at end of file
+not-enum-field: Field "{0}" is expected to be a enum but actually is of type
"{1}".
