[
https://issues.apache.org/jira/browse/TAPESTRY-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship updated TAPESTRY-2235:
-------------------------------------------
Priority: Minor (was: Major)
> Annotation for managing a property as the page activation context
> -----------------------------------------------------------------
>
> Key: TAPESTRY-2235
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2235
> Project: Tapestry
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.0.11
> Reporter: Howard M. Lewis Ship
> Priority: Minor
>
> A very common idiom is to have a page that exists to view/edit/create an
> entity, and to store the entity as the page activation context (relying on a
> ValueEncoder to extract the primary key as the value in the URL). Example
> code:
> public class ShowAccount
> {
> @GenerateAccessors
> private Account _account;
> void onActivate(Account account)
> {
> _account = account;
> }
> Object onPassivate()
> {
> return _account;
> }
> }
> It seems that these two methods could be generated automatically in some way,
> i.e.
> public class ShowAccount
> {
> @GenerateAccessors
> @PageActivationContext
> private Account _account;
> }
--
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]
