-----------------------------
Please read the FAQ!
<http://java.apache.org/faq/>
-----------------------------
I wrote:
!This is exactly the point where I think the existing JSSI installation
!notes/FAQs are weak; they don't adequately address the issue of how to
!configure JSSI with JServ to handle the obvious multi-zone usage cases:
!
! (a) different .jhtml pages each invoking servlets in different zones
! (ie: each page only invokes servlets from one zone, but different
! pages are working with different zones)
!
! (b) a particular .jhtml page invokes multiple servlets, not all
! of which reside in the same zone
Henner reponded:
!This is an interesting question for which I have no answer either (though
!I am one of the maintainers of JSSI), but a solution seems to be NEEDED,
!since it is a major drawback to have sophisticated multiple zones
!spreaded on probably many hosts -- but only one zone could be mapped with
!.jhtml (ok, we could map .1jthml, .2jthml on different zones -- but this
!is _awkward_).
I have come up with another possible kludge that solves the problem for my
current requirements, which mostly fall into category (a) above, but not for
more general kinds of usage. If you only have a small number of zones worry
about (like 2 or 3), you can set up as many named virtual hosts as you have
zones, and then place a specialized ApJservAction in the <VirtualHost>
section of httpd.conf for the corresponding server. That maps .jhtml to a
zone of your chosing, assuming a 1-to-1 or even n-to-1 relationship between
virtual host names and zones. You modify the repositories in all the
zone.properties files as per Jon's suggestion.
I've tried it with two virtual servers/two zones and it works. Not in
any sense a scalable solution (past a certain point I suspect your
network folks might woof their lunch), but tolerable for situations
where you are just trying to have separate server configurations for
concurrent phases of a single project (eg: development vs test vs
production). It is fractionally better than the multiple-extension
mappings (.1jhtml, etc.) in cases where the various project phases are
sharing the same collection of web pages. For example, you could keep
the web pages static, and depending on which virtual host you accessed
them from, the SSI would use the new test version of a servlet instead of
the old production version. I suspect you could also solve the problem
with the multiple extension mappings approach and a pile of links
(n x m links, where n is the number of zones, m is the number of .jhtml
pages).
====================================================
= Reid M. Pinchback =
= I/T Delivery, MIT =
= =
= Email: [EMAIL PROTECTED] =
= URL: http://mit.edu/reidmp/www/home.html =
= =
= Respect your own privacy; boycott Pentium III =
====================================================
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
