felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Clement Escoffier (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FELIX-3297) iPOJO Manipulator throws ClassNotFoundException
Date Thu, 09 Feb 2012 16:52:03 GMT

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

Clement Escoffier resolved FELIX-3297.

    Resolution: Fixed

I've rolled back the Java 7 Frame support for now, as it sounds a lot more complex than expected.

So, without this, we turn around this issue. On Java 7, you needs to use the  -XX:-UseSplitVerifier
JVM option
> iPOJO Manipulator throws ClassNotFoundException
> -----------------------------------------------
>                 Key: FELIX-3297
>                 URL: https://issues.apache.org/jira/browse/FELIX-3297
>             Project: Felix
>          Issue Type: Bug
>          Components: iPOJO
>    Affects Versions: ipojo-manipulator-1.8.2
>            Reporter: Clement Escoffier
>            Assignee: Clement Escoffier
>            Priority: Critical
>             Fix For: ipojo-manipulator-1.8.4
> The new iPOJO manipulator (1.8.2) asks ASM to compute the bytecode frames. However, this
may require ASM to load classes (dependencies of the manipulated class). If this classloading
fails, the maniulatoion is aborted with  a:
> java.lang.RuntimeException: java.lang.ClassNotFoundException: _THE_CLASS_

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


View raw message