You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2010/12/13 10:03:01 UTC
[jira] Closed: (SLING-1711) Move SlingAdaptable from adapter bundle
to api
[ https://issues.apache.org/jira/browse/SLING-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-1711.
-----------------------------------
> Move SlingAdaptable from adapter bundle to api
> ----------------------------------------------
>
> Key: SLING-1711
> URL: https://issues.apache.org/jira/browse/SLING-1711
> Project: Sling
> Issue Type: New Feature
> Components: API, Extensions
> Affects Versions: API 2.1.0, Adapter 2.0.6
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: API 2.2.0, Adapter 2.0.8
>
>
> The SlingAdaptable - which is the default implementation for Adaptable - is current in the adapter bundle. The implementation contains some caching.
> As the API should not depend on other Sling bundles, AbstractResource can't extend this implementation. In addition if one wants to use the SlingAdaptable together
> with the Sling API it needs several bundles.
> We can clean this up, by :
> - adding SlingAdaptable to the API
> - deprecate SlingAdaptable in the adapter bundle and let it extend the API version
> - make AbstractResource extend the new SlingAdaptable
> - move the AdapterManager code from AbstractResource to the new SlingAdaptable
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.