geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <>
Subject [jira] Updated: (GERONIMO-5744) bundle urls and 3rd party libraries
Date Mon, 24 Jan 2011 07:04:43 GMT


Jarek Gawor updated GERONIMO-5744:

    Attachment: GERONIMO-5744.patch

Proposed patch for this issue. The patch uses Equinox's classloader hook to return a custom
classloader that 1) uses Equinox's URLConversion service to translate "bundle" urls into "jar"
urls, 2) extends URLClassLoader class - therefore allows applications that assume TCCL to
be a URLClassLoader to still run ok (potentially) and 3) supports searching for META-INF/
resources in statically wired bundles.

> bundle urls and 3rd party libraries
> -----------------------------------
>                 Key: GERONIMO-5744
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: deployment
>    Affects Versions: 3.0-M2
>            Reporter: Jarek Gawor
>         Attachments: GERONIMO-5744.patch
> Resource lookup in Geronimo 3.0 returns "bundle" type of urls. However, a lot of Geronimo
code and a number of third party libraries assumes that urls returned by resource lookup return
"jar" or "file" type of urls. Because of this difference a lot of applications might not work
properly on Geronimo 3.0. The Geronimo specific code has mostly been updated to use OSGi-friendly
ways to look for resources. However, we can't expect every 3rd party library to be updated
to be OSGi friendly. So we might need a solution that can return "jar" or "file" urls that
works with most libraries.
> One possible solution is to use the BundleResourceClassLoader in the xbean-bundleutils
project (currently used in the OpenJPA plugin). That solution could be enhanced with Equinox-specific
extension (URLConverter service) that can convert "bundle" urls directly into "jar" or "file"
urls (using the jars in its bundle cache).

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message