[
https://issues.apache.org/jira/browse/CAUSEWAY-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Keir Haywood updated CAUSEWAY-3083:
------------------------------------------
Component/s: Core
Viewer Wicket
Fix Version/s: (was: 2.1.0)
Affects Version/s: 2.0.0-RC4
Priority: Minor (was: Major)
> Vetoed instances of objects should not be rendered a "(none)"; instead "not
> authorised" or "not available" would be better
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: CAUSEWAY-3083
> URL: https://issues.apache.org/jira/browse/CAUSEWAY-3083
> Project: Causeway
> Issue Type: Improvement
> Components: Core, Viewer Wicket
> Affects Versions: 2.0.0-RC4
> Reporter: Daniel Keir Haywood
> Priority: Minor
>
> For example, support we have a Party superclass, Person and Organisation as
> subclasses.
> We choose to allow the user to access Party, but then have a veto on
> Organisation.
> What we would expect is that the property of type PArty is rendered, and if
> it contains a Person, then show the title of the Person, but if it contains
> an Organisation, then show either "not authorised" or "not available".
> However, we currently see "(none)".
>
> Our guess is that the veto is returning null, which is being translated to
> "(none)". We need to extend the contract of the vetoers in order to
> distinguish null = there isn't one, vs null = not telling you if there is one.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
