> Wouldn't it make more sense then to have ShiroFilter subclasses that > perform configuration-specific activities instead of complicating > things with this 'WebConfiguration' concept? > > That is, IniShiroFilter (ini-specific config), GroovyShiroFilter, > SpringShiroFilter, GuiceShiroFilter, etc.
I'm pretty confused now, but the above seems like the wrong way to go. Shiro configuration and a web/servlet filter seem to be orthogonal concerns, so wrapping them together into an inheritance hierarchy seems wrong. However, since I am confused, I'll ask a few questions that might clear things up for me: 1. Is ShiroFilter intended to be a servlet filter? 2. If not, what is it? Thanks, Peter
