[jira] Commented: (TAPESTRY-397) caching should be definable per binding

["Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>]

    [ http://issues.apache.org/jira/browse/TAPESTRY-397?page=comments#action_12315961 ] 

Howard M. Lewis Ship commented on TAPESTRY-397:
-----------------------------------------------

To make this one thing right for you will undo a huge amount of performance improvements to the majority of users.

Perhaps it would be possible to add something to the <component> element (and @Component annotation) to disable caching for all parameters. This would still be a large change late in the 4.0 cycle.

> caching should be definable per binding
> ---------------------------------------
>
>          Key: TAPESTRY-397
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-397
>      Project: Tapestry
>         Type: Improvement
>   Components: Framework
>     Versions: 4.0
>     Reporter: Norbert Sándor
>     Priority: Minor

>
> While I was experimenting with recursive rendering, I wanted to render some of my components recursively. To make this working properly parameter caching must be disabled. But this is only possible by changing the parameter's definition because the current implementation allows the "cache" attribute to be specified only on parameters, not on bindings. However in most cases I want the parameter to be cached.
> Now the only solution to this problem  - as I see - is to copy-paste the component specifications and add cache="true" to the parameter specs.
> Br,
> Norbi

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org