ok, thanks a lot. I don't care if it has to be in my own properties file
or not. I just want it easy to edit/chage. Now I work this way with your
hint:
1. define the parameter as context-param in web.xml, eg. myParam
2. inject it in my page class:
@Inject
@Value("${myParam}")
String myParam;
Then I can use myParam in the page/service class very conveniently. pls
let me know if there is any problem with this way. thanks.
δΊ 2012/4/24 23:07, Lance Java ει:
There is no silver bullet solution for this and it's a matter of taste.
Tapestry has a number of built in SymbolProviders. You can specify a
combination of system properties, init-params to the tapestry filter,
factory defaults and application defaults
http://tapestry.apache.org/symbols.html
If you would like to configure your symbols in a properties file, there is
a HowTo page here:
http://wiki.apache.org/tapestry/Tapestry5HowToReadSymbolsFromPropertiesFile
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
