[
https://issues.apache.org/jira/browse/WICKET-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juergen Donnerstag resolved WICKET-2530.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.5-M1
Assignee: Juergen Donnerstag
thanks
> Class not found when using OSGI class loader
> --------------------------------------------
>
> Key: WICKET-2530
> URL: https://issues.apache.org/jira/browse/WICKET-2530
> Project: Wicket
> Issue Type: Bug
> Components: wicket-guice
> Affects Versions: 1.4.2
> Reporter: Marc-Andre Houle
> Assignee: Juergen Donnerstag
> Fix For: 1.4.3, 1.5-M1
>
> Attachments: wicket-guice-patch.txt
>
>
> I am presently using Guice and OSGi. Our OSGi platform is used as a plugin
> platform for our web application. We load the OSGi framework and load it
> into Guice as a service provider. The plugins can be used to return panel or
> other wicket components that are then used in the pages.
> When one of the plugins components have a Guice injection, there is a class
> not found problem that is seen when trying to use injected stuff :
> org.apache.wicket.guice.GuiceProxyTargetLocator.locateProxyTarget(GuiceProxyTargetLocator.java:79)
> This class not found is because the Guice injector is trying to access the
> class directly by making a Class.forName. Since using an OSGi framework, the
> classloader is not capable of returning the class correctly.
> To solve this issue, the wicket-guice integration should use the wicket
> Classes.resolveClass static method that is using a class resolver that can be
> changed and check for class in other class loader.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
