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-758) Discussion of more powerful batch operations for next version


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

Scott Malabarba commented on CMIS-758:
--------------------------------------

Re: 2) in Jay's last comment:

The FileNet API supports a fairly simple way of handling dependencies between objects in a batch. You can force the ID of a new object so that you can generate a reference to an object before the object is persisted in the repository.
In pseudocode it's something like this:

Id folderId = createId();
Id documentId = createId();
A = createFolder(folderId);
B = createDocument(documentId);
C = fileDocument(A, B);
updatingBatch.add(A);
updatingBatch.add(B);
updatingBatch.add(C);

You can also add an object to a batch multiple times to handle bidirectional dependencies.
A = createDocument();
B = createDocument();
B.setProperty("relatedDocument", A);
updatingBatch.add(A);
updatingBatch.add(B);
A.setProperty("relatedDocument", B);
updatingBatch.add(A);

I'm sure not all repositories support forcing IDs. But it might be a reasonable solution as an optional capability if variables get too complicated.

> Discussion of more powerful batch operations for next version
> -------------------------------------------------------------
>
>                 Key: CMIS-758
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-758
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: New Feature
>          Components: Domain Model
>    Affects Versions: Proposals for 2.0
>            Reporter: Jay Brown
>
> Creating this record as a placeholder for discussions on this subject. 
> What additional batch features should we support in v.next? (e.g.  batch Create, Delete, ...) 
> What should they look like? etc. 
> Please comment.

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