Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <14757254.1145303721587.JavaMail.jira@brutus>
Date: Mon, 17 Apr 2006 19:55:21 +0000 (GMT+00:00)
From: "Rick Hillegas (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-842) Internationalize messages in
 PreparedStatement to Section in org.apache.derby.client.am
In-Reply-To: <1175550010.1137778062439.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DERBY-842?page=comments#action_12374801 ] 

Rick Hillegas commented on DERBY-842:
-------------------------------------

If you wanted to be fancy: checkForClosedResultSet() could use Throwable.getStackTrace() to look at the stack above it and find the first method name which appears in the public api for ResultSet. That name could then be included in the error message.

As a practical matter, I don't see much value to the "Operation {0} not permitted" clause. The application code knows which ResultSet method it just called.

> Internationalize messages in PreparedStatement to Section in org.apache.derby.client.am
> ---------------------------------------------------------------------------------------
>
>          Key: DERBY-842
>          URL: http://issues.apache.org/jira/browse/DERBY-842
>      Project: Derby
>         Type: Sub-task

>   Components: Network Client
>     Reporter: David Van Couvering
>     Assignee: David Van Couvering

>


-- 
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