You can do it with a little fiddling, but Tapestry is a bit conservative in
exposing this part of the API, see:
https://issues.apache.org/jira/browse/TAP5-838
Also, there is a wiki article as well with some helpful hints:
http://wiki.apache.org/tapestry/Tapestry5HowToReadSymbolsFromPropertiesFile
On Sun, Feb 20, 2011 at 6:34 AM, Vangel V. Ajanovski wrote:
> If you already use a database in the project and if the project is depending
> on the operation of the database, than I would say that there is no reason
> that is sufficient to justify the use of a property file beside the
> database.
On Sun, Feb 20, 2011 at 5:34 AM, Ulrich Stärk wrote:
> There is a SymbolProvider for properties files in the non-public parts of the
> API. Have a look at that.
I'm using those in a few places where I need to set a value once
before the app is started. However, I was wanting something that
woul
On 19.02.2011 16:36, Mark wrote:
I have an application that requires a great deal of configuration data
after the app is running and needs to be configurable by the end user
from within the application This includes things like Facebook admin
id, Twitter account info, Mailchimp api key, etc.
So
There is a SymbolProvider for properties files in the non-public parts of the
API. Have a look at that.
Uli
On 19.02.2011 16:36, Mark wrote:
> I have an application that requires a great deal of configuration data
> after the app is running and needs to be configurable by the end user
> from wit
Ok thats what I've started using, but I wanted to make sure there wasn't
some built in Tapestry capability to write back to properties files. I'd
rather not re-invent the wheel when I don't have to.
Thanks!
Mark
On Sat, Feb 19, 2011 at 2:11 PM, Werner Keil wrote:
> It's non trivial, but Apac
It's non trivial, but Apache Commons Config worked for us in another project
(With Selenium2, not Tapestry, but it should work for the web container just
as well as the Functional Web Test[?])
