aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Bosschaert (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARIES-1339) IllegalAccessException when installing a new subsystem
Date Mon, 29 Jun 2015 11:32:04 GMT

    [ https://issues.apache.org/jira/browse/ARIES-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605488#comment-14605488
] 

David Bosschaert commented on ARIES-1339:
-----------------------------------------

This is caused by incorrectly implemented reflection logic, which was added to Subsystems-core
to allow it to consume both repository 1.0 and 1.1 services at the same time. 

The reflection logic invokes a 'declared' method from the Repository implementation class.
If this class is not public, the invocation will fail like this. It should use the method
from the Repository interface implemented by the repository class instead.

I am working on a fix.

> IllegalAccessException when installing a new subsystem
> ------------------------------------------------------
>
>                 Key: ARIES-1339
>                 URL: https://issues.apache.org/jira/browse/ARIES-1339
>             Project: Aries
>          Issue Type: Bug
>          Components: Subsystem
>    Affects Versions: subsystem-2.0.1
>            Reporter: David Bosschaert
>            Assignee: David Bosschaert
>
> Exception when installing a subsystem:
> SubsystemException: java.lang.IllegalAccessException: Class org.apache.aries.subsystem.core.internal.RepositoryServiceRepository
can not access a member of class org.apache.felix.bundlerepository.impl.OSGiRepositoryImpl
with modifiers "public"
> This can be reproduced by following the steps described in http://aries.apache.org/modules/subsystems.html
to install the feature1.esa file.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message