topic Re: Using transactions with CMIS & RESTful API in Alfresco Archive

Using transactions with CMIS & RESTful API

andennis — Tue, 04 Dec 2012 10:55:07 GMT

Hi EveryoneI use DotCMIS and RESTful APIs to interact with Alfresco. (.NET app)Is there any way, using CMIS and RESTful APIs, to roll back data modification operations like e.g. folders\document\user\group creation\renaming\deleting?In other words, does Alfresco support transactions in that case?Tha

Re: Using transactions with CMIS & RESTful API

mrogers — Tue, 04 Dec 2012 11:50:24 GMT

No - each webscript invocation is a separate transaction on the server. By the time you get the result over REST the transaction has either been committed or rolled back.

Re: Using transactions with CMIS & RESTful API

andennis — Tue, 04 Dec 2012 12:01:40 GMT

No - each webscript invocation is a separate transaction on the server. By the time you get the result over REST the transaction has either been committed or rolled back.

Thanks a lot for your answer.
Would you please suggest any solution to roll back the modification operations.
For example:
May transaction be used with JavaScript API?
May I have direct access to Alfresco database? Is it good practice?

Re: Using transactions with CMIS & RESTful API

mrogers — Tue, 04 Dec 2012 12:24:34 GMT

Why do you want to roll back?

You can use distributed transactions if you really need to with the Java API. For example folks wrap the Java API with EJB. But its a rare use case that will require it and will require reconfiguration (via Spring) of the transaction manager and the database resource.

Re: Using transactions with CMIS & RESTful API

vikashkaushik — Wed, 07 Jan 2015 05:49:12 GMT

Hi,

Can you please let us know how to reconfigure the transaction manager and the database resource via Spring, so that we will able to rollback the transaction performed when some conditions are met.

The scenario that we need currently is :

1. Creation of document in Alfresco using CMIS
2. Insertion of the details of document in DB

So when DB insertion fails, we need to rollback the document creation transaction.