You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Oscar Bou (JIRA)" <ji...@apache.org> on 2014/01/04 06:49:52 UTC

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

Oscar Bou created ISIS-644:
------------------------------

             Summary: 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)