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

Lance edited comment on TAP5-2099 at 2/23/16 3:44 PM:
------------------------------------------------------

It seems there's a gap in my knowledge if this is true. Perhaps I need to 
better grok the 
[ParameterWorker|https://github.com/apache/tapestry-5/blob/master/tapestry-core/src/main/java/org/apache/tapestry5/internal/transform/ParameterWorker.java]
 

I was under the impression that the value must be stored by the binding and 
there was no other thread / request scoped place that it lives. If your 
implementation works then I'm obviously wrong 

Please note that I do not want to update the symbol provider, that would be 
wrong. I just want a place to store the new value. 

Can you explain where the new value reference is held in your solution if not 
in the binding? I'm confused 


was (Author: uklance):
It seems there's a gap in my knowledge if this is true. Perhaps I need to 
better grok the 
[ParameterWorker](https://github.com/apache/tapestry-5/blob/master/tapestry-core/src/main/java/org/apache/tapestry5/internal/transform/ParameterWorker.java)
 

I was under the impression that the value must be stored by the binding and 
there was no other thread / request scoped place that it lives. If your 
implementation works then I'm obviously wrong 

Please note that I do not want to update the symbol provider, that would be 
wrong. I just want a place to store the new value. 

Can you explain where the new value reference is held in your solution if not 
in the binding? I'm confused 

> 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, 5.4
>            Reporter: Lance
>              Labels: patch
>         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 was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to