[
https://issues.apache.org/jira/browse/DERBY-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charlie Mordant updated DERBY-4120:
-----------------------------------
Attachment: derby OSGI issue.jpg
Hi Rick,
Many other framework use this solution as an easier solution than changing all
their architecture: for example ActiveMQ community choose the name
'activemq-osgi' to wrap the entire amq fwk without taking care of their
internal design.
If it is something that is not acceptable for Derby, I think that it will be
very difficult to find an OSGI compliant, see a simple picture resuming the
problem in attachement
> derbyclient.jar is not a complete OSGi bundle
> ---------------------------------------------
>
> Key: DERBY-4120
> URL: https://issues.apache.org/jira/browse/DERBY-4120
> Project: Derby
> Issue Type: Bug
> Components: Eclipse Plug-in, Services
> Affects Versions: 10.4.2.0
> Environment: OSGi
> Reporter: JJ Snyder
> Assignee: Bryan Pendleton
> Fix For: 10.5.3.1, 10.6.1.0
>
> Attachments: addToManifest.diff, derby OSGI issue.jpg
>
>
> The manifest in derbyclient.jar is incomplete for usage in OSGi. There are
> no packages exported. This appears to only be a problem in standalone
> equinox (outside of eclipse). Note that I did not try other OSGi containers.
> The fix is relatively simple. Adding the Export-Package manifest header
> should take care of the problem.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
