db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bradley Beddoes (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (DERBY-1945) Need changes to manifest for OSGi environment
Date Mon, 26 May 2008 00:05:55 GMT

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

beddoes edited comment on DERBY-1945 at 5/25/08 5:04 PM:
-----------------------------------------------------------------

The symbolic name component of this issue would appear to still not be fixed in 10.4.1.3 making
it impossible to use as an OSGi bundle straight out of the box (Effects at least derby.jar)
even though the associated issue claims it is fixed.

Could this be looked at?

      was (Author: beddoes):
    Even with the closing of the attached issue this would appear to still not be fixed in
10.4.1.3 making it impossible to use as an OSGi bundle straight out of the box. (Effects at
least derby.jar)

Could this be looked at?
  
> 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