Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: pass (herse.apache.org: domain of ross.gardler@googlemail.com
 designates 209.85.146.181 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=YgmFEiNFbwBR5/u8fCTO6xn2qgLOmRL+W6l8NDBuMWly/S+LnHmJouy6GIC4G+KB5xydTzJiNyZsP+HmIP8e56FZgvkToLOsJM8TWeic1cttccpKz7MUcxVlsNhApVjreg04fjxJyAf8WewN3IDuFNbldViz7BOrigjizKpRWb0=
Message-ID: <61c9bc470706150045i77abbf88i9cd0b190ee4935da@mail.gmail.com>
Date: Fri, 15 Jun 2007 08:45:29 +0100
From: "Ross Gardler" <rgardler@apache.org>
Sender: ross.gardler@googlemail.com
To: dev@forrest.apache.org
Subject: Re: Conditional application of dispatcher contracts
In-Reply-To: <2a18206d0706141643x2ab62f26q3672843319d17e52@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <61c9bc470706121500o4d45e3f0gc7ff32e705d43ce0@mail.gmail.com>
	 <1181731726.10629.9.camel@cartman>
	 <2a18206d0706131034p388171cficc61eca6305e6f03@mail.gmail.com>
	 <61c9bc470706141244l6f087f77p6bc988052fb1eecd@mail.gmail.com>
	 <2a18206d0706141643x2ab62f26q3672843319d17e52@mail.gmail.com>

On 15/06/07, Brian M Dube <bdube@apache.org> wrote:
> On 6/14/07, Ross Gardler <rgardler@apache.org> wrote:
> > On 13/06/07, Brian M Dube <bdube@apache.org> wrote:
> > > On 6/13/07, Thorsten Scherler <thorsten@apache.org> wrote:
> > > > On Tue, 2007-06-12 at 23:00 +0100, Ross Gardler wrote:
> > > > > Note that overriding the theme with "projectDetails/theme.fv" and
> > > > > "projectDetails/index/theme.fv" does not work as I would have
> > > > > expected, the second theme requested is never used.
> > > > > This looks like a
> > > > > cache problem, is it?
> > > >
> > > > Hmm, not sure would be new. Should work fine: is the template name equal
> > > > to ${dispatcher.theme}?
> > >
> > > I've also experienced this issue in dynamic mode. In my case, the
> > > sequence is (from memory): 1) visit page with default
> > > structurer--works fine; 2) visit page with overridden
> > > structurer--works fine; 3) visit page with default
> > > structurer--non-default structurer from step 2 is used. If I recall,
> > > static mode generation was correct.
> >
> > Did you see Thorstens subsequent mails. Apparently putting overrides
> > of the structurer in the content/xdocs directory is deprecated, and
> > doesn't work.
> >
> > However, the *.fv files in /src/content/resources/structurer/url/foo/bar works.
> >
> > I put a test case (which forms a kind of documentation) in the
> > dispatcher plugin and Thorsten has now fixed it.
>
> I've never tried it in content/xdocs. I had this issue in
> content/resources/structurer/url. The structurer(s) work fine. It acts
> like an intermittent cache issue.

Well now I have moved to the correct location everything seems to work
fine for me. That being said, it's not been tested by a significant
number of people yet.

Ross