commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (Commented) (JIRA)" <>
Subject [jira] [Commented] (DBCP-363) dbcp bundle should use DynamicImport
Date Wed, 07 Mar 2012 17:52:57 GMT


Jukka Zitting commented on DBCP-363:

Having DynamicImport in place does not prevent DBCP from also using the DataSourceFactory
mechanism in OSGi.

Meanwhile defining DynamicImport for DBCP does solve the problem for cases where the JDBC
driver exports the relevant driver classes but does not (yet) implement a DataSourceFactory
> dbcp bundle should use DynamicImport
> ------------------------------------
>                 Key: DBCP-363
>                 URL:
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.3, 1.4
>            Reporter: Felix Mayerhuber
>             Fix For: 1.4.1
> The bundle provided in the maven central of the commons.dbcp doesn't have a DynamicImport
defined. This resolves in following error:
> If you want to use a BasicDataSource class as dataSource and the class is provided by
the osgi environment (equinox, ...) the dataSource is not able to be created due to a ClassNotFoundException.
If the bundle would have set DynamicImport it works. (I had to change from your bundle to
the commons.dbcp bundle provided by servicemix, because there the DynamicImport is set)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message