Author: dwoods
Date: Tue Mar 9 22:34:06 2010
New Revision: 921177
URL: http://svn.apache.org/viewvc?rev=921177&view=rev
Log:
OPENJPA-1550 Fix comment
Modified:
openjpa/trunk/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/kernel/BatchingPreparedStatementManagerImpl.java
Modified:
openjpa/trunk/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/kernel/BatchingPreparedStatementManagerImpl.java
URL:
http://svn.apache.org/viewvc/openjpa/trunk/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/kernel/BatchingPreparedStatementManagerImpl.java?rev=921177&r1=921176&r2=921177&view=diff
==============================================================================
---
openjpa/trunk/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/kernel/BatchingPreparedStatementManagerImpl.java
(original)
+++
openjpa/trunk/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/kernel/BatchingPreparedStatementManagerImpl.java
Tue Mar 9 22:34:06 2010
@@ -194,9 +194,9 @@ public class BatchingPreparedStatementMa
//When we do a 'getNextException', the 'next exception'
doesn't contain the same message as se.
//That is, 'next exception' contains a subset msg which is
contained in se. For legacy, should
//we continute to use 'sqex' in the 'old path' and use 'se' in
the next path/code?????
-// SQLException sqex = se.getNextException();
- // if (sqex == null)
- // sqex = se;
+ //SQLException sqex = se.getNextException();
+ //if (sqex == null)
+ // sqex = se;
SQLException sqex = se;
if (se instanceof ReportingSQLException){
