tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lance (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-2099) Update parameters bound to literal: or symbol: from a mixin
Date Tue, 26 Mar 2013 17:27:15 GMT

    [ https://issues.apache.org/jira/browse/TAP5-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614328#comment-13614328

Lance commented on TAP5-2099:

It's not really that literal:1 is returning something other than 1. It's that a parameter
that started out off being bound to literal:1 but was then changed by a mixin is now returning
a different calue than 1.

Does that feel better?
> Update parameters bound to literal: or symbol: from a mixin
> -----------------------------------------------------------
>                 Key: TAP5-2099
>                 URL: https://issues.apache.org/jira/browse/TAP5-2099
>             Project: Tapestry 5
>          Issue Type: Improvement
>    Affects Versions: 5.3.6
>            Reporter: Lance
>              Labels: binding, literal-binding, mixin, symbol-binding
>         Attachments: TAP52099-1.patch
> Currently, I cannot update a component component parameter that is initialized with a
literal: or symbol: binding from a mixin. If I try to @BindParameter the param and change
it's value, I get a "Binding %s is read-only" exception (originating from AbstractBinding).
> I propose that literal and symbol bindings are sourced from a PerThreadValue that can
be updated by a mixin.
> My original need for this was to create a "SinglePage" mixin for the Grid component which
would set the rowsPerPage parameter to Integer.MAX_VALUE. I can't currently do this because
by default, the parameter is a symbol: binding.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message