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 2013/03/24 13:57:15 UTC
[jira] [Assigned] (SLING-2796) Support refreshing of resource
providers
[ https://issues.apache.org/jira/browse/SLING-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler reassigned SLING-2796:
---------------------------------------
Assignee: Carsten Ziegeler
> Support refreshing of resource providers
> ----------------------------------------
>
> Key: SLING-2796
> URL: https://issues.apache.org/jira/browse/SLING-2796
> Project: Sling
> Issue Type: Bug
> Components: API, JCR, ResourceResolver
> Affects Versions: JCR Resource 2.2.4, API 2.3.0, Resource Resolver 1.0.4
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: JCR Resource 2.2.6, API 2.4.0, Resource Resolver 1.1.0
>
>
> We should add a method refresh() to the resource resolver which delegates this call to all resource providers implementing the RefreshableResourceProvider (or is there a better name?)
> Some data storages like JCR (especially with the upcoming Oak implementation) might give you the state of the storage from the time the login happened. Therefore we need a way to get the latest state. In JCR this is done through the refresh method. With adding this for resource providers we can support this for all resource providers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira