It does not appear to solve the @Secured issue for me under T5.1.0.5.
I still need to add the: contributeComponentClassTransformWorker
method in my AppModules.java. Otherwise, @Secured is ignored.
Norman Franke
Answering Service for Directors, Inc.
www.myasd.com
On May 29, 2009, at 5:32 PM, Thiago H. de Paula Figueiredo wrote:
On Fri, May 29, 2009 at 3:34 PM, Robin Helgelin <lob...@gmail.com>
wrote:
Hi,
Hi!
I've just uploaded a 2.1.0-SNAPSHOT release of
tapestry-spring-security with support for Tapestry 5.1.
We're releasing this as a SNAPSHOT so that we can see that it
actually
works for everybody before we make the final release.
Thank you! Does it solve the @Secured annotation handling? It is
broken in 2.0 when used with T5.1.
--
Thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
