[
https://issues.apache.org/jira/browse/TAPESTRY-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Kuhnert resolved TAPESTRY-1760.
-------------------------------------
Resolution: Fixed
Fix Version/s: 4.1.4
Assignee: Jesse Kuhnert
Was fixed to behave as it used to.
> Contrib:Table column ids mangled: underscores become periods so column
> heading lookup fails
> -------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1760
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1760
> Project: Tapestry
> Issue Type: Bug
> Components: Contrib
> Affects Versions: 4.1.3
> Reporter: Geoff Callender
> Assignee: Jesse Kuhnert
> Priority: Critical
> Fix For: 4.1.4
>
>
> Until 4.1.3, this was valid:
> <table jwcid="[EMAIL PROTECTED]:Table"
> columns="User_firstName_colhdg:firstName, User_lastName_colhdg:lastName" ...
> The Table component would produce column headings by using
> "User_firstName_colhdg" and "User_lastName_colhdg" as message keys.
> But now, the underscores are replaced by periods (ie. dots) on the fly and
> the lookup fails, so it outputs these unhappy column headings:
> User.firstName.colhdg User.lastName.colhdg
> The doco states "the title of the column will be taken from translation
> strings of the component by using the column id as a key" at
> http://tapestry.apache.org/tapestry4.1/tapestry-contrib/componentreference/table.html.
> A workaround for anyone experiencing this problem is to change all
> underscores in the affected message keys from underscores to dots - this
> means throughout your code and in the message properties files. This may of
> course be quite error-prone in large systems.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
