db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Charlie Mordant (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-4120) derbyclient.jar is not a complete OSGi bundle
Date Tue, 27 May 2014 13:22:01 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009649#comment-14009649

Charlie Mordant commented on DERBY-4120:


I made a superbundle made of the aggregation of derby, derbyclient, derbynetwork and derbytools,
exporting all their contents (let's call it derby-all). I tested it, and it works for my use-case:
Starting a server, creating a xadatasource, tables and querying it.

I'll publish it as soon as possible, then attach it with this ticket.
It is one of the solutions for that kind of issues (and easy as possible: consists on just
a pom.xml and another two lined file).

In order to integrate well and easily in an OSGI environment Derby team/a good soul should
have to rename the most part of derby packages: for example, suffixing all packages by .network
in the derbynet jar, .client in the client one...
One of the goals to be OSGI compliant is to avoid having the same package exported by two
different jars (bundle).
Once that stuff is done, you just have to declare the maven-bundle-plugin in your pom to have
an out-of-box OSGI compliant manifest (but this kind of changes should preferably be for the
11 release;) )

See you (very) soon!

> 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:
>         Environment: OSGi
>            Reporter: JJ Snyder
>            Assignee: Bryan Pendleton
>             Fix For:,
>         Attachments: addToManifest.diff
> 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

View raw message