[
https://issues.apache.org/jira/browse/CAUSEWAY-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845831#comment-17845831
]
Andi Huber edited comment on CAUSEWAY-3736 at 5/13/24 9:14 AM:
---------------------------------------------------------------
404 can be reproduced using simpleapp-jpa then requesting
http://localhost:8080/restful/services/causeway.ext.executionOutbox.OutboxRestApi/actions/pending/invoke
However, all works correct (return 200), when test user `sven` has sufficient
access rights. (Role causeway-ext-executionOutbox in the simpleapp case.)
was (Author: hobrom):
404 can be reproduced using simpleapp-jpa then requesting
http://localhost:8080/restful/services/causeway.ext.executionOutbox.OutboxRestApi/actions/pending/invoke
> [RO] Returns 404 for empty List (while should 200)
> --------------------------------------------------
>
> Key: CAUSEWAY-3736
> URL: https://issues.apache.org/jira/browse/CAUSEWAY-3736
> Project: Causeway
> Issue Type: Bug
> Components: Viewer RO
> Affects Versions: 2.0.0, 3.0.0
> Reporter: Daniel Keir Haywood
> Assignee: Andi Huber
> Priority: Major
> Fix For: 2.1.0, 3.1.0
>
>
> Dan:
> I tracked down the issue I think ... there's a method called route(...) where
> we pass in a PackedManagedObject that wraps the empty List (or rather, Can at
> this stage), but what we get out is an EMPTY ManagedObject. The RO viewer
> then interprets that as a 404.
> [..] the behaviour is because route(...) calls in turn
> ManagedObjects.isNullOrUnspecifiedOrEmpty(...) [line 70]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
