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 (JIRA)" <ji...@apache.org> on 2013/04/19 17:37:17 UTC
[jira] [Updated] (ISIS-386) Provide the ability to force a reload
of an object by the JDO objectstore.
[ https://issues.apache.org/jira/browse/ISIS-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Haywood updated ISIS-386:
-----------------------------
Description:
This is needed because, it would seem, DataNucleus does not maintain 1:m bidirectional relationships for us, and so we need to be able to re-retrieve the parent object when a child object has just been persisted.
While we are at it, promote the JDO facet factories that set up the ignore of "jdo" prefix (we are already half-way there in ignoring the PersistenceCapable interface).
was:
This is needed because, it would seem, DataNucleus does not maintain 1:m bidirectional relationships for us, and so we need to be able to re-retrieve the parent object when a child object has just been persisted.
While we are at it, promote the JDO facet factories that set up the ignore of "jdo" prefix (we are already half-way there in ignoring the PersistenceCapable interface.
> Provide the ability to force a reload of an object by the JDO objectstore.
> --------------------------------------------------------------------------
>
> Key: ISIS-386
> URL: https://issues.apache.org/jira/browse/ISIS-386
> Project: Isis
> Issue Type: Improvement
> Reporter: Jeroen van der Wal
> Assignee: Dan Haywood
> Priority: Minor
>
> This is needed because, it would seem, DataNucleus does not maintain 1:m bidirectional relationships for us, and so we need to be able to re-retrieve the parent object when a child object has just been persisted.
> While we are at it, promote the JDO facet factories that set up the ignore of "jdo" prefix (we are already half-way there in ignoring the PersistenceCapable interface).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira