Em Wed, 30 Sep 2009 19:09:49 -0300, Patrick Moore <patmo...@amplafi.com>
escreveu:
Hi there --
Hi!
1. some inner plumbing modules do make better sense to be hidden away
from non-programmer type's fingers.
I would say that the almost everyting regarding plumbing should be only
touched by programmers.
2. For other modules, we want to allow things like directory paths and
other text configuration to be exposed. (properties file??)
Nothing prevents you to have some service pull configuration data from a
file or any other source.
Is there a standard way to read properties files and match property
names to java bean getter/setters?
There's no such thing out-of-the-box, in Tapestry, but this can be easily
implemented with reflection or, better yet, Tapestry's PropertyConduits. :)
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
