[jira] [Comment Edited] (WICKET-6066) IDataExporter (and CSVDataExporter) does not handle i18n of column headers

["Martin Grigorov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15092769#comment-15092769 ] 

Martin Grigorov edited comment on WICKET-6066 at 1/11/16 10:04 PM:
-------------------------------------------------------------------

The simplest way is to move all these properties into WicketApplication.properties, so that they do not depend on a component.

I see no easy way how auto-wrap it in the export related classes.


was (Author: mgrigorov):
The simplest way is to move all this properties into WicketApplication.properties, so that they do not depend on a component.

I see no easy way how auto-wrap it in the export related classes.

> IDataExporter (and CSVDataExporter) does not handle i18n of column headers
> --------------------------------------------------------------------------
>
>                 Key: WICKET-6066
>                 URL: https://issues.apache.org/jira/browse/WICKET-6066
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-extensions
>    Affects Versions: 6.21.0
>         Environment: All
>            Reporter: Steve Lowery
>            Assignee: Martin Grigorov
>            Priority: Minor
>         Attachments: Simpsons.csv, quickstart.zip
>
>
> When using the CSVDataExporter, it does not handle i18n of the column headers when using ResourceModel unless the developer does a wrap(new ResourceModel("my.key")) when defining the display model for the column.  While this is doable, it would be nice for the exporter to handle the wrapping for them in the case that the developer doesn't do this.  
> The IDataExporter interface doesn't provide any component (the table or otherwise) that it could use to wrap the ResourceModel to.  Maybe it would be the intent to pass in the DataTable to the constructor of the exporter.?
> Any thoughts on how to best achieve what we are looking to do without looking through the entire codebase and wrapping all of the ResourceModels?
> See attached quickstart to replicate.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)