You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Edstrom Johan (JIRA)" <ji...@apache.org> on 2012/06/18 17:53:43 UTC
[jira] [Created] (DBCP-386) Osgi imports and classpath for
Class.forName
Edstrom Johan created DBCP-386:
----------------------------------
Summary: Osgi imports and classpath for Class.forName
Key: DBCP-386
URL: https://issues.apache.org/jira/browse/DBCP-386
Project: Commons Dbcp
Issue Type: Bug
Affects Versions: 1.4
Environment: OSGi, felix, equinox, karaf
Reporter: Edstrom Johan
Priority: Minor
The bundle MANIFEST does not provide a Dynamic import, this forces you to either attach data sources as a fragment or load them via exposed system classes.
A dynamic import * would simplify this.
<commons.osgi.dynamicImport>*</commons.osgi.dynamicImport>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DBCP-386) Osgi imports and classpath for
Class.forName
Posted by "James Carman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DBCP-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13395984#comment-13395984 ]
James Carman commented on DBCP-386:
-----------------------------------
Thank you, Johan! We'll get this added in right away.
> Osgi imports and classpath for Class.forName
> --------------------------------------------
>
> Key: DBCP-386
> URL: https://issues.apache.org/jira/browse/DBCP-386
> Project: Commons Dbcp
> Issue Type: Bug
> Affects Versions: 1.4
> Environment: OSGi, felix, equinox, karaf
> Reporter: Edstrom Johan
> Priority: Minor
> Fix For: 1.4.1
>
>
> The bundle MANIFEST does not provide a Dynamic import, this forces you to either attach data sources as a fragment or load them via exposed system classes.
> A dynamic import * would simplify this.
> <commons.osgi.dynamicImport>*</commons.osgi.dynamicImport>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DBCP-386) Osgi imports and classpath for
Class.forName
Posted by "James Carman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DBCP-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Carman updated DBCP-386:
------------------------------
Fix Version/s: 1.4.1
> Osgi imports and classpath for Class.forName
> --------------------------------------------
>
> Key: DBCP-386
> URL: https://issues.apache.org/jira/browse/DBCP-386
> Project: Commons Dbcp
> Issue Type: Bug
> Affects Versions: 1.4
> Environment: OSGi, felix, equinox, karaf
> Reporter: Edstrom Johan
> Priority: Minor
> Fix For: 1.4.1
>
>
> The bundle MANIFEST does not provide a Dynamic import, this forces you to either attach data sources as a fragment or load them via exposed system classes.
> A dynamic import * would simplify this.
> <commons.osgi.dynamicImport>*</commons.osgi.dynamicImport>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira