What are you trying to accomplish? Tapestry already has great mechanisms for extending the request processing behavior, including dealing with thrown exceptions. That's why such methods are final, to encourage you to look in the correct place.
On Wed, Jun 2, 2010 at 10:14 AM, Dmitry Gusev <dmitry.gu...@gmail.com> wrote: > I need to override this method to wrap it with try/catch but can't do it > right now. > > Is there any reason why this method was declared final? > > -- > Dmitry Gusev > > AnjLab Team > http://anjlab.com > -- 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
