[ https://issues.apache.org/jira/browse/DERBY-6803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14704958#comment-14704958 ]
Bryan Pendleton commented on DERBY-6803: ---------------------------------------- Before we resolve this issue, we need to address the detail mentioned here: https://issues.apache.org/jira/browse/DERBY-6802?focusedCommentId=14659343&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14659343 > 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)