s.
Thanks,
DH
- Original Message -
From: "Thiago H. de Paula Figueiredo"
To: "Tapestry users"
Sent: Thursday, March 26, 2009 9:55 PM
Subject: Re: Tapestry-Spring-Security and Tapestry 5.1.0.x
> On Wed, Mar 25, 2009 at 4:18 AM, DH wrote:
>> Maybe caused by Mu
On Wed, Mar 25, 2009 at 4:18 AM, DH wrote:
> Maybe caused by MutableComponentModel#addRenderPhase?
> I don't use T-S-S, but have another role annotation based solution. I can
> work before 5.0.18 too but fail when upgrade to 5.1.0.0.
> I need call MutableComponentModel#addRenderPhase to make it w
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 beha
orker.
Thanks,
DH
- Original Message -
From: "Thiago H. de Paula Figueiredo"
To: "Tapestry users"
Sent: Wednesday, March 25, 2009 10:23 AM
Subject: Tapestry-Spring-Security and Tapestry 5.1.0.x
> Hi!
>
> Is it just me or Tapestry-Spring-Security doesn&#
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 Tape
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
expect
