Mostly Apache-based static site

plamborne <[email protected]> Fri, 16 Sep 2005 15:55:13 CDT
Newsgroups gmane.comp.web.sitemesh.general,gmane.comp.lang.pnuts.user
Message-ID <31172416.1126904143217.JavaMail.os-j2ee@opensymphony01.contegix.com>
Hi, I believe the config of the product I develop on is pretty unique so I'm hoping for some custom advice on best-practice.

Our site contains a couple hundred static pages served by apache.  These do not need decoration, they all use apche/ssi includes to suck in the headers, footers, scripts, etc.

There are only a handful of pages that ping Tomcat for dynamic behavior.

Of these, some are able to be wrapped by static html files living on apache, they use a SSI to call the servlet or jsp that is needed.

What I'd like to do is to use sitemesh to auto-decorate servlets/jsp's as I develop new ones.  The main problem I have here is that some of the existing JSPs are called in two different ways -- as an include from a static html file on apache (where they don't need decoration), and other times from a direct link.

I am hoping sitemesh can spare me the trouble of rebuilding everything to be more sensible.  I want sitemesh to be able to know whether the JSP was called directly (and therefore needs decoration) or whether it was called as an include in the middle of an html page (and there fore does NOT need decoration).

Is there any way to accomplish this?

Now, less importantly, is there a good way to include some of the static html files on apache from within a decorator?  Ie without using the fully qualified URL as if it were a page on another webserver.  Basically, we want all .html files to be served by Apache, not Tomcat.

Sorry if this rambles and makes no sense.  It's an odd architecture.

---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=6819&messageID=15171#15171


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]