[
https://issues.apache.org/jira/browse/CAUSEWAY-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17743659#comment-17743659
]
Andi Huber commented on CAUSEWAY-3530:
--------------------------------------
Root cause here is a regression introduced since we do detach the Wicket
Viewer's DataTableModel, that forces a model load on any follow up request. In
our delete case, this will result in an attempt to reconstruct the
DataTableModel's owning bookmarked object, which was already deleted.
Not sure yet which directions to explore for solutions. Also this only is an
issue with JDO, whereas JPA works just fine.
Sidenote: For JPA there is no REMOVED state we could detect and hence don't
keep track of with the framework. Magically object deletion, just works fine.
However, for JDO objects we consider the REMOVED state and do have same extra
code to keep track of and honor this state, but yet run into issues.
> Managed Object for Entity: On object refetch, Object-Not-Found should be
> silently ignored
> -----------------------------------------------------------------------------------------
>
> Key: CAUSEWAY-3530
> URL: https://issues.apache.org/jira/browse/CAUSEWAY-3530
> Project: Causeway
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0.0-RC2
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Major
> Fix For: 2.0.0-RC3
>
>
> In
> org.apache.causeway.core.metamodel.object._ManagedObjectEntityHybrid.getPojo()
> we try to detect whether an object was deleted and if so transition its
> state holding ManagedObjectHybrid to REMOVED.
> However, if this detection fails, an error page is shown instead.
> Ways to reproduce (JDO): when you login to simpleapp with secman-admin and go
> to the Role Manager and delete a random role (or one that you just created),
> the subsequent page will not be rendered, and instead an error page is shown
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
