cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrus Adamchik (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CAY-1850) ROP: server context bound to client channel doesn't rollback changes in case of commit failure
Date Thu, 19 Sep 2013 08:17:52 GMT

    [ 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:16 AM:
---------------------------------------------------------------

I guess this can be made a strategy governing context *assignment* behavior (instead of a
rollback policy), as generally we support stateful apps that can store changes on the server
between requests and rollback may be undesirable in all cases. 

Possible strategies can be these:

1. Context per session (current de-facto strategy)
2. shared cross-user context for onQuery calls, and dedicated request-scoped context for onSync.
3. new context per request
4. any custom strategy...
                
      was (Author: andrus):
    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?
                  
> 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

Mime
View raw message