forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Allen Lee <>
Subject Re: adding dynamic content (e.g. JSP, TagLibs, etc.) to Forrest
Date Fri, 23 Jul 2004 23:59:09 GMT
Sorry to revive an old thread, but I am encountering a similar issue, where
I'd like to have dynamic content, adding JSP forms into a Forrest site.  I
tried random insertion of the JSP file into the generated webapp directory
tree; sticking it in the build/webapp/content directory displays the JSP
page's source text instead of interpreting it.  I know I must be missing
somethin stupid... is this sort of thing easily done, or would I be better off
havin two separate webapps, one for forrest, and the other for the dynamic

Thanks for your time!

On Thu, Feb 19, 2004 at 03:09:36AM -0400, Ross Gardler wrote:
> Arnaud SAHUGUET wrote:
> >Hi,
> >
> >I am using Forrest for a CS research web site.
> >Forrest is great for static content, but for things like publications 
> >(for people, for projects), I would like to have a central XML files 
> >describing all the publications and insert in people's and project's 
> >pages a call to generate the right set of publications.
> >What are my options with Forrest to do that?
> >- XSP
> XSP works pretty much out of the box and is well documented over at 
> Cocoon (
> >- other
> Flowscript, theoretically, should be easy to set up since it is core to 
> Cocoon. I did have a little play with this a while back but hit a couple 
> of problems that I never solved due to lack of an urgent itch.
> I have recently created a site that uses some PERL scripts. Works great 
> in "forrest run", currently requires either manual copying of the perl 
> scripts when distributing, or a configuration of your server to read the 
> scripts from the Forrest site diresctory. If this is an use I can send 
> you the required jetty config file.
> Ross

View raw message