Great investigation ! I hope this will solve the "deprecated api" issue.
I've another issue due to the fact that ShiroModule is a private module. I do not know how to expose one of my custom realm. I need to inject some elements in it from another module. I've seen that there is a work around but I'm sure to know how to use it in that case : http://markmail.org/message/pvjcz5akerw3ynae#query:+page:1+mid:pvjcz5akerw3ynae+state:results maybe you can help me on that point. Another point I've seen in the ShiroModule code is that you encapsulate guice multibinding mechanism in the bindRealm() function. IMHO, I'm not sure this is a good idea because end users need to know which mechanism is used behind. I think that the main goal of the shiro-guice library is to encapsulate internal configuration of shiro but not guice mechanisms and particularly on this part directly used by the end users. I don't think that end users that choose to use guice will be afraid to write : Multibinder<Realm> multibinder = Multibinder.newSetBinder(binder(), Realm.class); multibinder.addBinding().to(MyCustomRealm1); multibinder.addBinding().to(MyCustomRealm2); Thanks in advance for your help. -- View this message in context: http://shiro-user.582556.n2.nabble.com/Guice-shiro-jersey-tp6673315p6695831.html Sent from the Shiro User mailing list archive at Nabble.com.
