Hi, I'm coming to this a bit late - I read the whole thread, hopefully got the idea ;-)
On Fri, Mar 18, 2016 at 8:08 AM, Carsten Ziegeler <cziege...@apache.org> wrote: > ...My rough initial proposal would be: > a) forget about Resource#getResourceSuperType.... > b) the resource hierarchy is not spread across /libs, /apps anymore... > c) we create a dedicated resource tree at /foo... > d) we create a service which has three methods.... The whole thing looks a bit too big to me in terms of "small, reversible changes" - would a simpler definition of those changes work? 1) Forget about Resource#getResourceSuperType as you suggest - IOW it's not the Resource which provides the resource type hierarchy anymore 2) Create a service API that provides the resource type hierarchy Am I correct that this is the core of your proposal? If yes I think where 2) gets its info from can be seen as a separate concern, or maybe as a second phase of these changes. Having minimal changes initially should make it easier to figure out any backwards compatibility issues. -Bertrand
