[
https://issues.apache.org/jira/browse/DERBY-6586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007718#comment-14007718
]
Charlie Mordant commented on DERBY-6586:
----------------------------------------
Why is it resolved?
It's not resolved at all! derby.jar and derbyclient.jar are both exporting
org.apache.derby.jdbc packages, thus making it impossible to have a derby db
and a client on the same OSGI runtime...
(for example, I have an embedded db, with derbynet exporting it on localhost,
consumed by client, as the last picture on the derby main page:
http://db.apache.org/derby/papers/DerbyTut/ns_intro.html)
Known fix is either to change the client api packages, or the server ones (and
seeing if it's the same on derbytools, derbynet...).
> CLONE - derbyclient.jar conflict with derby.jar on package export, which is
> problematic on OSGI environment
> -----------------------------------------------------------------------------------------------------------
>
> Key: DERBY-6586
> URL: https://issues.apache.org/jira/browse/DERBY-6586
> Project: Derby
> Issue Type: Bug
> Components: Network Client, Network Server
> Affects Versions: 10.10.2.0
> Environment: OSGi
> Reporter: Charlie Mordant
> Assignee: Bryan Pendleton
>
> 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)
