Add ability to load UTF-8 encoded properties not in XML format.
---------------------------------------------------------------
Key: WICKET-2451
URL: https://issues.apache.org/jira/browse/WICKET-2451
Project: Wicket
Issue Type: Improvement
Components: wicket
Affects Versions: 1.4.1
Environment: ALL
Reporter: Olivier Bourgeois
Priority: Trivial
In Wicket 1.4.x if you want to use UTF-8 to encode your localization
properties, you have to switch to the XML properties format. This is mainly
because Wicket PropertiesFactory use native Java Properties that cannot handle
anything else than ISO in versions prior to JDK 6.
After some discussion on the user mailing list I made this patch which is
inspired on one hand by Tapestry 5 which allows to use UTF-8 in property files
(that works also in T4, but differently) and on the other hand by Spring that
uses the JDK 6 features when available.
IMHO XML is a burden here and adds nothing of value in the management of
properties.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
