You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Fe...@thomson.com on 2006/06/13 10:48:59 UTC
Serving cforms resources statically?
Hello,
I have a problem, as out Tomcat is fronted by Apache and we have a lot
of this badly designed JkUnmount rules
which serve all the .js, .gif, etc. statically without calling the
servlet container.
Is there any practical way to extract all this content to a filesystem
location and not have to do a lot of manual work rearranging/modifying
things each time a new Cocoon release is made?
Thanks
RE: Serving cforms resources statically?
Posted by Fe...@thomson.com.
Well, I got it working by putting the resources directories I need
under a top-level directory 'resources', and renaming them to 'forms',
'ajax', etc.
I then mapped the resources-uri to "/contextname/resources".
Of course, every time there is a Cocoon release I will have to copy and
rename those trees again.
It would be good if YourCocoonBasedProjectAnt16 or the brick-cms script
took care of this in the cocoon:get target.
________________________________
From: Mato Mira, Fernando (DIA CHE)
Sent: Tuesday, June 13, 2006 10:49 AM
To: users@cocoon.apache.org
Subject: Serving cforms resources statically?
Hello,
I have a problem, as out Tomcat is fronted by Apache and we have a lot
of this badly designed JkUnmount rules
which serve all the .js, .gif, etc. statically without calling the
servlet container.
Is there any practical way to extract all this content to a filesystem
location and not have to do a lot of manual work rearranging/modifying
things each time a new Cocoon release is made?
Thanks