* Peter Thomas:
> So to confirm my understanding, when using the
> ReloadingWicketFilter, when you make a change to a Page you have
> to re-trace navigation to a point prior to where the Page is
> loaded. Is that correct?
You have to make sure you're not using an instance of a page
loaded in a previous classloader, ie make sure not to keep an
instance of a page across reloads.
> I'm just hoping that something can be done (or
> un-done) to improve the developer experience when using
> ReloadingWicketFilter.
To be honest ReloadingWicketFilter is a hack to work around how
the JVM loads classes, and it is bootstrapped during the Wicket
application initialization.
If ReloadingWicketFilter is causing more problems than it is meant
to solve, we might simply want to remove it from Wicket,
especially if it proves to be unreliable in complex setups.
Unless you're willing to turn your hope into contribution?
Have you seen my suggestion to clear your session cookie before
reloading the page BTW? All this is very complicated I realize,
but there's not much we can do to simplify reloading.
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
