You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@isis.apache.org by "Dan Haywood (Closed) (JIRA)" <ji...@apache.org> on 2012/01/05 18:30:41 UTC

[jira] [Closed] (ISIS-119) Collections were marked as "resolved", even if a collection has an unresolved collection.

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

Dan Haywood closed ISIS-119.
----------------------------

    
> Collections were marked as "resolved", even if a collection has an unresolved collection.
> -----------------------------------------------------------------------------------------
>
>                 Key: ISIS-119
>                 URL: https://issues.apache.org/jira/browse/ISIS-119
>             Project: Isis
>          Issue Type: Sub-task
>          Components: Runtimes: Dflt: Objectstores: SQL
>    Affects Versions: 0.1.2-incubating
>            Reporter: Kevin Meyer
>            Assignee: Kevin Meyer
>              Labels: jdbc, objectstore, resolve
>             Fix For: 0.2.0-incubating
>
>
> Until now, when an object is loaded, if it has a collection, then that collection is loaded and marked as "Resolved".
> However, if *that* collection had an item with a field that was a collection, then the field collection is not loaded.
> The current implementation tries to resolve recursively. This is probably also not desirable. I think the best is for the parent to leave collection items as "partially resolved" or whatever is most appropriate.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira