[
https://issues.apache.org/jira/browse/WICKET-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624271#action_12624271
]
Juergen Donnerstag commented on WICKET-1796:
--------------------------------------------
It is a known problem. Localizer searches for *.properties and *.xml but
doesn't know that it should it ignore the xml file if the markup type is xml as
well. And we don't validate the <properties>.xml schema neither. The problem
really is that Localizer for good reason (see mails in the archive) knows only
about the component class, its locale, style and variant. Just the information
needed to search for the file (properties or xml).
What are the options to fix it:
a) add the component markup type and forward it to the localizer as well. Thus
telling localizer to ignore *.xml files. But wait: all *.xml files or just
specific ones? For all combination of locales, style and variant?
b) define a xml namespace for xml properties files and only if present,
localizer should handle it. If not exception are ignored (may be logged)
any other idea?
> 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.
