[
https://issues.apache.org/jira/browse/FELIX-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182410#comment-13182410
]
Guillaume Sauthier commented on FELIX-3297:
-------------------------------------------
That's exactly the Exception I got when I tried the manipulator v1.8.2
Most of the time, it happens when dealing with exceptions in the code.
You can workaround (partially) this issue by changing your source code:
changing scopes of variables, refining catch blocks, ... but the result is not
always very natural :(
> 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
