[
https://issues.apache.org/jira/browse/DERBY-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769246#action_12769246
]
JJ Snyder commented on DERBY-4120:
----------------------------------
All packages that contain classes that clients may want to cast to the derby
implementation must be exported. For example, if you think that a client
application wants to cast the Statement to
org.apache.derby.client.am.PreparedStatement40 then the
org.apache.derby.client.am package must be exported.
Exporting all of the packages gives client applications the option to directly
access the classes in those packages. So unless a package is intended to be
private then it should probably be exported
> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
