[ http://issues.apache.org/jira/browse/DERBY-843?page=comments#action_12375198 ]
David Van Couvering commented on DERBY-843: ------------------------------------------- OK, it appears that in the patch I had applied the JDK 1.3 version of updatableResultSet.out to the jdk16 directory. My own run of derbynetclientmats uncovered this as a problem, and I've fixed it. This answers Knut's first questions. I have also modified StatementTest.java to use SQLStateConstants.CONNECTION_EXCEPTION_CONNECTION_DOES_NOT_EXIST rather than SQLState.NO_CURRENT_CONNECTION. I'm dong a final test run and then I'll check in. I'll mark DERBY-1198 as fixed too when I do the checkin. > Internationalize messages in SectionManager to XaException in > org.apache.derby.client.am > ---------------------------------------------------------------------------------------- > > Key: DERBY-843 > URL: http://issues.apache.org/jira/browse/DERBY-843 > Project: Derby > Type: Sub-task > Components: Network Client > Reporter: David Van Couvering > Assignee: David Van Couvering > Attachments: DERBY-843-2.diff, DERBY-843.diff > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
