On Wed, 02 May 2012 19:19:43 -0300, netdawg <net.d...@yahoo.com> wrote:
For the component to pick up page property would make it "Polymorphic".
Regarding your mention of polymorphism and quoting Princess Bride, "I do
not think it means what you think it means.".
Components, for instance, can then just be a "shape" with an abstract
draw() method. The page will tell it what the shape is and what exactly
the draw method will do or for that matter what those parameters are -
in case of a circle it would be a radius, for rectangle - two sides etc.
This doesn't change the fact that they should be self-contained: in other
words, all code to implement its logic inside itself, not scattered.
Either way, when using Tapestry, you should use the definition of
'component' that Tapestry uses. And don't try to go against the principles
used to build a framework when you're using it.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
