On Thu, 11 Oct 2012 11:35:12 -0300, Ken in Nashua <[email protected]>
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 that would be
helpful.
PAGES HAVE PROPERTIES, COMPONENTS HAVE PARAMETERS (yeah I know I can
deviate but this is the general concept)
I wouldn't say that. Components can have properties just fine, but you
should use parameters to pass information to them (or the Environment on
some specific cases). Pages don't have parameters (unless you count the
page activation context as parameters), so you can't use @Parameter on
them..
1. would you agree this is the general concept?
No.
2. under what conditions would I deviate...
Any class can have properties.
2.1 ok say when would i want my page to have parameters
Yes if you consider parameters as the page activation context, no if
you're thinking about @Parameter.
2.2 ok say when would i want my component to have properties
3. I am seeing cases where I need both... for a component... is this bad
practice?
No. Just use the same common sense you'd use for any other Java class. Why
would it be a bad practice? :)
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
