You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chemistry.apache.org by "Florent Guillaume (JIRA)" <ji...@apache.org> on 2010/09/23 17:41:34 UTC
[jira] Created: (CMIS-253) Make doc.getContentStream return null
when there's no content stream
Make doc.getContentStream return null when there's no content stream
--------------------------------------------------------------------
Key: CMIS-253
URL: https://issues.apache.org/jira/browse/CMIS-253
Project: Chemistry
Issue Type: Improvement
Affects Versions: 0.1.0-incubating
Reporter: Florent Guillaume
Assignee: Florent Guillaume
Fix For: 0.2.0-incubating
The domain model says that getContentStream should throw a CmisConstraintException when there is no content stream or rendition stream.
For the bindings this should mean CmisConstraintException, although the AtomPub bindings currently return a CmisNotSupportedException due to the missing link.
For the session I think doc.getContentStream() should return null in that case instead of throwing.
The other exceptions would be let through. Only for the case where the repository returns a non-specified CmisConstraintException would we have an ambiguity, but I don't think it would be problematic as the end-result would still be the same: no content stream available.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CMIS-253) Make doc.getContentStream return null
when there's no content stream
Posted by "Florent Guillaume (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CMIS-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Florent Guillaume resolved CMIS-253.
------------------------------------
Resolution: Fixed
Implemented.
http://svn.apache.org/viewvc?rev=1000580&view=rev
> Make doc.getContentStream return null when there's no content stream
> --------------------------------------------------------------------
>
> Key: CMIS-253
> URL: https://issues.apache.org/jira/browse/CMIS-253
> Project: Chemistry
> Issue Type: Improvement
> Affects Versions: 0.1.0-incubating
> Reporter: Florent Guillaume
> Assignee: Florent Guillaume
> Priority: Minor
> Fix For: 0.2.0-incubating
>
>
> The domain model says that getContentStream should throw a CmisConstraintException when there is no content stream or rendition stream.
> For the bindings this should mean CmisConstraintException, although the AtomPub bindings currently return a CmisNotSupportedException due to the missing link.
> For the session I think doc.getContentStream() should return null in that case instead of throwing.
> The other exceptions would be let through. Only for the case where the repository returns a non-specified CmisConstraintException would we have an ambiguity, but I don't think it would be problematic as the end-result would still be the same: no content stream available.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CMIS-253) Make doc.getContentStream return null
when there's no content stream
Posted by "Florent Guillaume (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CMIS-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Florent Guillaume updated CMIS-253:
-----------------------------------
Priority: Minor (was: Major)
> Make doc.getContentStream return null when there's no content stream
> --------------------------------------------------------------------
>
> Key: CMIS-253
> URL: https://issues.apache.org/jira/browse/CMIS-253
> Project: Chemistry
> Issue Type: Improvement
> Affects Versions: 0.1.0-incubating
> Reporter: Florent Guillaume
> Assignee: Florent Guillaume
> Priority: Minor
> Fix For: 0.2.0-incubating
>
>
> The domain model says that getContentStream should throw a CmisConstraintException when there is no content stream or rendition stream.
> For the bindings this should mean CmisConstraintException, although the AtomPub bindings currently return a CmisNotSupportedException due to the missing link.
> For the session I think doc.getContentStream() should return null in that case instead of throwing.
> The other exceptions would be let through. Only for the case where the repository returns a non-specified CmisConstraintException would we have an ambiguity, but I don't think it would be problematic as the end-result would still be the same: no content stream available.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.