On 9/25/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote: > > * Peter Thomas: > > > Just curious to know if others have problems with the > > ReloadingWicketFilter when you make minor changes to a page with > > markup inheritance, you may want to look at the issue history. > > FYI the problem described in the JIRA issue is not related > to markup inheritance. The exception is thrown because the > class TestPage is loaded from two different classloaders, thus > TestPage(classloader1) != TestPage(classloader2). > --
Thanks JBQ. It would be nice to have a better error / stack trace for the above case. Currently it is like "Markup of type 'html' for component ' test.TestPage' not found." The stack trace also gives the impression that markup inheritance has something to do with the error, e.g. " markup.loader.InheritedMarkupMarkupLoader" etc. 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? I'm pretty sure that earlier in the SNAPSHOT days refreshing the page "just worked", and this is backed up by another user here: http://www.nabble.com/Has-something-changed-in-markup-inheritance--t3963374.html#a11532314 I'm just hoping that something can be done (or un-done) to improve the developer experience when using ReloadingWicketFilter. Thanks, Peter.
