There's very little in Tapestry that could not be readily built in
Tapestry; it's not that what you are doing is impossible, it's just
that there hasn't been a sufficient need to streamline access to this
configuration symbol.
On Sat, Jul 21, 2012 at 8:47 AM, sommeralex <alexander.som...@gmail.com> wrote:
> @Value("${tapestry.production-mode}")
> @Property
> private boolean productionMode;
>
> this way sounds much easier than the crpytic form in the constructor:
>
> public class MyService implements MyServiceInterface
> {
> public MyService(@Value("${tapestry.production-mode}") boolean
> productionMode, ...)
> {
> if (productionMode) {
>
> can someone explain me why app properties can not more easiliy requested?
>
>
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Test-if-production-or-test-mode-tp5714658.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
