On Wed, May 6, 2009 at 1:25 PM, Kent Larsson <kent.lars...@gmail.com> wrote: > Hi, > > I'm having some trouble getting method security to work as expected > using Spring Security together with Wicket, I have a thread about it > over at the SpringSource forum: > http://forum.springsource.org/showthread.php?t=71397 . > > Basically I have this situation: > 1. Unauthenticated user submits a form, the onSubmit method calls a > method in a Spring singleton which is secured using method security by > a @Secured("NON_EXISTING_ROLE") annotation. > 2. At this point, the method call is intercepted by Spring and I > _think_ I should get the option to log in here. However I do not get > this option, instead I'm shown a stack trace. > > I'm really banging my head against the wall here. I just wanted to ask > here if this could have anything with the Wicket-Spring-IOC project? > > I would suspect no and that I'm to blame, but I'm also having a really > hard time finding the source of the problem. If you have any tip for > my as well I would really appreciate it! ;-)
I don't usually use spring security in that way with Wicket. I use wicket-auth-roles and the annotations it comes with to secure at the page/component level. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
