You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Howard Miller <me...@howardmiller.co.uk> on 2002/10/15 21:45:10 UTC
Request v Page scope?
Hi,
Can somebody explain (slowly) the difference between Request
scope and Page scope - I particularly don't understand what the
intended purpose of Page scope is.
HM
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Request v Page scope?
Posted by "Craig R. McClanahan" <cr...@apache.org>.
On Tue, 15 Oct 2002, Howard Miller wrote:
> Date: Tue, 15 Oct 2002 20:45:10 +0100
> From: Howard Miller <me...@howardmiller.co.uk>
> Reply-To: Struts Users Mailing List <st...@jakarta.apache.org>,
> me@howardmiller.co.uk
> To: struts Users Mailing List <st...@jakarta.apache.org>
> Subject: Request v Page scope?
>
> Hi,
>
> Can somebody explain (slowly) the difference between Request
> scope and Page scope - I particularly don't understand what the
> intended purpose of Page scope is.
>
In practice, there are only two places that the difference between
page scope and request scope show up:
* When you use <jsp:include> to dynamically include another
page, the included page has its own *page* scope but shares
the same *request* scope as the calling page.
* Page scope is a JSP thing only, not accessible from servlets
or Java code called by servlets. From a Struts perspective,
that means it is pretty useless for passing objects from your
Actions into the pages that will use them to render the
display -- request scope is most commonly used for this.
> HM
>
Craig
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>