Great Wiki ! Thx for sharing !
Hugues

On Thu, Sep 18, 2008 at 1:22 PM, Ulrich Stärk <[EMAIL PROTECTED]> wrote:

> Here you go:
> http://wiki.apache.org/tapestry/Tapestry5HowToReadSymbolsFromPropertiesFile
>
> Cheers,
>
> Uli
>
> Peter Stavrinides schrieb:
>
>  Thats great thanks for sharing!
>>
>> ----- Original Message -----
>> From: "Ulrich Stärk" <[EMAIL PROTECTED]>
>> To: "Tapestry users" <users@tapestry.apache.org>
>> Sent: Thursday, 18 September, 2008 11:44:30 AM GMT +02:00 Athens, Beirut,
>> Bucharest, Istanbul
>> Subject: Re: [T5] loading tapestry configuration from properties file?
>>
>> I wrote a SymbolProvider that reads a properties file either from
>> classpath or a filesystem location. I'm going to write a wiki howto about it
>> today.
>>
>> Uli
>>
>> Neeme Praks schrieb:
>>
>>> Hi,
>>>
>>> I know Tapestry5 really pushes the convention-over-configuration
>>> approach, but lets face it - in every non-trivial application you
>>> eventually need to configure stuff. If not directly tapestry-related
>>> properties, then at least your application.
>>>
>>> By default, Tapestry seems to suggest that everybody should start using
>>> web.xml for all such configuration purposes. At least that's the
>>> impression that I get when looking at
>>> http://tapestry.apache.org/tapestry5/guide/conf.html.
>>>
>>> However, I don't particularly like the overly-verbose web.xml style of
>>> configuring plain-simple properties - I'd rather use (the much more
>>> concise) properties file syntax for that.
>>>
>>> Is it possible to tell to Tapestry: "please load all properties from
>>> WEB-INF/myapp.properties"?
>>>
>>> If not, can someone give some pointers on how to implement it?
>>> (it would also be a welcome "out-of-the-box" addition to Tapestry5)
>>>
>>> Rgds,
>>> Neeme
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to