Hi devs, In order to manage authorization access based on the signature of scripts, I need to have better knowledge on which rendering is being processed at any moment. The rendering is the one who knows the better the current rendering status, so it is also the best place to feed the ExecutionContext with the TransformationContext and the MacroTransformationContext. Therefore, I would like to introduce a dependency on xwiki-commons-context into xwiki-rendering-api. Since xwiki-commons-context does not have any transitive dependencies, and is part of commons, it should not be an issue. This is not a proposal to remove the current usage of the rendering contexts, it will not impose existing user of the rendering project to embrace the EC at all. If nobody complains, I am starting working on this now, so please comment ASAP if you are against. Thanks -- Denis Gervalle SOFTEC sa - CEO _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Hi devs, In order to manage authorization access based on the signature of scripts, I need to have better knowledge on which rendering is being processed at any moment. The rendering is the one who knows the better the current rendering status, so it is also the best place to feed the ExecutionContext with the TransformationContext and the MacroTransformationContext. Therefore, I would like to introduce a dependency on xwiki-commons-context into xwiki-rendering-api. Since xwiki-commons-context does not have any transitive dependencies, and is part of commons, it should not be an issue. This is not a proposal to remove the current usage of the rendering contexts, it will not impose existing user of the rendering project to embrace the EC at all. If nobody complains, I am starting working on this now, so please comment ASAP if you are against. Thanks -- Denis Gervalle SOFTEC sa - CEO