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-372) How should repositoryspecific information be conveyed in WS binding



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

Al Brown commented on CMIS-372:
-------------------------------

JIRA Cleanup

> How should repository specific information be conveyed in WS binding
> --------------------------------------------------------------------
>
>                 Key: CMIS-372
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-372
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>            Reporter: Al Brown
>             Fix For: Draft 0.63
>
>
> Currently in the REST binding, a vendor or client can send additional information on any of the structures due to xs:any in the CMIS types as well as the atom types.
> This is currently not possible in the WS binding due to all the messages not having xs:any.  When xs:any is included on the messages (both in & out) the interface that gets generated is quite unpleasant.  When a type is used as input or output that supports xs:any this is not a large problem.
> However, with Query, all the inputs are primitives/simple types.  There is currently no way for a client to pass in additional information such as 'I know this is being performed on X, and here are some additional parameters to help perform the search in the vendor's namespace'.
> I see three options:
> 1. Do nothing - information extensibility is just not part of the ws binding
> 2. Add another element to the in and out methods (e.g., extension) that supports xs:any inside that element
> 3. Add xs:any to the in & out messages and live with the generation issues
> I prefer the solutions in the following order: 2, 1, 3

-- 
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]