Hi Thiago,
I didn't go through that link. That seems sufficient.
Yes, rest all can be debugged from tapestry source..
Thank you,
Hari
--- On Sat, 7/11/09, Thiago H. de Paula Figueiredo <thiag...@gmail.com> wrote:
> From: Thiago H. de Paula Figueiredo <thiag...@gmail.com>
> Subject: Re: how does PageElementFactory,
> ComponentPageElement/instantiatorSource etc.. work?
> To: "Tapestry users" <users@tapestry.apache.org>
> Date: Saturday, July 11, 2009, 12:48 AM
> Em Fri, 10 Jul 2009 15:57:34 -0300,
> hari ks <hari_...@yahoo.com>
> escreveu:
>
> > hi,
>
> Hi!
>
> > What is the sequence of flow between
> PageElementFactory,
> ComponentPageElement/ComponentinstantiatorSource etc.. and
> other important classes to understand the render phase..
>
> You can download the Tapestry source, put some breakpoints
> on them and them debug an application.
> But why do you need to undestand the render phase in such a
> deep detail? Aren't
> http://tapestry.apache.org/tapestry5.1/guide/rendering.html
> and other docuemntation pages enough? Just curious, as I
> work with Tapestry daily for almost 2.5 years and never
> needed to go that far. :)
>
> --Thiago H. de Paula Figueiredo
> Independent Java consultant, developer, and instructor
> http://www.arsmachina.com.br/thiago
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
