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] [Updated] (CAY-1737) ObjectContexts listening to DataChannel events must be non-blocking
Date Sat, 08 Sep 2012 10:18:07 GMT

     [ https://issues.apache.org/jira/browse/CAY-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrus Adamchik updated CAY-1737:
---------------------------------

    Description: 
To solve CAY-957, ObjectContexts listening to DataChannel events must be non-blocking. Documenting
this in a separate Jira to give more exposure to this change in the framework that may have
app consequences. 

The actual logic will be like that - if the EventManager in the runtime is single-threaded,
use blocking events, if it is multi-threaded - use non-blocking.

This affects both ROP CayenneContext and server DataContext

  was:To solve CAY-957, ObjectContexts listening to DataChannel events must be non-blocking.
Documenting this in a separate Jira to give more exposure to this change in the framework
that may have app consequences. 

    
> ObjectContexts listening to DataChannel events must be non-blocking
> -------------------------------------------------------------------
>
>                 Key: CAY-1737
>                 URL: https://issues.apache.org/jira/browse/CAY-1737
>             Project: Cayenne
>          Issue Type: Task
>            Reporter: Andrus Adamchik
>            Assignee: Andrus Adamchik
>             Fix For: 3.1B2, 3.2M1
>
>
> To solve CAY-957, ObjectContexts listening to DataChannel events must be non-blocking.
Documenting this in a separate Jira to give more exposure to this change in the framework
that may have app consequences. 
> The actual logic will be like that - if the EventManager in the runtime is single-threaded,
use blocking events, if it is multi-threaded - use non-blocking.
> This affects both ROP CayenneContext and server DataContext

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