Re: [xwiki-dev] [API] Deprecate Api.checkProgrammingRights?

On Feb 2, 2007, at 2:57 PM, Vincent Massol wrote: Let me rephrase that... I agree within the current architecture. I really don't agree that there should be APIs for all possible stuff located in XWiki (i.e. flatten the object tree). My preference would be to have components and that each component has a public API and that API be available from velocity or groovy. We are already stretching the XWiki object too much. Thus any rights check should be done through the Rights manager component. Something like: $container.lookup ("com.xpn.xwiki....RightsManager").hasProgrammingRights() Of course we could register some well known components: $rightsManager.hasProgrammingRights() In Java: public class MyClassRequiringRightsVerifications ... { private RightsManager; ... } Then MyClassRequiringRightsVerifications is registered againt the component manager (Plexus, OSGi, etc) with a dependency on the RightsManager component so that it's injected either in the constructor, in setters or in the field. This is what I'd like to do for XWiki 2.0. Thanks -Vincent ___________________________________________________________________________ Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire. http://fr.mail.yahoo.com