[jira] [Commented] (ISIS-644) Update FrameworkSynchronizer to avoid the "Object not yet known to Isis" exception

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ISIS-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862243#comment-13862243 ] 

ASF subversion and git services commented on ISIS-644:
------------------------------------------------------

Commit 716ea4a00e8f06ffde9e90629cdfacde928f2a10 in branch refs/heads/master from [~oscarbou]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=716ea4a ]

ISIS-644: Update FrameworkSynchronizer to avoid the "Object not yet known to Isis" exception


> Update FrameworkSynchronizer to avoid the "Object not yet known to Isis" exception
> ----------------------------------------------------------------------------------
>
>                 Key: ISIS-644
>                 URL: https://issues.apache.org/jira/browse/ISIS-644
>             Project: Isis
>          Issue Type: Bug
>          Components: Objectstore: JDO
>            Reporter: Oscar Bou
>            Assignee: Oscar Bou
>             Fix For: objectstore-jdo-1.4.0
>
>
> Sometimes the Isis synchronizer has not yet picked up the domain entity and needs to be created.
> It has been detected when using the @Persistent ("dependentElement="true") JDO annotation, such as in:
> @PersistenceCapable
> @Inheritance(strategy = InheritanceStrategy.NEW_TABLE)
> public class TimeScale extends AbstractScale {
>    // {{ TimeScaleLevels (Collection)
>    @Persistent(mappedBy = "timeScale", dependentElement = "true")
>    private SortedSet<PointInTime> timeScaleLevels = new TreeSet<PointInTime>();
>    
>    ...
> }
> The solution is simply to update the ensureRootObject method.
> Replace the "getAdapterManager().getAdapterFor(pojo)" by "getAdapterManager().adapterFor(pojo)" as it will create the adapter if it's still not available to Isis.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)