forrest-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Clay Leeds <cle...@medata.com>
Subject Re: Forrest page Rendering / file Processing Order
Date Fri, 19 Nov 2004 04:38:16 GMT
On Nov 18, 2004, at 2:08 PM, Dave Brondsema wrote:
> Clay Leeds wrote:
>> On Nov 17, 2004, at 7:26 PM, Dave Brondsema wrote:
>>> Forrest relies on Cocoon for this;  Cocoon's CLI does the traversal, 
>>>  starting at linkmap.html.  My guess is that it is not predictable  
>>> (using a hashmap or something), but you can poke around in the java  
>>> files if you want.  See the files in  
>>> http://svn.apache.org/viewcvs.cgi/cocoon/trunk/src/java/org/apache/ 
>>> cocoon/bean/
>>>
>>> Why, though?  Does it matter?
>> Matter? No. Annoying? Yes! In my quest to get xml-fop working, I am  
>> frequently waiting on one file to be processed: compliance.html 
>> (which  *argh!* happens to come 3/4 of the way down the list... :-/)
>> I suppose I could trick the system, and place a link to 
>> compliance.html  on *every* page... ;-)
>> Web Maestro Clay
>> p.s. Thanks for indulging me with a decent, searchable answer to my  
>> question! I think it will fit nicely in the archives... I appreciate  
>> it!
>
> forrest -Dproject.start-uri=compliance.html
>
> That'll start at compliance.html instead of linkmap.html

Thank you very much! It works like a charm! That would be a good thing 
to add to the docs, although I don't know where. Perhaps the FAQ?

Thanks again! And thanks to Nicola Ken for his suggestion as well.

Web Maestro Clay
-- 
Clay Leeds - <cleeds@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>


Mime
View raw message