"Craig R. McClanahan" wrote:
> Kurt Bernhard Pruenner wrote:
> > "Lacerda, Wellington (AFIS)" wrote:
> > > Why don't you use the plain <jsp:include> ?
> >
> > Because the page is an shtml page that's handled by Apache, and since it's
> > possible to include JSP-pages that are handled by mod_jserv with the old
> > JServ I'm curious why this shouldn't be possible with Tomcat. Also, all
> > our html pages are actually treated as shtml pages, but we really don't
> > want to
> >
> > a) change all of them to JSPs
> > b) have all of them handled by Tomcat for performance reasons
> >
> > (FYI, shtml pages are handled by mod_rewrite for Apache, and #include
> > virtual="..." allows you to include any other page that can otherwise be
> > served by Apache, except that it mysteriously doesn't work with pages that
> > come from Tomcat, while it _does_ work with the older JServ... that's why
> > we've got both JServ and Tomcat running on our server currently, which of
> > course isn't really preferable... :/)
>
> It would be feasible to add SHTML support to Tomcat.
No no no no no... I _don't_ want to add SHTML/SSI support to Tomcat - I want
mod_jserv fixed so that, using the SSI facility in Apache, I can include
Tomcat-generated pages that get passed back to Apache via mod_jserv - the only
thing that hinders this is that mod_jserv seems to pass the wrong location to
Tomcat when it's called to include a page, as it passes the location of the
including (SHTML) page instead of the (JSP's) location that's given using the
"virtual" attribute in the #include statement of the SHTML page... you can see
that when Tomcat generates a file not found message, which is correctly
included into the SHTML page.
I, for performance reasons, don't want to serve all HTML pages which might or
might not include SSI statements using Tomcat, I just want mod_jserv for
Tomcat to work with Apache's SSI parser like mod_jserv for JServ did. :(
Am I really describing it so bad that nobody seems to understand me? :(
I'll try describing it in detail:
1. A request for an SHTML file goes to Apache
2. Apache's SSI facility starts parsing the SHTML file
3. Said facility encounters an <!--#include virtual="<location of a JSP page
that is mounted via AjPServMount and is handled perfectly right when
accessed directly thru this URL>">
4. The location of said JSP page (and some other info) is passed to mod_jserv
5. mod_jserv sends the location of the JSP page to Tomcat
6. Tomcat serves the page back to mod_jserv
7. mod_jserv hands the result back to Apache
8. Apache includes the result in it's output
9. All is fine and dandy, the admins/developers cheer and the crowd roars ;)
The problem is, this works fine with the versions of Apache JServ/GnuJSP and
it's mod_jserv we've got installed on our server, while when using
Tomcat/Jasper and that's mod_jserv the location passed from mod_jserv to
Tomcat in step 5 is that of the including (SHTML) page instead of the (JSP)
page to be included.
I just don't see why this behaviour shouldn't work with Tomcat/Jasper/Tomcat's
mod_jserv when it worked correctly with Apache JServ/GnuJSP/the old
mod_jserv...
--
Kurt Bernhard Pruenner --- Haendelstrasse 17 --- 4020 Linz --- Austria
Music: http://www.mp3.com/Leak --- Work: http://www.ssw.uni-linz.ac.at
.......It might be written "Mindfuck", but it's spelt "L-A-I-N".......
np: Boards Of Canada - Kid For Today: Stereolab Mix (WARP10+3.1 Remixes)
