db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1945) Need changes to manifest for OSGi environment
Date Tue, 19 Jun 2007 20:43:25 GMT

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

Daniel John Debrunner commented on DERBY-1945:

Which exposed class or classes causes the proxy generation process problems?

I think maybe the problem is, as you pointed out, that too many classes are being exposed
in the org.apache.derby.jdbc package.

The javadoc lists the api classes in that package, which is a sub-set of the public classes
in the packge.

I'm also wondering what the proxy generator is doing for connections returned by Derby's DataSources
or Driver.
Is it creating a proxy for java.sql.Connection or a Derby specific class? Because the api
indicates that connections
returned by derby are java.sql.Connection objects, the implementation class is not meant to
be assumed or used by applications.

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

View raw message