[ 
https://issues.apache.org/jira/browse/JCRVLT-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15003837#comment-15003837
 ] 

Robert Munteanu commented on JCRVLT-61:
---------------------------------------

A solution that comes into mind is to establish an absolute ordering for the 
packages. This can for instance be a numeric value - ranking - attached to a 
package, and the packages are processed in natural order of their rankings - 
smaller values first. This will at least make the processing consistent.

Absolute ordering is not without pitfalls - e.g. what happens when two packages 
have the same ranking? Or what happens when you want to process your entries 
between package A ( ranking = 1 ) and package B (ranking = 2 )? So this needs 
more thought.

I have considered relative ordering ( package A installed after package B ) but 
I think this is not going to be maintainable in the long run - packages come 
and go, are refactored, etc. Also, ordering at the ACE level will not be 
maintainable either as there are simply too many entries to consider.

Another thought is to separate ACE setup into phases:

- system
- application
- demo

etc

Each package could declare ACEs as belonging to a phase, which allows more 
fine-grained control over what gets setup when. It's basically a rehash of the 
absolute ordering idea, with predefined phases and allowing a package to 
contribute to more phases. It has the advantage of being more intuitive, but 
less flexible if you need more phases than what we allow.

> Allow AccessControllHandling be defined per filter root
> -------------------------------------------------------
>
>                 Key: JCRVLT-61
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-61
>             Project: Jackrabbit FileVault
>          Issue Type: Improvement
>          Components: Packaging
>            Reporter: Tobias Bocanegra
>
> the current packaging only allows to specify the AccessControllHandling per 
> package. if one requires different behaviors for different content trees, the 
> only workaround today is to create sub-packages.
> it would be nice if the ac-control handling can be defined by workspace 
> filter root, similar to the iImportMode - or even tie the 
> AccessControllHandling to the ImportMode. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to