From 90a95d4ee9e5f5bd31a2b5a6b45903f5963b30eb Mon Sep 17 00:00:00 2001 From: "Kevin W. Sutter" Date: Fri, 4 Feb 2011 14:51:26 +0000 Subject: [PATCH] OPENJPA-1213. Updating the documentation for the change in behavior with the Query.setParameter() exception processing (at least our implementation of the interface). git-svn-id: https://svn.apache.org/repos/asf/openjpa/trunk@1067185 13f79535-47bb-0310-9956-ffa450edef68 --- .../doc/manual/migration_considerations.xml | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/openjpa-project/src/doc/manual/migration_considerations.xml b/openjpa-project/src/doc/manual/migration_considerations.xml index 83dcb2ae9..898c5c11c 100644 --- a/openjpa-project/src/doc/manual/migration_considerations.xml +++ b/openjpa-project/src/doc/manual/migration_considerations.xml @@ -143,20 +143,20 @@ enhancement and at runtime. -
+
- Query.setParameteres() + Query.setParameter() - The Query interface setParameters() method behavior has - changed to throw an IllegalArgumentException if more - parameter substitutions are supplied than defined in the - createQuery() or createNamedQuery() call, as required by - the JPA2 specification. - OpenJPA 1.2.x and prior versions would silently ignore the - supplied parameter substitutions and allow the Query to be - processed. + The Query interface setParameter() method behavior has + changed to throw an IllegalArgumentException (as required + by the JPA specification) if more parameter substitutions + are supplied than defined in the createQuery(), + createNamedQuery(), or createNativeQuery() invocation. + OpenJPA 1.2.x and prior versions silently ignored these + extraneous parameter substitutions and allowed the Query + to be processed.