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 2012/09/08 11:51:07 UTC

[jira] [Created] (CAY-1737) ObjectContexts listening to DataChannel events must be non-blocking

Andrus Adamchik created CAY-1737:
------------------------------------

             Summary: 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. 

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

[jira] [Closed] (CAY-1737) ObjectContexts listening to DataChannel events must be non-blocking

Posted by "Andrus Adamchik (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAY-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrus Adamchik closed CAY-1737.
--------------------------------

    Resolution: Fixed
    
> 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

[jira] [Updated] (CAY-1737) ObjectContexts listening to DataChannel events must be non-blocking

Posted by "Andrus Adamchik (JIRA)" <ji...@apache.org>.
     [ 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