Mailing-List: contact user-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@forrest.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <44FC117E.8030501@apache.org>
Date: Mon, 04 Sep 2006 12:43:58 +0100
From: Ross Gardler <rgardler@apache.org>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: user@forrest.apache.org
Subject: Re: xinclude
References: <6212b1d00606290824p5557e258q7d878c14d62cd89f@mail.gmail.com>
 <1151595390.8177.39.camel@localhost.localdomain>
 <Pine.LNX.4.58.0609031601400.16247@westbury.dixons.org>
 <44FB3B5C.80808@apache.org>
 <Pine.LNX.4.58.0609040814190.16247@westbury.dixons.org>
 <44FBE573.2010609@apache.org>
 <Pine.LNX.4.58.0609041018400.16247@westbury.dixons.org>
 <44FBFDCA.3070902@apache.org>
 <Pine.LNX.4.58.0609041129080.16247@westbury.dixons.org>
In-Reply-To: <Pine.LNX.4.58.0609041129080.16247@westbury.dixons.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Jim Dixon wrote:
> On Mon, 4 Sep 2006, Ross Gardler wrote:
> 

...

> 
> Following earlier advice, I removed that and rely upon the main Forrest
> sitemap.  In my first email today I wrote: "OK, this file, created after
> reading the advice above, has been dropped".

We are getting confused. I later asked you to add it back in (although 
not explicitly I just said "XI:Include stuff"). However, now I know it 
is not there lets leave it out (see below for the reason for the confusion).

You confirmed in an early post that if you remove the XInclude stuff 
from your source document, the XML source file is found. Cool.

If you add your XInclude stuff back in you get a resource not found error.

You say that the logs do not tell you exactly which file is missing 
(which is very unusual by the way, are you sure there is no file not 
found exception in the logs?)

Since your original source is being found, it must be your included 
source that is not being found. You can confirm this by requesting 
eg/logMeIn.xml - you should see an XML document complete with your 
unprocessed XI:Include statements.

So, check the location of your source document relative to your included 
document and verify that the path in the source document is the same.

Note: it is better to use the cocoon:// protocol to resolve files since 
this will make your source files more portable.

As I have said earlier in the post, there are examples of how to do all 
this in the plugins directory.

>>This should be the pipeline that does the work in your project as
>>project sitemaps override the Forrest sitemaps.
> 
> 
> Is there a reason for using a project sitemap rather than relying on
> the main one?

Yes, and no.

XInclude is not enabled in all pipelines by default. It would create an 
unnecessary processing step in the vast majority of cases. For example, 
it is not enabled in the XML pipelines, but it is enabled in the html 
pipelines. Therefore if you are XIncluding HTML you do not need to 
override your sitemap, but if you want to add XML you do need to, I 
assumed that you needed to do this as you had done so in your first 
example.

Lets leave it out for now.

Ross

[1] 
http://mail-archives.apache.org/mod_mbox/forrest-user/200609.mbox/browser