2013/3/7 Carsten Ziegeler <[email protected]>: > Therefore I propose we add a simple interface: > public interface ResourceProviderDecorator { > > ResourceProvider decorate(final ResourceProvider provider); > > AttributableResourceProvider decorate(final > AttributableResourceProvider provider); > > ModifyingResourceProvider decorate(final ModifyingResourceProvider > provider); > > QueriableResourceProvider decorate(final QueriableResourceProvider > provider); > > DynamicResourceProvider decorate(final DynamicResourceProvider provider); > }
Rethinking this, I don't think we should decorate a DynamicResourceProvider. A dynamic resource provider is used to find out if the provider (or the underlying storage) is still alive and when the resource resolver is closed, it's used to close the connection (or session). And I don't think we need to decorate an AttributableResourceProvider either - these are used to provide additional attributes to the resource resolver. So far I don't see any use case here. Carsten -- Carsten Ziegeler [email protected]
