Return-Path: 
 <user-return-4776-apmail-forrest-user-archive=forrest.apache.org@forrest.apache.org>
Delivered-To: apmail-forrest-user-archive@www.apache.org
Received: (qmail 60549 invoked from network); 19 Feb 2009 13:07:11 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 19 Feb 2009 13:07:11 -0000
Received: (qmail 11071 invoked by uid 500); 19 Feb 2009 13:07:10 -0000
Delivered-To: apmail-forrest-user-archive@forrest.apache.org
Received: (qmail 11038 invoked by uid 500); 19 Feb 2009 13:07:10 -0000
Mailing-List: contact user-help@forrest.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:user-help@forrest.apache.org>
list-unsubscribe: <mailto:user-unsubscribe@forrest.apache.org>
List-Post: <mailto:user@forrest.apache.org>
Reply-To: user@forrest.apache.org
List-Id: <user.forrest.apache.org>
Delivered-To: mailing list user@forrest.apache.org
Received: (qmail 11029 invoked by uid 99); 19 Feb 2009 13:07:10 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Feb 2009 05:07:10 -0800
X-ASF-Spam-Status: No, hits=1.2 required=10.0
	tests=SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Received: from [193.252.22.190] (HELO smtp6.freeserve.com) (193.252.22.190)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Feb 2009 13:07:01 +0000
Received: from me-wanadoo.net (localhost [127.0.0.1])
	by mwinf3604.me.freeserve.com (SMTP Server) with ESMTP id 5A5577000084
	for <user@forrest.apache.org>; Thu, 19 Feb 2009 14:06:38 +0100 (CET)
Received: from [192.168.1.36] (user-514da6ab.l2.c1.dsl.pol.co.uk
 [81.77.166.171])
	by mwinf3604.me.freeserve.com (SMTP Server) with ESMTP id 26FAA7000082
	for <user@forrest.apache.org>; Thu, 19 Feb 2009 14:06:38 +0100 (CET)
X-ME-UUID: 20090219130638159.26FAA7000082@mwinf3604.me.freeserve.com
Message-ID: <499D595E.8070405@free.fr>
Date: Thu, 19 Feb 2009 13:06:38 +0000
From: Mathieu Champlon <m.champlon@free.fr>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: user@forrest.apache.org
Subject: Re: Embedding existing HTML pages from a location outside
 src/documentation/content/xdocs
References: <4996D919.8060902@free.fr>
In-Reply-To: <4996D919.8060902@free.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Just in case someone faces the same issue, here is how I ended up 
working around it.

I used the following pipeline :

<map:pipelines>
   <map:pipeline>
     <map:match pattern="embedded/**.html">
       <map:generate type="html" src="{properties:content}{0}"/>
       <map:transform 
src="{forrest:forrest.stylesheets}/html-to-document.xsl"/>
       <map:serialize type="xml"/>
     </map:match>
     ...

Along with the following generator (a bit adapted from 
https://issues.apache.org/jira/browse/FOR-679) :

  <map:components>
    <map:generators default="file">
      <map:generator name="html" 
src="org.apache.cocoon.generation.HTMLGenerator">
        <jtidy-config>context://WEB-INF/jtidy.properties</jtidy-config>
      </map:generator>
    </map:generators>
    ...

And this solves the error I had previously which was :
X [0]                                     embedded/embedded_html.html   
BROKEN: 
C:\Users\Mat\Desktop\dev\tools\forrest\main\webapp\.\c:\Users\Mat\Desktop\dev\perso\cpp\forrest_seed\src\WEB-INF\jtidy.properties 
(The filename, directory name, or volume label syntax is incorrect)


Afterwards I played a bit with the forrest sitemap configuration, and 
changed main/webapp/resources/schema/entity/symbols-core-v10.ent like this :
@@ -25,7 +25,7 @@
 <!ENTITY for-s "<strong>Apache Forrest</strong>">
 
 <!-- Configure some sitemap components -->
-<!ENTITY generator-html-jtidy-properties "WEB-INF/jtidy.properties">
+<!ENTITY generator-html-jtidy-properties 
"context://WEB-INF/jtidy.properties">
 <!ENTITY dispatcher-output-serializer "xhtml">
 <!ENTITY serializer-html-encoding "UTF-8">
 <!ENTITY serializer-html-doctype-public "-//W3C//DTD HTML 4.01 
Transitional//EN">

It seems to work quite well and I was able to remove the generator 
definition from my project sitemap entirely.
The jtidy.properties file is then looked for in main/webapp/WEB-INF 
which is fine when no project specific customization is required.

I'm not really sure but maybe this could also be used to fix 
https://issues.apache.org/jira/browse/FOR-679 ?
Actually I never experienced the problem described in FOR-679 anyway so 
maybe it became invalid at some point when moving from 0.8 to 0.9dev ?


MAT.