You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by "Andrus Adamchik (JIRA)" <ji...@apache.org> on 2013/09/19 10:12:00 UTC

[jira] [Comment Edited] (CAY-1850) ROP: server context bound to client channel doesn't rollback changes in case of commit failure

    [ https://issues.apache.org/jira/browse/CAY-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771681#comment-13771681 ] 

Andrus Adamchik edited comment on CAY-1850 at 9/19/13 8:11 AM:
---------------------------------------------------------------

I guess this can be made a  property governing context assignment behavior, as generally we support stateful apps that can store changes on the server between requests. Here is an idea - the property doesn't have to be about rollback, but rather it can specify that the client wants a fresh context on every request, instead of using a session one?
                
      was (Author: andrus):
    I guess this should be made a context property, as generally we support stateful apps that can store changes on the server between requests. Here is an idea - the property doesn't have to be about rollback, but rather it can specify that the client wants a fresh context on every request, instead of using a session one?
                  
> ROP: server context bound to client channel doesn't rollback changes in case of commit failure
> ----------------------------------------------------------------------------------------------
>
>                 Key: CAY-1850
>                 URL: https://issues.apache.org/jira/browse/CAY-1850
>             Project: Cayenne
>          Issue Type: Bug
>          Components: ROP
>    Affects Versions: 3.1B2
>            Reporter: Dzmitry Kazimirchyk
>
> When commit containing new object passes validation on client and then fails on server, server context instance handling all client's ROP requests doesn't rollback the changes therefore every consecutive ROP commit from the same client channel will fail.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira