Hi Bryan,

I studied your patch and it was helpful. But I still have doubts about the
implementation of getArgs() in MessageUtils, in what form will the function
return the arguments ? I've attached the latest MessageUtils class.

On Sun, Jul 26, 2015 at 12:20 AM, Bryan Pendleton (JIRA) <[email protected]>
wrote:

>
>      [
> https://issues.apache.org/jira/browse/DERBY-6803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Bryan Pendleton updated DERBY-6803:
> -----------------------------------
>     Attachment: clientOutline.diff
>
> The attached "clientOutline.diff" does not compile and is not
> intended to be committed. It is intended to suggest a possible
> implementation of this Jira sub-task. The patch assumes the
> existence of a method in MessageUtils with the signature:
>
>     Object [] getArgs( String sqlerrmc )
>
> Abhinav, I hope this gives you something concrete to work with
> as you continue to study how to build MessageUtils.java.
>
> thanks,
>
> bryan
>
>
> > 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: 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)
>

Reply via email to