You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2016/02/22 14:45:19 UTC

[jira] [Updated] (TAP5-1584) Add support for coercing values explicitly in the property expression language

     [ https://issues.apache.org/jira/browse/TAP5-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jochen Kemnade updated TAP5-1584:
---------------------------------
    Labels: bulk-close-candidate  (was: property-expression)

This issue affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent version of Tapestry (currently 5.4.0, available from Maven Central), please update it as soon as possible and add '5.4.0') to the issue's affected versions.

> Add support for coercing values explicitly in the property expression language
> ------------------------------------------------------------------------------
>
>                 Key: TAP5-1584
>                 URL: https://issues.apache.org/jira/browse/TAP5-1584
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.3
>            Reporter: Howard M. Lewis Ship
>            Priority: Minor
>              Labels: bulk-close-candidate
>
> Something like:
>     prop:someMap.get('id') as Integer
> The "as <classname>" qualifier would pass the value through the TypeCoercer.
> Integer is a fully qualified class name, with special cases for java.lang classes (which don't have to be qualified).



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