Page has context, component has parameters. Component should NOT care nor know the page it is in, to promote real componentization. It is not the job of the component to decode the parameters from web, the page should do that. And then the page should forward the context as parameters to the component. The page can also contain lots of other state that the component is not interested of and the same component could be used from several pages that have different context encoding schemes.
- Ville -- View this message in context: http://tapestry.1045711.n5.nabble.com/Pagination-Component-tp4455142p4456045.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
