"Kirkdorffer, Daniel" wrote:
> Craig,
>
> A question to you on your answer. Having not dived into the newer spec,
> being a 0.91 user with WebSphere, when you say using <jsp:include> will
> include the outout from a servlet, what output would that be?
The output will be whatever bytes your servlet writes to the output stream or
writer, but not any HTTP headers that the included servlet tries to set. The
calling page will have already set the HTTP headers for this response.
Essentially, <jsp:include> is very similar to server-side includes that have
been around for a long time, with a syntax like this:
<!--#include virtual="..." -->
The biggest difference is that the path is being interpreted relative to the
context path of this web application, instead of the document root for the
entire server.
> I assume that
> I'd have to pass any params my servlets typically expect via a GET approach
> in the URL. Right?
>
Because the original request is being passed on, just like with
RequestDispatcher.include(), the called servlet will see the same request
method (GET or POST) that was used to access the calling JSP page. You
therefore cannot assume that it will always be a GET.
>
> Dan
>
Craig
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
