correct configuration property name

git-svn-id: https://svn.apache.org/repos/asf/incubator/openjpa/trunk@471499 13f79535-47bb-0310-9956-ffa450edef68

openjpa-jdbc/src/main/resources/org/apache/openjpa/jdbc/conf/localizer.properties

@@ -221,7 +221,7 @@ ConnectionURL-values: jdbc:JSQLConnect://<hostname>/database=<database>,\
 
 connecting-for-dictionary: OpenJPA will now connect to the database to attempt \
     to determine what type of database dictionary to use.  To prevent this \
-	connection in the future, set your org.apache.openjpa.jdbc.DBDictionary \
+	connection in the future, set your openjpa.jdbc.DBDictionary \
     configuration property to the appropriate value for your database (see \
     the documentation for available values).
 map-factory: Using mapping factory "{0}".

openjpa-jdbc/src/main/resources/org/apache/openjpa/jdbc/meta/localizer.properties

@@ -81,7 +81,7 @@ generic-unique-exists: "{0}" marks its columns as explicitly not unique, but \
 	a unique constraint exists.
 generic-unique-support: "{0}" marks its columns as having a unique constraint, \
 	but your database does not support unique constraints.  Include \
-	"SupportsUniqueConstraints=true" in the org.apache.openjpa.jdbc.DBDictionary \
+	"SupportsUniqueConstraints=true" in the openjpa.jdbc.DBDictionary \
 	configuration property to override this default.
 generic-defer-unique: "{0}" marks its columns as having a deferred unique \
 	constraint, but the existing constraint on these columns is not deferred. \
@@ -187,7 +187,7 @@ join-unique-exists: "{0}" marks its join columns as explicitly not unique, but \
 	a unique constraint exists.
 join-unique-support: "{0}" marks its join columns as having a unique \
 	constraint, but your database does not support unique constraints.  \
-	Include "SupportsUniqueConstraints=true" in the org.apache.openjpa.jdbc.DBDictionary \
+	Include "SupportsUniqueConstraints=true" in the openjpa.jdbc.DBDictionary \
 	configuration property to override this default.
 join-defer-unique: "{0}" marks its join columns as having a deferred unique \
 	constraint, but the existing constraint on these columns is not deferred. \
@@ -331,7 +331,7 @@ cant-use-char: Column "{0}" is type CHAR(1), but OpenJPA cannot \
 	reverse map it into a Java char because OpenJPA is currently configured to \
 	store Java chars into numeric database columns.  To configure OpenJPA to \
 	store Java chars into CHAR(1) columns, set the following property:\n\
-	org.apache.openjpa.jdbc.DBDictionary: StoreCharsAsNumbers=false
+	openjpa.jdbc.DBDictionary: StoreCharsAsNumbers=false
 revtool-running: The reverse mapping tool will run on the database.  The tool \
 	is gathering schema information; this process may take some time.  Enable \
 	the org.apache.openjpa.jdbc.Schema logging category to see messages about schema data.

openjpa-jdbc/src/main/resources/org/apache/openjpa/jdbc/meta/strats/localizer.properties

@@ -110,7 +110,7 @@ outer-join-support: The subclass-join class indicator mapped to "{0}" requires \
 	outer joins to function.  Your database dictionary is configured to use \
 	"traditional" join syntax, which does not support outer joins.  To \
 	use SQL 92 joins instead, set the following property:\n\
-	org.apache.openjpa.jdbc.DBDictionary: JoinSyntax=sql92
+	openjpa.jdbc.DBDictionary: JoinSyntax=sql92
 unknown-discrim-value: Could not map disciminator value "{0}" to any \
 	known subclasses of the requested class "{1}" (known discriminator \
 	values: {2}).

openjpa-jdbc/src/main/resources/org/apache/openjpa/jdbc/sql/localizer.properties

@@ -28,7 +28,7 @@ feature-not-supported: The database dictionary in use ("{0}") reports that it \
 	does not have feature "{1}".  This feature is needed to complete the \
 	current operation.  To force OpenJPA to try to use the feature anyway, set \
 	the following property:\n\
-	org.apache.openjpa.jdbc.DBDictionary: {1}=<value>
+	openjpa.jdbc.DBDictionary: {1}=<value>
 cant-outer-fk: Could not outer join the given foreign key "{0}" due to syntax \
 	and foreign key limitations.  The join was converted to an inner join.
 no-auto-assign: This database dictionary does not support auto-assigned column \
@@ -47,7 +47,7 @@ sqlserver-cachedstmnts: The Microsoft JDBC driver has bugs that manifest \
 sqlserver-netdirect-batch: The JNetDirect JDBC driver has problems when using \
 	batch statements. Please disable prepared \
 	statement pooling when using the this JDBC driver by including \
-	"BatchLimit=0" in your org.apache.openjpa.jdbc.DBDictionary \
+	"BatchLimit=0" in your openjpa.jdbc.DBDictionary \
 	configuration property.
 sqlserver-cursor: The SQLServer connection URL "{0}" may be invalid: \
 	it does not contain the parameter "SelectMethod=cursor", which is \
@@ -56,7 +56,7 @@ oracle-syntax: Oracle 8 does not support SQL92 syntax.  You can avoid \
 	this message by setting the "JoinSyntax" DBDictionary property \
 	to "database".\
 	For example:\n\
-	org.apache.openjpa.jdbc.DBDictionary: oracle(JoinSyntax=database)
+	openjpa.jdbc.DBDictionary: oracle(JoinSyntax=database)
 oracle-batch-lob: LOB operations not allowed for batched statement: {0}
 oracle-batch-bug: The Oracle 9.2 JDBC driver has problems with \
 	batch statements and has been disabled by default.  You can \
@@ -71,17 +71,17 @@ oracle-batch-override: The BatchLimit property was set even though \
 oracle-connecting-for-driver: OpenJPA is now connecting to the database in order \
 	to figure out what JDBC driver you are using, as OpenJPA must alter its \
 	behavior for this database depending on the driver vendor.  To avoid this \
-	connection, set the DriverVendor value in your org.apache.openjpa.jdbc.DBDictionary \
+	connection, set the DriverVendor value in your openjpa.jdbc.DBDictionary \
 	configuration property to one of the following values:\n\
 	oracle, oracle92 (for the 9.2 driver), datadirect, datadirect61 \
 	(for driver versions <= 3.1), other \n\
 	For example:\n\
-	org.apache.openjpa.jdbc.DBDictionary: oracle(DriverVendor=oracle92)
+	openjpa.jdbc.DBDictionary: oracle(DriverVendor=oracle92)
 oracle-constant: Cannot outer join tables "{0}" and "{1}" using native \
 	join syntax and constant joins.  If you are using Oracle 9 or higher, \
 	you should instead use SQL92 joins by specifying the JoinSyntax \
-	value in the org.apache.openjpa.jdbc.DBDictionary configuration property:\n\
-	org.apache.openjpa.jdbc.DBDictionary: oracle(JoinSyntax=sql92).
+	value in the openjpa.jdbc.DBDictionary configuration property:\n\
+	openjpa.jdbc.DBDictionary: oracle(JoinSyntax=sql92).
 oracle-savepoint: An error occurred when attempting to set an Oracle \
 	savepoint "{0}".  You must use Oracle driver and database 9.2 or higher.
 oracle-rollback: An error occurred when attempting to rollback to an Oracle \
@@ -103,7 +103,7 @@ bad-param: The specified parameter of type "{0}" is not a valid query parameter.
 warn-generic: Your database configuration was not recognized as a supported \
 	OpenJPA database. The generic dictionary will be used, which may result in \
 	limited functionality. This behavior can be overridden by specifying the \
-	appropriate dictionary class in the "org.apache.openjpa.jdbc.DBDictionary" \
+	appropriate dictionary class in the "openjpa.jdbc.DBDictionary" \
 	property of the OpenJPA configuration.
 using-dict: Using dictionary class "{0}"{1}.
 no-pessimistic: This dictionary ({0}) does not support locking, so \