Return-Path: <lryan@evolve.com>
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list tomcat-user@jakarta.apache.org
Received: (qmail 17119 invoked from network); 12 May 2000 04:11:51 -0000
Received: from mail-oak-2.pilot.net (HELO mail02-oak.pilot.net)
 (198.232.147.17)
  by locus.apache.org with SMTP; 12 May 2000 04:11:51 -0000
Received: from skate.evolveinc.com (unknown-123-18.evolveinc.com
 [198.70.123.18] (may be forged)) by mail02-oak.pilot.net with ESMTP id
 VAA03666 for <tomcat-user@jakarta.apache.org>;
 Thu, 11 May 2000 21:11:41 -0700 (PDT)
Received: by skate.evolveinc.com with Internet Mail Service (5.5.2650.21)
	id <KLQMY6DV>; Thu, 11 May 2000 21:09:13 -0700
Message-ID: <BAB068367BD7D3119E8600508B67020401249F@skate.evolveinc.com>
From: "Ryan, Louis" <lryan@evolve.com>
To: "'tomcat-user@jakarta.apache.org'" <tomcat-user@jakarta.apache.org>
Subject: Include path question??
Date: Thu, 11 May 2000 21:09:06 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

Hi,

I am trying to use the <jsp:include> mechanism to include content from a
servlet in some jsp generated content and Im seeing the following behaviour.

The context is mapped in server.xml as follows

<Context path="/home" docBase="c:/home" debug="0" reloadable="false" > 
       </Context>

The page I am using is "/home/jsp/MyPage.jsp" and the include tag is. 

<jsp:include page="/home/servlet/MyServlet"  flush="true">

Internally this creates a RequestDispatcherImpl with path
"/home/servlet/MyServlet" and makes the call to include passing the request
and response.
In the include call is see the line
Request subRequest=context.getContextManager().createRequest( context, path
);

When I step into the createRequest method it determines the path of my
request to be
/home/home/servlet/MyServlet
i.e
context.getPath() + path

before creating the actual request object. Am I right in thinking this is a
bug?

Im using Tomcat 3.1 release, IBM JDK 118 on WinNT

Thanks

Louis Ryan