A POST will trigger a redirect (Tapestry employs the redirect-after-post pattern)
An actionlink will also trigger a redirect. However a pagelink will not, this is a straightforward GET request. For redirects yes state is lost. If you are redirecting to the same page you can @Persist fields to store any state (values for @Persist'd fields are stored in the session and are scoped to the one page). If you are redirecting to another page you can store state globally in the session via ApplicationStateManager R. -----Original Message----- From: Damien de Saint Laurent <[email protected]> Reply-to: "Tapestry users" <[email protected]> To: [email protected] Subject: calliing a tapestry component from a JSP Date: Tue, 9 Nov 2010 09:24:01 +0000 (GMT) Hi, Is there a simple way for including a tapestry(5) component into a JSP view with setting request attributes from the JSP and accessing these attributes in the tapestry component via request.getAttribute ? Since, "in Tapestry, there is usually two requests per operation: the action request that redirects to a render request" , I wander if attributes stored in request are lost in between . Best regards, Damien --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
