[
https://issues.apache.org/jira/browse/WICKET-5847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138793#comment-15138793
]
Tobias Soloschenko commented on WICKET-5847:
--------------------------------------------
{quote}
For built-in support we would have to agree on a placeholder syntax (e.g. {{}},
${} or #{}), while watching for many pitfalls (overlap with property values
and/or MessageFormat placeholders, increased API complexity etc.).
{quote}
Sadly this is something the users of Wicket have to do in future if no out of
the box solution is provided. Don't get me wrong, but I think a framework
should provide this if it is that simple (one class).
> Support for nested properties keys in translations
> --------------------------------------------------
>
> Key: WICKET-5847
> URL: https://issues.apache.org/jira/browse/WICKET-5847
> Project: Wicket
> Issue Type: New Feature
> Components: wicket
> Affects Versions: 7.0.0-M5
> Reporter: Rob Sonke
> Assignee: Sven Meier
> Priority: Minor
> Attachments: i18nresolver.zip, keyreplacelocalizer.patch,
> screenshot-1.png
>
>
> I wrote an extended version of the Localizer class to support properties like:
> {code}
> lbl.test=This is a string including this ${lbl.other} test
> lbl.other=nested property
> {code}
> Based on this discussion:
> http://apache-wicket.1842946.n4.nabble.com/Resolving-nested-properties-td4669681.html
> It would be nice if this can be added to Wicket core to support this. Then
> developers can easily choose to use this one or not. By default the existing
> Localizer is used.
> I've attached a patch file based on today's master branch which includes the
> new class and some junit tests. Apart from that I attached a zipped
> quickstart that shows the use. Please be aware that I added the new class as
> a copy in that project on the same package as in the real Wicket jar.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
