[EMAIL PROTECTED] wrote:

I have to agree. I believe the reason my files were not being copied is
because the link is being constructed using JavaScript. Practically, this
situation occurs when I'm including a web application generated from another
application into my Forrest site using and iframe. It sounds a little
complicated, but it really worked out well -- once I manually move the
files.


This behaviour (see below) occurs because of the way the site is generated, Cocoon walks through all the links of the site generating the pages as it goes. We recently changed the way RAW files are handled, using the old method your scenario would have been OK, using the new method it is not. Until now we never thought it was a problem, but now you have given us a use case we'll have to reconsider this. I think the forthcoming linkmap will solve this problem but I'm not sure (this mail copied to dev list for comment, I think this has the same root cause as http://issues.cocoondev.org/browse/FOR-341 ).

As a temporary workaround you could add a copy command to the "site" target in FORREST_HOME/main/forrest.build.xml. You should make it copy all the files in your xdocs directory *before* the site is built

Ross



--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.8.6 - Release Date: 07/02/2005



Reply via email to