chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ramasamy, Sud" <>
Subject RE: SOAP GetContentStream and extensions in the response
Date Mon, 06 Jun 2016 18:00:08 GMT
So sounds like the limitation we have is that the other bindings don't have a way to support
extensions in the response for getContentStream. So it wouldn't make sense to introduce this
for the SOAP binding since the code impact is common to all the bindings.

Thanks for the clarification and helpful hints.


-----Original Message-----
From: Florian Müller [] 
Sent: Saturday, June 04, 2016 11:12 AM
To:; Ramasamy, Sud
Subject: Re: SOAP GetContentStream and extensions in the response

Hi Sud,

the intention of the CMIS spec is that a client calls getObject and getContentStream separately.

Technically (although not implemented in OpenCMIS), it would be possible to transport additional
data with the content with the Web Services binding. But that is not standardized and wouldn't
work with the other bindings. I would advised against it.

- Florian

> I see that the current code for the ObjectService.GetContentStream operation does not
support returning extensions in the SOAP response. The use case we are trying to implement
is to return the content stream along with the document metadata in the same response.
> Any suggestions how we should approach this. Does it make sense to enhance GetContentStream
to support extensions in the response? Or is there a different operation that is more appropriate
for our use case or should simply using GetContentStream and GetObject with two separate calls
to get both content and metadata?
> -sud
> The information contained in this message may be CONFIDENTIAL and is for the intended
addressee only.  Any unauthorized use, dissemination of the information, or copying of this
message is prohibited.  If you are not the intended addressee, please notify the sender immediately
and delete this message.

View raw message