Though it comes with some baggage, integrating Spring would probably still be the path of least resistance for you since its tried and widely used. It's not your only option however; you could also use aspectj support directly. In terms of lines of code, the effort required to write an aspect for securing some service calls is minimal, but learning AOP takes some time if you never used it before. Finally, and I don't know if you want to explore that route, but somebody just wrote a wicket/tapestry-ioc integration module (https://github.com/criedel/WicketTap5IOC) and tapestry-security (http://tynamo.org/tapestry-security+guide) has built-in support for securing services via annotations.
Kalle On Sun, Nov 21, 2010 at 7:21 AM, Fernando Wermus <[email protected]> wrote: > Hi all, > I am using shiro successfully with wicket. But I need to develop > authorization for services in the backend. I am thinking of using some kind > of interceptor, which authorizes the called. We don't use spring and we need > to find a way to develop it with the minimun effort. Is there any solution > that not take into account spring for security and has its all benefits? Or > should we integrate our app with spring? > thanks in advance > > -- > Fernando Wermus. > > www.linkedin.com/in/fernandowermus >
