Github user cnoelle commented on the issue:
https://github.com/apache/wicket/pull/171
Hi,
I tried using a custom class resolver (one provided by Pax Wicket), but it
doesn't help.
Below is the stack trace that causes the problem... there is no
IClassResolver involved, instead the class is loaded via
WicketObject.resolveClass() (called by WicketObject.newInstance() in the stack
trace). I suspect this is due to the fact that the
Application#initializeComponents() is called before the Application#init()
method, where one would normally register the class loader?
Caused by: org.apache.wicket.WicketRuntimeException: Unable to create
org.ops4j.pax.wicket.internal.Initializer
at
org.apache.wicket.core.util.lang.WicketObjects.newInstance(WicketObjects.java:385)
at org.apache.wicket.Application.addInitializer(Application.java:587)
at org.apache.wicket.Application.load(Application.java:633)
at
org.apache.wicket.Application.initializeComponents(Application.java:511)
at org.apache.wicket.Application.initApplication(Application.java:829)
at
org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:427)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
