[
https://issues.apache.org/jira/browse/WICKET-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juergen Donnerstag resolved WICKET-1888.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.4.5
Assignee: Juergen Donnerstag
as mentioned in the previous comment, it has been fixed in 1.4
> FormComponents (and subclasses) should be able to provide their own resource
> bundles
> ------------------------------------------------------------------------------------
>
> Key: WICKET-1888
> URL: https://issues.apache.org/jira/browse/WICKET-1888
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.3.4
> Reporter: Christian Oldiges
> Assignee: Juergen Donnerstag
> Priority: Minor
> Fix For: 1.4.5
>
>
> In order to fully support the idea to break down a large application into
> small reusable components it seems necessary that FormComponents provide
> their own resource bundles. We have a project that uses a customized subclass
> of Checkbox that needs to provide customized error messages. The ideal place
> for those error messages would be a resource bundle living next to the
> Checkbox subclass but this is not yet supported. Unfortunately the JavaDoc
> for ComponentStringResourceLoader indicates (see example: input1.properties
> => Required) that support for this already exists.
> A small change to FormComponent$MessageSource.getMessage(String key) could
> add support for this. Instead of using the formComponent.getParent() as the
> base for searching the resource string, simply use the formComponent itself.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
