[
https://issues.apache.org/jira/browse/CMIS-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florian Müller resolved CMIS-882.
---------------------------------
Resolution: Fixed
Fix Version/s: OpenCMIS 0.13.0
I’ve add a method {{TempStoreOutputStream getTempFileOutputStream(String
repositoryId)}} to the {{CmisServiceFactory}} interface. If it returns
{{null}}, the default (old) implementation kicks in. Otherwise the returned
{{TempStoreOutputStream}} implementation is used to manage the temporary
content.
This only works for the AtomPub and the Browser binding. The Web Services
binding relies on the JAX-WS implementation, which we cannot intercept.
> Allow server implementers to provide their own code to manage temporary
> content
> -------------------------------------------------------------------------------
>
> Key: CMIS-882
> URL: https://issues.apache.org/jira/browse/CMIS-882
> Project: Chemistry
> Issue Type: Improvement
> Components: opencmis-server
> Affects Versions: OpenCMIS 0.12.0
> Reporter: Florian Müller
> Assignee: Florian Müller
> Fix For: OpenCMIS 0.13.0
>
>
> The OpenCMIS server framework stores document content for a short moment in
> main memory or in temporary files when documents are created, document
> content is replaced, or a new document version is added.
> Server implementers can configure where the temporary files are stored and at
> which threshold, but it's not possible to provide an alternative temporary
> storage. There should be a way to plug in code that manages the temporary
> storage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
