[
https://issues.apache.org/jira/browse/WICKET-2713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931805#action_12931805
]
Hudson commented on WICKET-2713:
--------------------------------
Integrated in Apache Wicket 1.5.x #511 (See
[https://hudson.apache.org/hudson/job/Apache%20Wicket%201.5.x/511/])
fixed WICKET-2713 Locate .properties files using the same convention as
markup files
and some minor cleanup
Issue: WICKET-2713
> Locate .properties files using the same convention as markup files
> ------------------------------------------------------------------
>
> Key: WICKET-2713
> URL: https://issues.apache.org/jira/browse/WICKET-2713
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Reporter: Peter Swulius
> Assignee: Juergen Donnerstag
> Priority: Minor
> Fix For: 1.5-M4
>
>
> original inquiry on mailing list
> http://www.mail-archive.com/us...@wicket.apache.org/msg47803.html
> --
> I am curious. Why are .properties files not located in the same way as
> .html? I've overridden:
> [ResourceStreamLocator]
> public IResourceStream locate( Class<?> clazz, String aPath, String aStyle,
> Locale aLocale, String anExtension )
> I notice that property file locating doesn't invoke this method, but only
> invokes the lesser arg version with the style/variation/locale already
> embedded in the path. This is an inconvenience for me because I'm trying to
> inspect the style during location. Perhaps I shouldn't be doing what I'm
> trying to do, but after reading the docs, I expected locating to work the way
> it does for .html, but .properties threw me.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
