[ http://issues.apache.org/jira/browse/TAPESTRY-707?page=all ]
Howard M. Lewis Ship closed TAPESTRY-707:
-----------------------------------------
Resolution: Invalid
Assign To: Howard M. Lewis Ship
Ordinary properties, or ordinary methods taking multiple parameters, can
already do this. Also there's the external service and IExternalPage interface.
> Page Parameters
> ---------------
>
> Key: TAPESTRY-707
> URL: http://issues.apache.org/jira/browse/TAPESTRY-707
> Project: Tapestry
> Type: Wish
> Components: Framework
> Versions: 4.0
> Reporter: Claus Nielsen
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> I am ew to Tapestry, but as I understand it, a common method of activating a
> page is:
> - Get the page (using @InjectPage or other methods)
> - Passing data to it using it's setters
> - Activating it.
> Exactly which setters must be used is not always obvious. Therefore it would
> be nice if it was possible to annotate the setters / fields a caller is
> expected to use to pass in parameters to the page.
> Then Tapestry could also check that all required parameters has been set
> before the page is activated.
> Taking this a bit further, Tapestry could even take take of calling the
> setters, if the injected page-getter (RequestCycle.activate()) accepted an
> object-array with all the parameters to use.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
