[jira] Commented: (DERBY-1945) Need changes to manifest for OSGi environment

["Stephen Felts (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DERBY-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501261 ] 

Stephen Felts commented on DERBY-1945:
--------------------------------------

Regarding #2, the problem is that the exposed interfaces references classes that are not exported.  Either they should be exported or the references should be removed.


> Need changes to manifest for OSGi environment
> ---------------------------------------------
>
>                 Key: DERBY-1945
>                 URL: https://issues.apache.org/jira/browse/DERBY-1945
>             Project: Derby
>          Issue Type: Bug
>          Components: Miscellaneous
>    Affects Versions: 10.1.3.1
>            Reporter: Stephen Felts
>            Priority: Minor
>
> When running with Derby in an OSGi environment, there are a couple of changes that are needed in the manifest.
> 1. The manifest does not have a Bundle Symbolic Name.  This causes some tools not to recognize it as an OSGi bundle and some things don't work nicely without the symbolic name. 
> Add Bundle-SymbolicName: derby  to the manifest.
> 2. I'm working with a product that creates dynamic proxies for all of the interfaces like Connection, Statement, etc.
> As part of doing that, it needs access to all classes that are referenced in those interface classes.
> There are several classes that are referenced in packages that are not exported.  The following exports needed to be added to the manifest:
> org.apache.derby.iapi.jdbc
> org.apache.derby.impl.jdbc

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