incubator-isis-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Meyer (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ISIS-119) Collections were marked as "resolved", even if a collection has an unresolved collection.
Date Wed, 07 Sep 2011 19:23:09 GMT

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

Kevin Meyer resolved ISIS-119.
------------------------------

       Resolution: Later
    Fix Version/s: 0.2.0-incubating

Will return to this if the current implementation is insufficient.

> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message