Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <439D7865.6030607@apache.org>
Date: Mon, 12 Dec 2005 13:17:25 +0000
From: Ross Gardler <rgardler@apache.org>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: dev@forrest.apache.org
Subject: Re: Processing properties in Forrest core (was Re: svn
 commit:	r355634
 -	/forrest/trunk/site-author/forrest.properties.xml)
References: <20051209230735.30011.qmail@minotaur.apache.org>
	 <1134382112.10498.11.camel@localhost>  <439D5BCE.3030402@apache.org>
 <1134388257.10498.19.camel@localhost>
In-Reply-To: <1134388257.10498.19.camel@localhost>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Thorsten Scherler wrote:
> El lun, 12-12-2005 a las 11:15 +0000, Ross Gardler escribi=C3=B3:
>=20
>>Thorsten Scherler wrote:
>>
>>>El vie, 09-12-2005 a las 23:07 +0000, rgardler@apache.org escribi=C3=B3=
:
>>>
>>>
>>>>Author: rgardler
>>>>Date: Fri Dec  9 15:07:30 2005
>>>>New Revision: 355634
>>>>
>>>>URL: http://svn.apache.org/viewcvs?rev=3D355634&view=3Drev
>>>>Log:
>>>>no longer need forrest.properties.xml as plugin will now provide defa=
ults - only need this if you want behaviour other than the default
>>>>
>>>>Removed:
>>>>   forrest/trunk/site-author/forrest.properties.xml
>>>>
>>>
>>>
>>>How can I request all available properties (default and specific)?
>>>cocoon://=C2=BF?=20
>>
>>Right now you can't get the various values. There is only one property =

>>recorded - the one to actually use. The defaults are not recorded,=20
>>unless they are the ones to use.
>>
>>However, this can be changed.
>>
>>The processing of the properties is done in [1]
>>
>>The first value for a given property is the one we record, so we load=20
>>the various config files in the following order:
>>
>>- PROJECT_HOME/forrest.properties.xml (experimental)
>>- PROJECT_HOME/forrest.properties (may be deprecated)
>>- PLUGIN_HOME/default.plugin.properties.xml (experimental)
>>   - iterate over all active plugins
>>- FORREST_HOME/default.forrest.properties.xml (experimental)
>>- FORREST_HOME/default.forrest.properties (may be deprecated)
>>
>>What you could do is modify [1] to record each of those files in a=20
>>separate properties collection and provide a special property request=20
>>for getting a default value.
>>
>>For example:
>>
>>{forrest:default.PROPERTYNAME}
>>
>>would give the default rather than the user supplied one. To enable thi=
s=20
>>all you would have to do is modify getAttribute(...) in [1] to detect=20
>>this special request and process accordingly.
>>
>>If you do this we need to make this part of the naming convention so=20
>>that no property can start with the word "default". There is no=20
>>documentation for this system yet, but I am tracking things via [2]
>>Please be sure to include this issue number in any commits and add note=
s=20
>>to the documentation task associated with that issue.
>>
>=20
>=20
> Hmm, with other words the properties are store in an input module. What=

> I was looking for is an aggregation of the above properties but not in
> an module but as plain xml.=20

OK

> What do you thing what makes more sense, write some custom generator
> that would contact the input module and generate SAX events from the
> properties or simply aggregate them in the sitemap?

I'd go for the generator approach, more efficient which is important=20
given that there may be a large number of separate config files.

In addition, this will access t none-XML properties during the=20
(possible) migration to the XML system.

Ross

>=20
> salu2=20
>=20
>=20
>>Ross
>>
>>[1]=20
>>http://svn.apache.org/repos/asf/forrest/trunk/main/java/org/apache/forr=
est/conf/ForrestConfModule.java
>>[2] http://issues.apache.org/jira/browse/FOR-739
>>