From user-return-3075-apmail-forrest-user-archive=forrest.apache.org@forrest.apache.org Tue Jan 03 21:39:07 2006
Return-Path: <user-return-3075-apmail-forrest-user-archive=forrest.apache.org@forrest.apache.org>
Delivered-To: apmail-forrest-user-archive@www.apache.org
Received: (qmail 1825 invoked from network); 3 Jan 2006 21:39:07 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 3 Jan 2006 21:39:07 -0000
Received: (qmail 2894 invoked by uid 500); 3 Jan 2006 21:39:07 -0000
Delivered-To: apmail-forrest-user-archive@forrest.apache.org
Received: (qmail 2800 invoked by uid 500); 3 Jan 2006 21:39:06 -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 2789 invoked by uid 99); 3 Jan 2006 21:39:06 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jan 2006 13:39:06 -0800
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=HTML_MESSAGE
X-Spam-Check-By: apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Received: from [207.172.4.62] (HELO smtp02.mrf.mail.rcn.net) (207.172.4.62)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jan 2006 13:39:05 -0800
Received: from pool-68-237-29-110.ny325.east.verizon.net (HELO [192.168.0.7]) ([68.237.29.110])
  by smtp02.mrf.mail.rcn.net with ESMTP; 03 Jan 2006 16:38:42 -0500
X-IronPort-AV: i="3.99,326,1131339600"; 
   d="scan'208,217"; a="191070132:sNHT152861936"
Message-ID: <43BAEEEC.9030504@greenjaguar.com>
Date: Tue, 03 Jan 2006 16:38:52 -0500
From: Helena Edelson <helena@greenjaguar.com>
Organization: GreenJaguar
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To:  user@forrest.apache.org
Subject: Re: the forrest.properties-sitemap connection
References: <43BAC8C7.5070908@greenjaguar.com> <43BAE451.2010201@apache.org>
In-Reply-To: <43BAE451.2010201@apache.org>
Content-Type: multipart/alternative;
 boundary="------------080403020001030404080507"
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

This is a multi-part message in MIME format.
--------------080403020001030404080507
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

THank you for taking the time to pass along this immensely clear beta.
 
Helena


Ross Gardler wrote:

> Helena Edelson wrote:
>
>> Hi,
>>
>> What is actually reading the forrest.properties data?
>> I am trying to understand if there is more extendability for the 
>> parameters, for example:
>> forrest.validate.skinconf.includes=${skinconf-file}
>> i.e. what in the Forrest engine is parsing and using this or is it 
>> Cocoon?
>
>
> forrest.properties is a mixture of properties used during the 
> initialisation of the application and during the actually execution.
>
> The validate properties, like the one you select as an example, are 
> used by the ANT script that runs Forrest. Others, such as 
> "project.skin" are made available at runtime via a Cocoon Input 
> Module, which is configured in the forrest.xconf file.
>
>> Taking the question a step further, is it possible then to define new 
>> settings in forrest.properties?
>> example:
>> *project.data=${project.content-dir}/content/data*
>> and if so how might this be referenced in sitemap?
>
>
> Add your property to forrest.properties. If you want to provide a 
> default setting add it to FORREST_HOME/main/default.forrest.properties.
>
> Now find the following element in 
> FORREST_HOME/main/webapp/WEB-INF/xconf/forrest.xconf:
>
> <component-instance name="project" 
> class="org.apache.forrest.conf.ForrestConfModule">
>
> Inside this element there is a <valued> element. Add the following as 
> a child of that element:
>
> <data>@project.data@</data>
>
> Now you can access the value in your sitemap as {project:data}
>
> Couple of points to note:
>
> 1 - Forrest must be restarted to register these changes.
> 2 - When upgrading Forrest the changes to forrest.xconf will be lost, 
> make a local backup as soon as you have it working (something like 
> local.forrest.xconf.backup), this way, it doesn't matter if you forget 
> during upgrade, you will still have a copy.
>
> NOTE:
>
> There is a new config system being developed in 0.8-dev that will 
> simplify this process and allow projects to arbitrarily add properties 
> without editing core files. It is currently working in SVN head, if 
> you are interested join us on the dev list.
>
> Ross
>
>

--------------080403020001030404080507
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font size="-1"><font face="Verdana">THank you for taking the time to
pass along this immensely clear beta.<br>
&nbsp;</font></font><font size="-1"><font face="Verdana"><br>
</font></font>Helena<br>
<br>
<br>
Ross Gardler wrote:
<blockquote cite="mid43BAE451.2010201@apache.org" type="cite">Helena
Edelson wrote:
  <br>
  <blockquote type="cite">Hi,
    <br>
    <br>
What is actually reading the forrest.properties data?
    <br>
I am trying to understand if there is more extendability for the
parameters, for example:
    <br>
forrest.validate.skinconf.includes=${skinconf-file}
    <br>
i.e. what in the Forrest engine is parsing and using this or is it
Cocoon?
    <br>
  </blockquote>
  <br>
forrest.properties is a mixture of properties used during the
initialisation of the application and during the actually execution.
  <br>
  <br>
The validate properties, like the one you select as an example, are
used by the ANT script that runs Forrest. Others, such as
"project.skin" are made available at runtime via a Cocoon Input Module,
which is configured in the forrest.xconf file.
  <br>
  <br>
  <blockquote type="cite">Taking the question a step further, is it
possible then to define new settings in forrest.properties?
    <br>
example:
    <br>
*project.data=${project.content-dir}/content/data*
    <br>
and if so how might this be referenced in sitemap?
    <br>
  </blockquote>
  <br>
Add your property to forrest.properties. If you want to provide a
default setting add it to FORREST_HOME/main/default.forrest.properties.
  <br>
  <br>
Now find the following element in
FORREST_HOME/main/webapp/WEB-INF/xconf/forrest.xconf:
  <br>
  <br>
&lt;component-instance name="project"
class="org.apache.forrest.conf.ForrestConfModule"&gt;
  <br>
  <br>
Inside this element there is a &lt;valued&gt; element. Add the
following as a child of that element:
  <br>
  <br>
&lt;data&gt;@project.data@&lt;/data&gt;
  <br>
  <br>
Now you can access the value in your sitemap as {project:data}
  <br>
  <br>
Couple of points to note:
  <br>
  <br>
1 - Forrest must be restarted to register these changes.
  <br>
2 - When upgrading Forrest the changes to forrest.xconf will be lost,
make a local backup as soon as you have it working (something like
local.forrest.xconf.backup), this way, it doesn't matter if you forget
during upgrade, you will still have a copy.
  <br>
  <br>
NOTE:
  <br>
  <br>
There is a new config system being developed in 0.8-dev that will
simplify this process and allow projects to arbitrarily add properties
without editing core files. It is currently working in SVN head, if you
are interested join us on the dev list.
  <br>
  <br>
Ross
  <br>
  <br>
  <br>
</blockquote>
</body>
</html>

--------------080403020001030404080507--