[
https://issues.apache.org/jira/browse/DERBY-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573268#action_12573268
]
Knut Anders Hatlen commented on DERBY-3451:
-------------------------------------------
> The main reason originally for EmbedSQLException originally was to be able to
> keep the original non-SQLException (e.g. StandardException, IOException),
> which is (should be?) now handled by Throwable.initClause().
Another reason for EmbedSQLException is to be able to keep the message id so
that we can localize the messages correctly on the network client. I haven't
seen any proposals for how to solve that issue yet. (That's why we create the
argument ferry (an EmbedSQLException) in the JDBC 4.0 exception factory.)
> Throwing a non-java library exception causes some issues for JMX as the
> exception can not be transfered to the client.
Solving this problem involves getting rid of StandardException too, doesn't it?
At least when the SQLException is linked to a StandardException.
> Remove dependency between StandardException class and
> org.apache.derby.impl.jdbc classes.
> -----------------------------------------------------------------------------------------
>
> Key: DERBY-3451
> URL: https://issues.apache.org/jira/browse/DERBY-3451
> Project: Derby
> Issue Type: Sub-task
> Reporter: Dibyendu Majumdar
> Assignee: Dibyendu Majumdar
> Attachments: DERBY-3451_patch_rev630512.txt
>
>
> In the package org.apache.derby.iapi.error, the class StandardException
> contains references to following classes:
> org.apache.derby.impl.jdbc.Util
> org.apache.derby.impl.jdbc.EmbedSQLException
> This is undesirable as it introduces a dependency between StandardException
> and the implementation of EmbedSQLException.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
