You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by "Tsutomu YANO (JIRA)" <ji...@apache.org> on 2010/03/03 14:20:33 UTC

[jira] Created: (CAY-1400) lazyInitParentDomainName will become null when using Child Context

lazyInitParentDomainName will become null when using Child Context
------------------------------------------------------------------

                 Key: CAY-1400
                 URL: https://issues.apache.org/jira/browse/CAY-1400
             Project: Cayenne
          Issue Type: Bug
          Components: Core Library
    Affects Versions: 3.0RC2
         Environment: every platform
            Reporter: Tsutomu YANO


lazyInitParentDomainName field of DataContext is used to revive EntityResolver in the context. But the field become null on Child Context. So Child Context's EntityResolver will be lost at deserialized time.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (CAY-1400) lazyInitParentDomainName will become null when using Child Context

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

Andrey Razumovsky reassigned CAY-1400:
--------------------------------------

    Assignee: Andrey Razumovsky

OK I see the problem:

        DataContext context = createDataContextWithSharedCache();
        ObjectContext child = context.createChildContext();

        ObjectContext deserializedContext = (ObjectContext) Util.cloneViaSerialization(child);

        assertNotNull(deserializedContext.getChannel());
        assertNotNull(deserializedContext.getEntityResolver());

> lazyInitParentDomainName will become null when using Child Context
> ------------------------------------------------------------------
>
>                 Key: CAY-1400
>                 URL: https://issues.apache.org/jira/browse/CAY-1400
>             Project: Cayenne
>          Issue Type: Bug
>          Components: Core Library
>    Affects Versions: 3.0RC2
>         Environment: every platform
>            Reporter: Tsutomu YANO
>            Assignee: Andrey Razumovsky
>
> lazyInitParentDomainName field of DataContext is used to revive EntityResolver in the context. But the field become null on Child Context. So Child Context's EntityResolver will be lost at deserialized time.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (CAY-1400) lazyInitParentDomainName will become null when using Child Context

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

Andrey Razumovsky closed CAY-1400.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0RC3

> lazyInitParentDomainName will become null when using Child Context
> ------------------------------------------------------------------
>
>                 Key: CAY-1400
>                 URL: https://issues.apache.org/jira/browse/CAY-1400
>             Project: Cayenne
>          Issue Type: Bug
>          Components: Core Library
>    Affects Versions: 3.0RC2
>         Environment: every platform
>            Reporter: Tsutomu YANO
>            Assignee: Andrey Razumovsky
>             Fix For: 3.0RC3
>
>
> lazyInitParentDomainName field of DataContext is used to revive EntityResolver in the context. But the field become null on Child Context. So Child Context's EntityResolver will be lost at deserialized time.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (CAY-1400) lazyInitParentDomainName will become null when using Child Context

Posted by "Andrey Razumovsky (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CAY-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841801#action_12841801 ] 

Andrey Razumovsky commented on CAY-1400:
----------------------------------------

This looks weird.. lazyInitParentDomainName is only used when there is no channel defined (to load map at first need). For child contexts, channel is always defined and it is parent context, which should be (de)serialized properly. Can you give an example showing a problem?

> lazyInitParentDomainName will become null when using Child Context
> ------------------------------------------------------------------
>
>                 Key: CAY-1400
>                 URL: https://issues.apache.org/jira/browse/CAY-1400
>             Project: Cayenne
>          Issue Type: Bug
>          Components: Core Library
>    Affects Versions: 3.0RC2
>         Environment: every platform
>            Reporter: Tsutomu YANO
>
> lazyInitParentDomainName field of DataContext is used to revive EntityResolver in the context. But the field become null on Child Context. So Child Context's EntityResolver will be lost at deserialized time.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.