[
https://issues.apache.org/jira/browse/CAUSEWAY-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18057566#comment-18057566
]
Andi Huber commented on CAUSEWAY-3965:
--------------------------------------
Turns out the Hierarchical interface, which keeps track of sub-, super- and
interface-types within the discovered meta-model, was never used in v3 nor v4
in the following sense:
* interface-types were never populated
* track keeping of sub-types was never used
Which opens following opportunities:
* ditch track keeping of sub-types
* rethink how we want to the interface-type track keeping
** Idea: for every interface that is annotated with `@DomainObject` (which was
previously not allowed), collect it into the Hierarchical's interface-types
** when looking for layouts on the class-path, we currently don't consider
interface-types; however, we could make the exception for interfaces that are
annotated with `@DomainObject`
> [Metamodel] Type Hierarchy Introspection misses out on Interfaces
> -----------------------------------------------------------------
>
> Key: CAUSEWAY-3965
> URL: https://issues.apache.org/jira/browse/CAUSEWAY-3965
> Project: Causeway
> Issue Type: Bug
> Components: Core
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Major
> Fix For: 4.0.0
>
>
> Which apparently is not a problem until interface types are used as the
> element-type for collections.
> In addition we seem to have an issue with the framework getting confused on
> how to generate bookmarks.
> Can be reproduced, when e.g. converting SecMan Entity abstract super classes
> to interfaces.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
