Hello all, Some time ago Carsten proposed a new resource provider API [1], which would be more performant, extendable and easier to use. I worked on it for a few weeks and prepared a pull requests containing:
* JcrResourceProvider implemented in the new API, * ResourceResolver refactored to use new type of the resource providers, * a bridge automatically adapting old ResourceProviders into new ones. I tried to change the structure/design of the code without changing the logic (and dozens of corner cases hidden in many ifs ;). Right now the code passes all integration tests. It would be great if you can provide some feedback. This is a lot of code that changes the very heart of the Sling (resource resolver, jcr resource provider), so it would be great if other developers can reserve some time to do the code review. I also prepared implementation of the new Observation API (SLING-4751), but there will be a separate e-mail about that. There is also an idea to use the new Jackrabbit API with its getItemOrNull() method to avoid duplicated call hasItem()/getItem(). Joel Richard prepared an appropriate patch in SLING-4585 [2]. However, the new Jackrabbit API isn’t released yet, so we can merge it later. Best regards, Tomek [1] https://issues.apache.org/jira/browse/SLING-4750 [2] https://issues.apache.org/jira/browse/SLING-4585 -- Tomek Rękawek | Adobe Research | www.adobe.com [email protected]
