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 2014/01/24 07:18:37 UTC

[jira] [Commented] (ISIS-643) FrameworkSynchronizer throws NPE on delete of child entity in 1-N relationship

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

Dan Haywood commented on ISIS-643:
----------------------------------

Hi Ranganath 
Thanks for reporting this issue.
So that I can look into it more easily, could you prepare a small example project (eg up on github) that demonstrates the problem for me?
Dan

> FrameworkSynchronizer throws NPE on delete of child entity in 1-N relationship
> ------------------------------------------------------------------------------
>
>                 Key: ISIS-643
>                 URL: https://issues.apache.org/jira/browse/ISIS-643
>             Project: Isis
>          Issue Type: Bug
>          Components: Objectstore: JDO
>    Affects Versions: objectstore-jdo-1.3.0
>            Reporter: Ranganath Chittari
>            Assignee: Dan Haywood
>            Priority: Blocker
>         Attachments: ISIS-JDO-Delete.log, MOrganisation.java, OmOrgExtendedAttr.java
>
>
> Hello,
> Scenario is:
> There is 1-N relationship between MOrganisation and OmOrgExtendedAttr entities. MOrganisation is parent entity and OmOrgExtendedAttr  is child entity.
> OmOrgExtendedAttr cannot exist without MOrganisation.
> MOrganisation can exist without OmOrgExtendedAttr 
> So on delete of MOrganisation, OmOrgExtendedAttr  is also deleted. There is no problem in this case.
> But problem is on delete of OmOrgExtendedAttr . The error that is coming is NullPointerException in FrameworkSynchronizer of isis-objectstore-jdo-datanucleous component for adpater for the POJO.
> Please find attached log and also the java files
> Could you please help on this issue ASAP.
> Thanks
> Ranganath



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