You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Sebastian Gooren (JIRA)" <ji...@apache.org> on 2008/08/21 02:00:44 UTC

[jira] Commented: (WICKET-1796) When markup type is XML, getLocalizer().getString( "xyz", (WebPage) ) throws Exception

    [ https://issues.apache.org/jira/browse/WICKET-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624196#action_12624196 ] 

Sebastian Gooren commented on WICKET-1796:
------------------------------------------

Note: A workaround is available. I can put a <WebpageName>.properties file in place. As long as it contains all localized strings used in the webpage, it works.

Unfortunately, this means duplicating a lot of strings from my Application.properties into this secondary properties file.

> When markup type is XML, getLocalizer().getString( "xyz", (WebPage) ) throws Exception
> --------------------------------------------------------------------------------------
>
>                 Key: WICKET-1796
>                 URL: https://issues.apache.org/jira/browse/WICKET-1796
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.4
>         Environment: n/a
>            Reporter: Sebastian Gooren
>
> When using
> @Override
>     public String getMarkupType()
>     {
>         return "xml";
>     }
> in a webpage, I cannot use getLocalizer().getString( "xyz", this ) anymore. I traced it back to
> Caused by: org.xml.sax.SAXParseException: Document root element "order", must match DOCTYPE root "null".
> Apparently, the wicket localizer (org.apache.wicket.resource.loader.ComponentStringResourceLoader.loadStringResource, line 142) decides to look for an XML properties file. Normally, this would be ok. But now, since I have an XML file in place which is the markup for the webpage, localization breaks. Wicket thinks that my markup file is an XML properties file.
> Right now it's either XML markup and no localization for that page, or HTML markup.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.