[
https://issues.apache.org/jira/browse/WICKET-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488101
]
Jean-Baptiste Quenot commented on WICKET-457:
---------------------------------------------
NOTE: the issue with wicket 1.2.5 *only* happens when setting output folder to
src/main/webapp/WEB-INF/classes, it does not happen when using target/classes.
> wicket-quickstart issue with wicket-spring : classCastException
> ---------------------------------------------------------------
>
> Key: WICKET-457
> URL: https://issues.apache.org/jira/browse/WICKET-457
> Project: Wicket
> Issue Type: Bug
> Components: wicket-quickstart, wicket-spring
> Affects Versions: 1.2.5
> Reporter: Mathieu Sacrispeyre
> Assigned To: Jean-Baptiste Quenot
> Attachments: IssueQuickstartSpring.zip, quickstart125.zip,
> quickstart13.zip
>
>
> There is a classloader issue when using wicket-spring with wicket-quickstart
> : a classCastException is raised when trying to do something like
> (MyWebApplication) getApplication() in a page.
> In fact Jetty uses its own classloader and not the system one. The problem
> can be solved configuring Jetty to use the good classloader : the one used by
> the rest of the application (Spring...).
> With Jetty 6 (wicket-quickstart currently uses Jetty 4.2) it can be done like
> this :
> WebAppContext web = new WebAppContext();
> web.setClassLoader(Start.class.getClassLoader());
> ...
> server.addHandler(web);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
