You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by jblier <ja...@airwidesolutions.com> on 2007/10/02 23:01:20 UTC
T5: Newbie question - Context sensitive properties
Our web application consist in a main framework responsible for session
management and other shared functions and a number or modules loading inside
the main framework.
My question is what would be the best approach to structure the files and
screen in order to load both the main properties and the specific ones
needed for modules.
Currently I have an app.properties file inside WEB-INF and I load the
properties in my Start.tml using "${message:property string}".
So, in order to create a moduleA.tml template that share both app.properties
for the framework and moduleA.properties, what should I do?
--
View this message in context: http://www.nabble.com/T5%3A-Newbie-question---Context-sensitive-properties-tf4558034.html#a13007788
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: T5: Newbie question - Context sensitive properties
Posted by jblier <ja...@airwidesolutions.com>.
Thanks for the information.
I am not looking at folder specific properties. It looks like that
page/component messages iswhat I am looking for.
I found out about
http://tapestry.formos.com/nightly/tapestry5/tapestry-core/guide/parameters.html
document.
Regards,
- Jacques
Howard Lewis Ship wrote:
>
> From Tapestry's point of view, it's just one big web application, divided
> into folders.
>
> So anything global can go in app.properties, and be overriden in any
> page's
> (or component's) message catalog.
>
> So, page "modulea/apage" will be class foo.bar.pages.modulea.APage and
> there
> will be an APage.properties file with it.
>
> There currently isn't support for per-folder properties files (I think
> that's where you're going with this question). There's the page/component
> message catalog, and the global catalog, and that's it.
>
> On 10/2/07, jblier <ja...@airwidesolutions.com> wrote:
>>
>>
>> Our web application consist in a main framework responsible for session
>> management and other shared functions and a number or modules loading
>> inside
>> the main framework.
>>
>> My question is what would be the best approach to structure the files and
>> screen in order to load both the main properties and the specific ones
>> needed for modules.
>>
>> Currently I have an app.properties file inside WEB-INF and I load the
>> properties in my Start.tml using "${message:property string}".
>>
>> So, in order to create a moduleA.tml template that share both
>> app.properties
>> for the framework and moduleA.properties, what should I do?
>> --
>> View this message in context:
>> http://www.nabble.com/T5%3A-Newbie-question---Context-sensitive-properties-tf4558034.html#a13007788
>> Sent from the Tapestry - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
>
> --
> Howard M. Lewis Ship
> Partner and Senior Architect at Feature50
>
> Creator Apache Tapestry and Apache HiveMind
>
>
--
View this message in context: http://www.nabble.com/T5%3A-Newbie-question---Context-sensitive-properties-tf4558034.html#a13022134
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: T5: Newbie question - Context sensitive properties
Posted by Howard Lewis Ship <hl...@gmail.com>.
>From Tapestry's point of view, it's just one big web application, divided
into folders.
So anything global can go in app.properties, and be overriden in any page's
(or component's) message catalog.
So, page "modulea/apage" will be class foo.bar.pages.modulea.APage and there
will be an APage.properties file with it.
There currently isn't support for per-folder properties files (I think
that's where you're going with this question). There's the page/component
message catalog, and the global catalog, and that's it.
On 10/2/07, jblier <ja...@airwidesolutions.com> wrote:
>
>
> Our web application consist in a main framework responsible for session
> management and other shared functions and a number or modules loading
> inside
> the main framework.
>
> My question is what would be the best approach to structure the files and
> screen in order to load both the main properties and the specific ones
> needed for modules.
>
> Currently I have an app.properties file inside WEB-INF and I load the
> properties in my Start.tml using "${message:property string}".
>
> So, in order to create a moduleA.tml template that share both
> app.properties
> for the framework and moduleA.properties, what should I do?
> --
> View this message in context:
> http://www.nabble.com/T5%3A-Newbie-question---Context-sensitive-properties-tf4558034.html#a13007788
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Partner and Senior Architect at Feature50
Creator Apache Tapestry and Apache HiveMind