[OASIS Issue Tracker] Commented: (CMIS-693) CMIS RepositoryExtensions

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Florent Guillaume commented on CMIS-693:
----------------------------------------

I agree with Florian that having extensions presented as virtual content is cumbersome and not necessary.
They impose lots of special code on the server side when getting documents by id, children, path, by query, etc.
Simply having the extension data in the repository info would be much simpler IMHO.


> CMIS Repository Extensions
> --------------------------
>
>                 Key: CMIS-693
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-693
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: New Feature
>          Components: Domain Model
>    Affects Versions: V1.0
>         Environment: n/a
>            Reporter: Jay Brown
>            Priority: Minor
>
> As discussed in the TC meeting today. I have posted a wiki page describing the best practice for CMIS repository extensions. 
> Anyone interested, please comment. 
> Wiki page here:  http://wiki.oasis-open.org/cmis/Repository%20Extensions

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