tapestry-user@jakarta.apache.org
[Top] [All Lists]

Re: How the tapestry specific tags like <jwcid> are interpreted by the b

Subject: Re: How the tapestry specific tags like <jwcid> are interpreted by the browser
From: "Sunil"
Date: Wed, 2 Mar 2005 18:25:26 +0530
Tapestry is a framework built on java servlet API. Browser definately dont understand those tags. Whne u try to access the page of a deployed application of the browser for example if u want to access home page u will say something like .. http://localhost:8080/demo/app?service=page/Home so ur servelet will handle this request and get the .page file for this page and instantiate the class specified after that it will start rendering the html and send the response. At the time of rendering it will replace all
tags havin jwcid tag with some dynamik stuff.

i suggest u to go thru this beutiful presentation. http://www.ociweb.com/javasig/knowledgebase/2004-12/TapestryPresentation.pdf
this is very useful for those who are new to tapestry.


Sunil
----- Original Message ----- From: "Siva VP" <sivak@xxxxxxxxxxxxxxxxxxxx>
To: "Tapestry users" <tapestry-user@xxxxxxxxxxxxxxxxxx>
Sent: Wednesday, March 02, 2005 6:01 PM
Subject: How the tapestry specific tags like <jwcid> are interpreted by the browser


hi

How the tapestry specific tags like <jwcid> are interpreted by the browser

did browsers understand those tags ?? surely no i think

then what is the mechanism behind that how they are interpreted

Thanks & Regards,
Siva,

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@xxxxxxxxxxxxxxxxxx
For additional commands, e-mail: tapestry-user-help@xxxxxxxxxxxxxxxxxx



---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@xxxxxxxxxxxxxxxxxx
For additional commands, e-mail: tapestry-user-help@xxxxxxxxxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>