You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Arnaud SAHUGUET <sa...@lucent.com> on 2004/02/16 18:59:25 UTC
adding dynamic content (e.g. JSP, TagLibs, etc.) to Forrest
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
- processing instructions
- other
a concrete example would be appreciated.
regards,
Arnaud
Re: adding dynamic content (e.g. JSP, TagLibs, etc.) to Forrest
Posted by "Justus H. Piater" <Ju...@ULg.ac.be>.
Arnaud SAHUGUET <sa...@lucent.com> wrote on Mon, 16 Feb 2004
12:59:25 -0500:
> I am using Forrest for a CS research web site.
We are currently looking into the same thing.
> 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
> - processing instructions
> - other
You'll have to use some of the deeper functionality of Cocoon to do
that (but that should be no problem, Forrest should work with the full
Cocoon; if it doesn't, complain...).
Publication lists are a prime application for databases. We're going
to use RefDB (http://refdb.sourceforge.net/), which can produce output
in XML format. I hacked up a RefDBGenerator for Cocoon that returns a
publication list in XML format, given a URL that contains a RefDB
query string. (This can probably be done more elegantly using a
RequestGenerator and a RefDBTransformer, to be written.) The pub list
is then integrated into the output using an XIncludeTransformer, and a
custom XSLT style sheet converts RefDB's XML to HTML.
If you don't want to use a database, you can probably put all publis
into one large XML file, and have a Generator or a Transformer
generate XPath expressions to select the desired publications. I
suspect, though, that this will be harder to maintain and that it will
put a noticeable load on your server if you serve the pages
dynamically.
Keep me posted, perhaps we can share some effort...
Justus
--
Justus H. Piater, Ph.D. http://www.montefiore.ulg.ac.be/~piater/
Institut Montefiore, B28 Phone: +32-4-366-2279
Université de Liège, Belgium Fax: +32-4-366-2620
Re: adding dynamic content (e.g. JSP, TagLibs, etc.) to Forrest
Posted by Juan Jose Pablos <ch...@che-che.com>.
Allen Lee escribió:
> 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.
There is not JSP support on the jetty web server that we have compiled.
> 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
> jsps?
If you want to have JSP support do this:
1) Create a War file and insert on a web container that supports it.
2) Replace tools/jetty/jetty-4.2.19.jar for the one on the jetty
distribution.
>
> Thanks for your time!
> Allen
And yours!!!
Re: adding dynamic content (e.g. JSP, TagLibs, etc.) to Forrest
Posted by Allen Lee <al...@cs.indiana.edu>.
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
jsps?
Thanks for your time!
Allen
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 (http://cocoon.apache.org)
>
> >- 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
Re: adding dynamic content (e.g. JSP, TagLibs, etc.) to Forrest
Posted by Ross Gardler <rg...@apache.org>.
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 (http://cocoon.apache.org)
> - 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