i was also having issues with spring-security. The @secured annotation is not being processed however u could still secured the pages contributing the FilterSecurityInterceptor. I was able to find out why the annotation was not being processed,l i am still trying to understand some of the ioc behaviors.
On Wed, Mar 25, 2009 at 4:27 AM, Anthony Schexnaildre <apsch...@gmail.com>wrote: > Someone else mentioned that they were having issues with the same thing no > more than a week ago. I don't remember them having a solution either. > > -Anthony > > > On Mar 24, 2009, at 10:23 PM, Thiago H. de Paula Figueiredo wrote: > > Hi! >> >> Is it just me or Tapestry-Spring-Security doesn't work with Tapestry >> 5.1.0.x? I tried to use the @Secured annotation in a class, using a >> non-existent role, and the page was rendered normally when it should >> redirect to the login page. Changing to T5.0.18 makes everything work as >> expected. >> >> -- >> Thiago H. de Paula Figueiredo >> Independent Java consultant, developer, and instructor >> http://www.arsmachina.com.br/thiago >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> >
