Hi Hideyuki,
I think the idea is that if the Application class is modified then you'll
need to restart the whole web application.
Even if we use the ReloadingClassLoader it will reload the class but it wont
be re-init()-ed, so it will not be clear whether the changes are loaded and
taken into acco
Hi Martin,
Thanks for your reply.
Yes, Please see in WicketFilter.init(boolean, FilterConfig).
public void init(final boolean isServlet,
final FilterConfig filterConfig) throws ServletException {
this.filterConfig = filterConfig;
applicationFactory = getApplicationFactory();
applicati
Are you sure ?
See WicketFilter's code and the usage
of org.apache.wicket.protocol.http.WicketFilter.getClassLoader()
ReloadingWicketFilter overrides this method so the reloading class loader
should be used in init() and doFilter().
2011/4/1 Hideyuki TAKEUCHI
> Hi all,
>
> From Wicket 1.5, Reloa
Hi all,
>From Wicket 1.5, ReloadingWicketFilter does not work.
It seems a classloader from WicketFilter.getClassLoader()
isn't used on instancing WebApplication (WicketFilter.java:281).
The below code works correctly, but ad-hoc.
public class MyWicketFilter extends ReloadingWicketFilter {
stat
