[
http://issues.ops4j.org/browse/PAXEXAM-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12347#action_12347
]
Toni Menzel commented on PAXEXAM-81:
------------------------------------
I am not quite sure if "classloader is not isolated" is the correct term for
the observed behavior.
The OSGi fw runs in a separately spawned process with not a bit of exam other
than regular bundles.
We do a "java -jar felix.main.jar--..params" basically.
Your Test code ends up in a bundle of its own with generated meta data and
"optional" imports generated by bnd.
I predict the NoSuchMethod is being thrown _inside_ the new vm (see log:
"Welcome to Felix") ?
Isn't it then a leak in felix ?
> Pax exam classloader is not isolated
> ------------------------------------
>
> Key: PAXEXAM-81
> URL: http://issues.ops4j.org/browse/PAXEXAM-81
> Project: Pax Exam
> Issue Type: Bug
> Affects Versions: 0.5.0
> Reporter: Guillaume Nodet
> Assignee: Toni Menzel
>
> If the maven pom contains a dependency on Felix 1.6.0, it leads to the
> following exception:
> java.lang.NoSuchMethodError: org.apache.felix.framework.Logger.<init>(I)V
> If there is a dependency on bundlerepository 1.4.0, we have
> java.lang.RuntimeException: Could not create [service.obr]
> The classloader used to create pax runner should be isolated to avoid those
> errors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
