OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cmis message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Commented: (CMIS-480) Clarify the reaction ofgetTypeDefintion if a type is requested that doesn't exist



    [ http://tools.oasis-open.org/issues/browse/CMIS-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17367#action_17367 ] 

Al Brown commented on CMIS-480:
-------------------------------

JIRA Cleanup

> Clarify the reaction of getTypeDefintion if a type is requested that doesn't exist
> ----------------------------------------------------------------------------------
>
>                 Key: CMIS-480
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-480
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Domain Model, REST/AtomPub Binding, Web Services Binding
>    Affects Versions: Draft 0.63
>            Reporter: Florian Mueller
>            Assignee: Ryan McVeigh
>             Fix For: Committee Draft 04
>
>
> It's not clearly defined what should happen if getTypeDefintion is called with a type id that doesn't exist. The current WSDL indicates that it could return nothing in this case or throw a (not specified) exception.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]