db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5177) EmbeddedXADataSource should use the SQLException wrapping mechanism when throwing MessageId.CORE_DATABASE_NOT_AVAILABLE
Date Sun, 30 Jun 2013 17:58:20 GMT

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

Mamta A. Satoor updated DERBY-5177:
-----------------------------------

    Labels: derby_triage10_11  (was: )
    
> EmbeddedXADataSource should use the SQLException wrapping mechanism when throwing MessageId.CORE_DATABASE_NOT_AVAILABLE
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5177
>                 URL: https://issues.apache.org/jira/browse/DERBY-5177
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>    Affects Versions: 10.8.1.2
>            Reporter: Rick Hillegas
>            Priority: Minor
>              Labels: derby_triage10_11
>
> When raising CORE_DATABASE_NOT_AVAILABLE, EmbeddedXADataSource builds its own SQLException,
rather than using the Util.generateCsSQLException() logic. That logic is where Derby figures
out the correct subclass of SQLException to throw.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message