[Registry-dev] Transaction support in the registry

[Paul Fremantle]

+1 from me. We discussed this initially, and I think it makes some sense.

I guess we have a challenge when it comes to APP though. (Maybe some 
funky header extensions?). How does SVN do this?

Paul



Afkham Azeez wrote:
> https://wso2.org/jira/browse/REGISTRY-265
> 
> In Carbon, when a service is deployed, we store service meta data in the 
> registry. These are added as several resources (policies, parameters, 
> properties etc.) If something goes wrong, stale data should not remain 
> in the registry. So we should be able to rollback.
> 
> Azeez
> 
> Sanjiva Weerawarana wrote:
>> What scenario is motivating this feature?
>>
>> Sanjiva.
>>
>> Deepal Jayasinghe wrote:
>>> Hi all,
>>>
>>> I think is it very useful to have the transaction support in the 
>>> registry API level. There will be many instances where we want to do 
>>> transaction like functions in the registry , something like
>>> - Create a resource
>>> - rate that
>>> - Comment on that and etc..
>>>
>>> And one of those operation fails then need to rollback all those 
>>> operations. I know we can do that at the JDBCRegistry level with 
>>> minor changes but it would be great if we can add the transaction  
>>> handling support in to the registry API , then anyone using APP also 
>>> get the advantage of the transaction support.
>>>
>>> Thank you!
>>> Deepal
>>>
>>>
>>>
>>> _______________________________________________
>>> Registry-dev mailing list
>>> Registry-dev at wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
>>>
>>
> 
> 
> _______________________________________________
> Registry-dev mailing list
> Registry-dev at wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
> 

-- 
Paul Fremantle
CTO and Co-Founder, WSO2
OASIS WS-RX TC Co-chair
VP, Apache Synapse

Office: +44 844 484 8143
Cell: +44 798 447 4618

blog: http://pzf.fremantle.org
paul at wso2.com

"Oxygenating the Web Service Platform", www.wso2.com