felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <j...@apache.org>
Subject [jira] Updated: (FELIX-624) Wrong classloader is used to detect bind/unbind methods
Date Mon, 07 Jul 2008 14:51:31 GMT

     [ https://issues.apache.org/jira/browse/FELIX-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Carsten Ziegeler updated FELIX-624:

    Summary: Wrong classloader is used to detect bind/unbind methods  (was: Import statement
incomplete when inheriting from an abstract class from another bundle)

As discussed in the list, the SCR implementation should not use the classloader of the component
itself to load
the parameter classes for the bind/unbind methods. It should rather use the classloader of
the class implementing
the bind/unbind methods.
I've implemented a simpler variant which uses the classloader of the bundle exporting the
service. This classloader
is definitly able to load the class (and has already loaded it as the service is available).
Available with revision 674514.

> Wrong classloader is used to detect bind/unbind methods
> -------------------------------------------------------
>                 Key: FELIX-624
>                 URL: https://issues.apache.org/jira/browse/FELIX-624
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR)
>    Affects Versions: scr-1.0.2
>            Reporter: Carsten Ziegeler
>         Attachments: Archiv.zip
> I have two bundles:
> Bundle a exporting an abstract class which has a reference to another class (in my test
scenario to a class from commons-collections)
> Bundle b has a class inheriting from the abstract class from Bundle a
> The import package statement in Bundle b does not include the commons-collections class
which results in class not found exceptions
> when bundle b is started.
> This might either be a buig in the maven-bundle-plugin or the used bnd version.
> I'll add a simple test case

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

View raw message