I am trying to upgrage from wicket 1.4.1 to 1.4.17 and have following problem.
In our application we configure
getMarkupSettings().setThrowExceptionOnMissingXmlDeclaration(true);
This prevents all Wicket's default pages from rendering since none of
them contain XML prolog anymore. E.g. none of HTML files in
apache-wicket-1.4.17/src/wicket/src/main/java/org/apache/wicket/markup/html/pages
contain XML declaration prolog. When wicket tries to show error page
exception is thrown. Top of stack trace is:
at org.apache.wicket.markup.MarkupParser.parse(MarkupParser.java:280)
at
org.apache.wicket.markup.loader.SimpleMarkupLoader.loadMarkup(SimpleMarkupLoader.java:52)
at
org.apache.wicket.markup.loader.InheritedMarkupMarkupLoader.loadMarkup(InheritedMarkupMarkupLoader.java:62)
at
org.apache.wicket.markup.loader.DefaultMarkupLoader.loadMarkup(DefaultMarkupLoader.java:55)
at org.apache.wicket.markup.MarkupCache.loadMarkup(MarkupCache.java:465)
at
org.apache.wicket.markup.MarkupCache.loadMarkupAndWatchForChanges(MarkupCache.java:561)
at org.apache.wicket.markup.MarkupCache.getMarkup(MarkupCache.java:325)
at org.apache.wicket.markup.MarkupCache.getMarkupStream(MarkupCache.java:216)
at
org.apache.wicket.MarkupContainer.getAssociatedMarkupStream(MarkupContainer.java:351)
at org.apache.wicket.Page.onRender(Page.java:1587)
at org.apache.wicket.Component.render(Component.java:2521)
at org.apache.wicket.Page.renderPage(Page.java:932)
I can work around by switching these exceptions off. But I think that
the problem should be fixed otherwise since even when these exceptions
are switched off following message is written to log:
log.debug("The markup file does not have a XML declaration prolog: " +
markupResourceData.getResource() + ". It is more save to use it. E.g.
<?xml version=\"1.0\" encoding=\"UTF-8\" ?>");
--
Petr Gladkikh
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
