db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-5050) BrokeredConnection could call setHoldability() without using reflection
Date Thu, 17 Feb 2011 09:35:24 GMT

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

Knut Anders Hatlen closed DERBY-5050.
-------------------------------------

          Resolution: Fixed
       Fix Version/s: 10.8.0.0
    Issue & fix info:   (was: [Patch Available])

Committed revision 1071558.

> BrokeredConnection could call setHoldability() without using reflection
> -----------------------------------------------------------------------
>
>                 Key: DERBY-5050
>                 URL: https://issues.apache.org/jira/browse/DERBY-5050
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>    Affects Versions: 10.8.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>             Fix For: 10.8.0.0
>
>         Attachments: d5050.diff
>
>
> BrokeredConnection uses reflection to call Connection.setHoldability() because that method
wasn't available in Java 1.3. Since Derby doesn't support Java 1.3 anymore, we could call
the method directly.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message