Hi, On Tue, Dec 20, 2016 at 11:50 AM, Stefan Seifert <sseif...@pro-vision.de> wrote: > ...so, what about defining only an "conversion interface" in the Sling API, > limit it per > javadocs to support only a fixes list of types and conversions, and start > with providing > an own implementation in a new bundle based on what is in jcr.resource > today...
+1 on having our own API while the OSGi one stabilizes, and maybe we can already use the Felix implementation that you mention underneath? Temporarily forking that Felix code in Sling is ok and would make it easier to control updates to the parts that we use, without depending on Felix releases of that module. -Bertrand
