You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by hari ks <ha...@yahoo.com> on 2009/06/08 10:09:22 UTC

component rendering and dispatcher

hi,
  I have a basic doubt. I am not able to understand logic on how Dispatcher(/RequestHandler) gets connected to components in tapestry.

How does Page gets parsed and gets linked to RequestHandler / also how is Page responsible for rendering components?

I couldn't find a documentation on this.

Thanks in Advance,
Hari Sujathan




      

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org

Re: component rendering and dispatcher

Posted by Sergey Didenko <se...@gmail.com>.
If you want to know little details, you can study the code of
org.apache.tapestry5.TapestryFilter.

It gets the control because of the following record in WEB_INF/web.xml:

	<filter>
		<filter-name>app</filter-name>
		<filter-class>org.apache.tapestry5.TapestryFilter</filter-class>
	</filter>


On Mon, Jun 8, 2009 at 11:09 AM, hari ks<ha...@yahoo.com> wrote:
>
> hi,
>  I have a basic doubt. I am not able to understand logic on how Dispatcher(/RequestHandler) gets connected to components in tapestry.
>
> How does Page gets parsed and gets linked to RequestHandler / also how is Page responsible for rendering components?
>
> I couldn't find a documentation on this.
>
> Thanks in Advance,
> Hari Sujathan
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org