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

Nick Westgate updated TAPESTRY-1694:
------------------------------------

    Affects Version/s:     (was: 5.0.5)
                           (was: 5.0.4)
                           (was: 5.0.3)
                           (was: 5.0.6)

> Add ability to auto-enhance pages with temp variables.
> ------------------------------------------------------
>
>                 Key: TAPESTRY-1694
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1694
>             Project: Tapestry
>          Issue Type: Wish
>          Components: Framework
>    Affects Versions: 4.1.2
>            Reporter: Kevin Menard
>
> Nowadays, I store most properties right in the page class.  There's typically 
> little reason to store them in the page spec.  For temporary variables, 
> however, such as "value" used in the For component, I tend to put them in the 
> page spec.  The reason is simply that the getters and/or setters would never 
> actually be accessed if they were in the page class and this makes static 
> anaylzers go nuts.  The result is someone invariably removes the method 
> thinking it's no longer needed and then the page breaks.
> What I would like to see is either a new binding or a new attribute.  
> Tapestry would then auto-enhance the page as if the property were defined in 
> the page spec.
> As an example, the following:
> page spec:
> <page-specification class="...">
>     <property name="blah"/>
> </page-specification>
> template:
> <span jwcid="@For" source="ognl:someSource" value="ognl:blah">
>  ...
> </span>
> would reduce to one of the following:
> <span jwcid="@For" source="ognl:someSource" value="temp:blah">
>  ...
> </span>
> or
> <span jwcid="@For" source="ognl:someSource" temp="ognl:blah">
>  ...
> </span>
> In these latter cases, nothing needs to be added to the page spec.  "blah" is 
> just a name given to the current element in the iteration.

-- 
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]

Reply via email to