[CAUSEWAY-3532] [Regression] Loading an EntityPage when Object-Not-Found results in HTTP 500 (JDO+JPA)

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Resolved
• Affects Version/s: 2.0.0-RC2
• Fix Version/s: 2.0.0-RC3
• Component/s: Core, Viewer Wicket
• Assignee: Andi Huber
• Reporter: Andi Huber
• Created: 20/Jul/23 07:02
• Updated: 24/Jul/23 15:42
• Resolved: 24/Jul/23 15:42

Description

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).