db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Hall (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-4924) o.a.d.client.am not exported in OSGi manifest
Date Wed, 01 Dec 2010 02:50:11 GMT
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:
            Reporter: Carl Hall

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.
You can reply to this email to add a comment to the issue online.

View raw message