[
https://issues.apache.org/jira/browse/DERBY-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499685
]
Niclas Hedhman commented on DERBY-1945:
---------------------------------------
1. Agree, Bundle-SymbolicName and Bundle-Version are required by the OSGi R4
spec, and forms a unique key.
2. I disagree. If you are adding such internal behavior to the bundle, you
should probably either add them inside the Derby bundle, or create a Fragment
that attaches itself to the host bundle (Derby). This allows you to access the
internal classes accordingly. Internal packages should not be exported
frivolously.
> 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.
