[
https://issues.apache.org/jira/browse/WICKET-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Messer updated WICKET-4032:
----------------------------------
Attachment: resourceloadingissue.patch
Patch to fix the issue.
This excludes AbstractRepeaters from the component stack, unlike the
getResourcePath method that excludes AbstractRepeaters children. This leaves
the path hierachy sensible, in that it has no 0, 1 etc ids in it, but also
leaves the component hierarchy so that components added as children of abstract
repeaters can have property files that will be looked in for resources.
> Issue when using a StringResourceModel to lookup a resource for a component
> underneath a repeating view.
> --------------------------------------------------------------------------------------------------------
>
> Key: WICKET-4032
> URL: https://issues.apache.org/jira/browse/WICKET-4032
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.18
> Reporter: Nathan Messer
> Assignee: Peter Ertl
> Attachments: resource-lookup.zip, resourceloadingissue.patch
>
>
> Issue when using a StringResourceModel to lookup a resource for a component
> underneath a repeating view.
> When a StringResourceModel is used by a component under a repeating view, the
> ComponentStringResourceLoader doesn't find the resource.
> This seems to be a problem introduced by the fix for 3671.
> In ComponentStringResourceLoader, getResourcePath excludes all
> AbstractRepeaters, however getComponentStack doesn't leading to the two being
> out of sync for the elements of the component hierarchy under the repeating
> view.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
