db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4924) o.a.d.client.am not exported in OSGi manifest
Date Mon, 14 Feb 2011 20:03:57 GMT

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

Kathey Marsden updated DERBY-4924:
----------------------------------

    Issue & fix info: [High Value Fix, Newcomer, Workaround attached]  (was: [Workaround
attached])
             Urgency: Normal
              Labels: derby_triage10_8  (was: )

Triage for 10.8. I marked newcomer because I think these issues have been relatively easy
to fix although we don't have tests in place.

> o.a.d.client.am not exported in OSGi manifest
> ---------------------------------------------
>
>                 Key: DERBY-4924
>                 URL: https://issues.apache.org/jira/browse/DERBY-4924
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>    Affects Versions: 10.6.2.1
>            Reporter: Carl Hall
>              Labels: derby_triage10_8
>
> When calling ClientDataSource.setSsl(String), o.a.d.client.am.SqlException can be thrown
but o.a.d.client.am is not exported in the OSGi manifest.
> Either o.a.d.client.am needs to be exported or this exception needs to be moved to an
exported package (only o.a.d.jdbc is currently exported).
> Workaround: catch java.lang.Exception so that the class loader doesn't try to load o.a.d.client.am.

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

        

Mime
View raw message