[
https://issues.apache.org/jira/browse/CAUSEWAY-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andi Huber resolved CAUSEWAY-3532.
----------------------------------
Resolution: Resolved
fixed by probing whether entity object is found in UiObjectWkt before trying to
populate the property models;
if not-found, the we throw an ObjectNotFoundException (causeway), which is
later intercepted by the Wicket Viewer to render the expected object-not-found
ErrorPage
> [Regression] Loading an EntityPage (JDO) when Object-Not-Found results in
> HTTP 500
> ----------------------------------------------------------------------------------
>
> Key: CAUSEWAY-3532
> URL: https://issues.apache.org/jira/browse/CAUSEWAY-3532
> Project: Causeway
> Issue Type: Bug
> Components: Core, Viewer Wicket
> Affects Versions: 2.0.0-RC2
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Major
> Fix For: 2.0.0-RC3
>
>
> There is an asymmetry with JdoEntityFacet vs JpaEntityFacet, where on object
> not found during fetch, we either throw an ObjectNotFound exception (JDO) or
> return _null_ (JPA).
> It seems Wicket Viewer does not handle both cases consistently. The expected
> behavior is to show an Object-Not-Found error page (instead of a Server 500
> or Server 404).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
