Shiro starts to shine when the features you need are not provided by the other authentication and authorization frameworks, e. g. NoSQL support or your users and roles are in different relational databases or one authentication framework to serve web and non-web applications simultaneously. These use cases are fairly easy to write up and integrate yourself with Shiro whereas container authentication or Spring Security pretty much block you from any use case but the ones provided - and slight variations thereof.
-- View this message in context: http://shiro-user.582556.n2.nabble.com/Simple-instructions-on-Shiro-with-GWT-application-tp7580560p7580565.html Sent from the Shiro User mailing list archive at Nabble.com.
