[ http://issues.apache.org/jira/browse/TAPESTRY-707?page=comments#action_12356281 ]
Leonardo Quijano Vincenzi commented on TAPESTRY-707: ---------------------------------------------------- This is a great idea which promotes orthogonality. I'd vote for this, but it's closed. A major area of concern is that External Service is unusable (using parameter order to assign values it's a recipe for disaster), and Page Service doesn't allow for params to be set on the URL line. I'd contribute a PageService with named parameters, if only improvements where taken into account here. > 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]
