Hi, Ok, I found the solution to my problem. It's not directly related to Shiro, the issue was coming from a bad integration between jersey and spring. My jersey servlet was defined with
<servlet-class>com.sun.jersey.spi.container.servlet.ServletContainer</servlet-class> when it should have been <servlet-class>com.sun.jersey.spi.spring.container.servlet.SpringServlet</servlet-class> Here is a link to a guide that shows how to integrate jersey with spring: http://www.mkyong.com/webservices/jax-rs/jersey-spring-integration-example/ For Shiro annotations, the information in this thread helped me to get everything working: http://stackoverflow.com/questions/7743749/shiro-authorization-permission-check-using-annotation-not-working Philippe D. On Wednesday 22 May 2013 at 09:18, Philippe Deslauriers wrote: > Him > > I tried to delete the line as well as to mimic as much as possible the sample > context xml, but still no result. For now I will "upgrade" the sample to make > it closer to my setup until it breaks, it should help me to find my mistake. > I'll get back to you next week with the result. > > Thanks for your help, > Philippe D. > > > On Tuesday 21 May 2013 at 18:00, Harald Wellmann wrote: > > > Have you tried running the Spring-Hibernate sample from the Shiro source > > repository? The Hibernate part is probably not relevant to your use > > case, but the Spring configuration might help you. > > > > This sample does NOT use AspectJ, and that may be the reason why your > > setup doesn't work. > > > > In other words, Spring and Shiro do support AspectJ but don't require > > it, so unless your own application relies on AspectJ, I'd say you're > > better off without it. > > > > Can you try deleting > > > > <aop:aspectj-autoproxy proxy-target-class="true" /> > > > > from your Spring context? > > > > The DefaultAdvisorAutoProxyCreator bean should be sufficient to create > > proxies and advice for your Shiro annotations. > > > > Best regards, > > Harald > > > > > > > >
