Return-Path: 
 <tomcat-user-return-130602-apmail-jakarta-tomcat-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org
Received: (qmail 88270 invoked from network); 29 Jul 2005 21:38:28 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 29 Jul 2005 21:38:28 -0000
Received: (qmail 5630 invoked by uid 500); 29 Jul 2005 21:38:12 -0000
Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org
Received: (qmail 5620 invoked by uid 500); 29 Jul 2005 21:38:11 -0000
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-user-help@jakarta.apache.org>
List-Post: <mailto:tomcat-user@jakarta.apache.org>
List-Id: "Tomcat Users List" <tomcat-user.jakarta.apache.org>
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Delivered-To: mailing list tomcat-user@jakarta.apache.org
Received: (qmail 5607 invoked by uid 99); 29 Jul 2005 21:38:11 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Jul 2005 14:38:11 -0700
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of psthomas@gmail.com designates
 64.233.162.201 as permitted sender)
Received: from [64.233.162.201] (HELO zproxy.gmail.com) (64.233.162.201)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Jul 2005 14:38:03 -0700
Received: by zproxy.gmail.com with SMTP id 40so500502nzk
        for <tomcat-user@jakarta.apache.org>;
 Fri, 29 Jul 2005 14:38:09 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=JGnSgc40lMdQH39m1VYDUumVJ6ivfE1tdMoozaGZOQKHVPmfMOmInKU2o1jzhkVuq7w6bG7d3g4aYf2tgfQvgIjV1QsUWlNzhjIzjzhkrYyO14Q5hvYVHDujQE0l1eiWfFoWAjXc+DEOB8zehRxPO9stB3yn8TZcEqjPugIq7Uo=
Received: by 10.36.224.6 with SMTP id w6mr3167603nzg;
        Fri, 29 Jul 2005 14:37:18 -0700 (PDT)
Received: by 10.36.134.15 with HTTP; Fri, 29 Jul 2005 14:37:18 -0700 (PDT)
Message-ID: <f6942ff8050729143745f5dff7@mail.gmail.com>
Date: Fri, 29 Jul 2005 14:37:18 -0700
From: Patrick Thomas <psthomas@gmail.com>
To: tomcat-user@jakarta.apache.org
Subject: jsp:include params
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Hi All,

When jsp:include-ing a page, I see that params from the calling page
are also passed on to the called page.

Example:

caller.jsp: (hypothetically called with param1 =3D val1)=20
<jsp:include page=3D"callee.jsp">
   <param name=3D"param2" value=3D"val2">
</jsp:include>

callee.jsp:
Sees request variables param2 (of course) *and* param1.

This is specified by the spec, so everything's okay in that regard,
but is there a way to have it *not* pass on the callers vars to the
callee? It seems like there are several types of situations where one
would want to use a jsp:include and be able to explicitly control the
parameters it receives.

If there isn't a way to do it, does anyone know the rationale for not
providing the option?

Cheers,
PST

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org