Felix Meschberger wrote: > (5) Move the o.a.s.api.adapter package to the Sling Adapter module > (which also contains the AdapterManager implementation and the > SlingAdaptable class. Thus the Sling Adapter module would not import > from the Sling API anymore. Instead the Sling API would import from the > Sling Adapter Module. As a consequence the SyntheticResource could > extend the SlingAdaptable class. > Hi,
i think we should keep the API self contained and try to not depend on other parts. On the other hand I agree that there might be use cases where adapting a synthetic resource makes sense. So what about leaving everything as is and return where appropriate sub classes of SyntheticResource which have a proper adaptTo() implementation. We just have to change the api docs for the synthetic resource that adaptTo() might return an object (and not always null) and we're done. Carsten -- Carsten Ziegeler [email protected]
