Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Thu, 6 Aug 2015 13:35:04 +0000 (UTC)
From: "Bryan Pendleton (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12822880.1429666085000.389035.1438868104721@Atlassian.JIRA>
In-Reply-To: <JIRA.12822880.1429666085000@Atlassian.JIRA>
References: <JIRA.12822880.1429666085000@Atlassian.JIRA>
 <JIRA.12822880.1429666085768@arcas>
Subject: [jira] [Updated] (DERBY-6803) Change Sqlca and SqlException in
 NetworkClient to call MessageUtils
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-6803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Pendleton updated DERBY-6803:
-----------------------------------
    Attachment: clientChanges.diff

Attached clientChanges.diff represents the current code we've been testing.

I also adjusted the Javadoc tag in Sqlca.java to address
the Javadoc complaint following yesterday's commit for
DERBY-6802.

Note that we won't want to resolve this JIRA Issue until
we've more full addressed the sqlerrmc delimiter redundancy
exposed by that Javadoc complaint.

> Change Sqlca and SqlException in NetworkClient to call MessageUtils
> -------------------------------------------------------------------
>
>                 Key: DERBY-6803
>                 URL: https://issues.apache.org/jira/browse/DERBY-6803
>             Project: Derby
>          Issue Type: Sub-task
>          Components: JDBC, Network Client, Network Server
>            Reporter: Bryan Pendleton
>            Assignee: Abhinav Gupta
>            Priority: Minor
>         Attachments: MessageUtils_1.diff, MessageUtils_2.diff, clientChanges.diff, clientOutline.diff
>
>
> Currently, the network client code is not able to access the arguments
> that are associated with a Derby exception that is returned by the engine.
> We would like to change the network client code, specifically the code
> in the Sqlca and SqlException classes, so that it uses the new MessageUtils
> class to access the exception arguments.
> We wish to take the exception arguments and associate them with the
> SqlException object, so that when the client calls the SQLExceptionFactory
> to create a SQLException to throw to the user application, it can create
> a Derby-specific subclass of that exception, when appropriate, which
> contains the arguments that the server sent to the client.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)