On Thu, 11 Oct 2012 11:35:12 -0300, Ken in Nashua
wrote:
Folks,
Hi!
I am trying to nail down the concept (or at least inspired concept) of
page and components and how they should be modeled with parameters and
properties.
Here is my semantic concept issue... if you can add to it t
Hi Ken,
Maybe I can help you out:
1. I would not :)
Pages and Components both have Properties. It's nothing special really. Think
Bean Properties with automatic getter/setters.
Components have Parameters, Pages have PageActivationContext. Both can be
Properties as well (because a property i
Pages and components are generally the same for me.
Pages are just top-level components.
They both have parameters: for pages they came from GET/POST/... HTTP
requests, source of component parameters are pages and other components.
Properties are just their state, the state that pages/components
Hey,
I'm not a tapestry expert but here is what I think about pages, components,
properties and parameters:
Parameters (annotated with @Parameter) can only be used in components as
parameters for the component (pages don't have parameters).
Properties (annotated with @Property) are private attrib
