db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dibyendu Majumdar (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3453) The PublicAPI class should belong to org.apache.derby.iapi.jdbc as it handles creation of SQLException
Date Sat, 23 Feb 2008 00:51:19 GMT

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

Dibyendu Majumdar updated DERBY-3453:
-------------------------------------

    Attachment: DERBY-3453_patch_1.txt

The PublicAPI class has been moved to org.apache.derby.iapi.jdbc.
The EmbedSQLException and EmbedSQLWarning classes have been moved out of org.apache.derby.impl.jdbc
to org.apache.derby.iapi.jdbc.

> The PublicAPI class should belong to org.apache.derby.iapi.jdbc as it handles creation
of SQLException
> ------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3453
>                 URL: https://issues.apache.org/jira/browse/DERBY-3453
>             Project: Derby
>          Issue Type: Sub-task
>            Reporter: Dibyendu Majumdar
>            Assignee: Dibyendu Majumdar
>         Attachments: DERBY-3453_patch_1.txt
>
>
> The PublicAPI class should belong to org.apache.derby.iapi.jdbc as it handles creation
of SQLException.
> The classes EmbedSQLException and EmbedSQLWarning are better placed in org.apache.derby.iapi.jdbc.
These classes are referenced outside the jdbc module.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message