[
https://issues.apache.org/jira/browse/CMIS-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14345422#comment-14345422
]
Florian Müller commented on CMIS-888:
-------------------------------------
The repository info cache implementation is not meant to be configurable.
And, again, it wouldn't help you much as long as you don't also keep the
content of the type definition cache. The best way is store the whole session
object.
If you want full control, including the repository infos, you have to build a
custom binding or a custom session factory that uses your own {{CmisBinding}}
object.
> Make RepositoryInfo Cacheable
> -----------------------------
>
> Key: CMIS-888
> URL: https://issues.apache.org/jira/browse/CMIS-888
> Project: Chemistry
> Issue Type: Improvement
> Components: opencmis-client-bindings
> Affects Versions: OpenCMIS 0.12.0
> Reporter: Francesco Uliana
> Priority: Minor
>
> each time I create a new org.apache.chemistry.opencmis.client.api.Session
> with
> org.apache.chemistry.opencmis.client.runtime.SessionFactoryImpl#createSession(..)
> the cmis client perform an HTTP GET request to
> "/alfresco/api/-default-/public/cmis/versions/1.1/atom?repositoryId=-default".
> The response from alfresco is always the same, could you allow some kind of
> policy to cache globally RepositoryInfo?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
