db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stan Bradbury (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1945) Need changes to manifest for OSGi environment
Date Wed, 04 Jun 2008 20:59:45 GMT

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

Stan Bradbury commented on DERBY-1945:
--------------------------------------

We too would like to be able to use derby in an OSGI 4 compliant bundle but /META-INF/MANIFEST.MF
is missing Bundle-SymbolicName.   This JIRA addresses the Bundle-SymbolicName topic but also
makes another requests ( two issues in one).  Should another entry or a sub-task be created
for item #1 such that it might be addressed independently of the issue of adding classes to
the exports in the manifest?

ISSUE of interest: 
  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.



> 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.


Mime
View raw message