+1 I would also vote to deprecate Api.hasProgrammingRights in favor of XWiki.hasProgrammingRights() if it is possible.. It's not a very good idea to have these APIs in Api.. I don't know why I had this crazy idea Ludovic Jean-Vincent Drean a écrit : -- Ludovic Dubost Blog: http://www.ludovic.org/blog/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost AIM: nvludo Yahoo: ludovic

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

On Feb 2, 2007, at 7:53 PM, Sébastien Gaïde wrote: I think Rights is a cross cutting concern that spans across both Users and Documents (and possibly other stuff too). I would definitely see it as a component in itself and not inside either User nor Documents. In this way it's nicely decoupled and could be implemented in different manner in the future: using a rule engine, using AOP, etc. Thanks -Vincent ___________________________________________________________________________ Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire. http://fr.mail.yahoo.com

for XWiki 2.0. I'd say both functions are useful, but not necessary. But this is something particular, meaning that no other APIs should alter existing APIs, so that different modules can be easily decoupled. So, I'd say that by XWiki 2.0 we should have the second method, and add the first method only if many developers want it. -- http://purl.org/net/sergiu