cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrey Razumovsky (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAY-1400) lazyInitParentDomainName will become null when using Child Context
Date Fri, 05 Mar 2010 10:24:32 GMT

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


Mime
View raw message