Tapestry ignores static fields when performing instrumentation. I often use static final fields. If you make them public, you can access them from the template as if they were a property.
On Wed, Jan 9, 2013 at 11:34 PM, bhorvat <horvat.z.bo...@gmail.com> wrote: > Is there any reason not to use static final something in the page classes? > > I want to introduce some const field that is only needed in the page class > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Reason-not-to-use-static-final-tp5719227.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
