shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Demers <>
Subject Re: ExceptionCatchingModularRealmAuthorizer ?
Date Thu, 14 Apr 2011 15:45:11 GMT
Yeah, changing the Realm interface defiantly violates the versioning
guidelines.  Is there anything saying the next release cannot be 2.0
(granted that doesn't change the problem here)

On the plus side, I think my ExceptionCatchingModularRealmAuthorizer
was the only think that broke, which highlights a contribution.

On Tue, Apr 12, 2011 at 2:24 PM, Les Hazlewood <> wrote:
> Refactoring the ModularRealmAuthorizer to use the Strategy design
> pattern (like the ModularRealmAuthenticator) is probably the best
> approach.  This allows pluggable strategies to be used so you don't
> need to subclass.
> As far as SHIRO-231 is concerned, I agree with it, but I really think
> we need to revert that change until 2.0.  We should not introduce
> fundamental (breaking) API changes in a minor version release.  (This
> is the reason for the APR versioning guidelines at least).  Thoughts?
> Les

View raw message