[
https://issues.apache.org/jira/browse/CAUSEWAY-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18057254#comment-18057254
]
Andi Huber commented on CAUSEWAY-3963:
--------------------------------------
>From our hook into Spring's classpath-scanning we collect a subset of the
>discovered beans into our BeanTypeRegistry, categorized into BeanSort(s)
>(ABSTRACT, ENTITY, VIEWMODEL, VALUE, ...).
Then introspection happens in multiple stages (REGISTER, TYPE_HIERARCHY,
MEMBERS), where initial introspection may trigger discovery of new types.
The challenge is to keep track of this discovery cascade, so one can reason
about what type triggered discovery of another.
> [Debug] For every Type introspected, keep track of what triggered the
> Introspection
> -----------------------------------------------------------------------------------
>
> Key: CAUSEWAY-3963
> URL: https://issues.apache.org/jira/browse/CAUSEWAY-3963
> Project: Causeway
> Issue Type: New Feature
> Components: Core
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Major
> Fix For: 4.0.0
>
>
> Some times types end up in the meta-model, which we perhaps don't want. At
> this stage it is hard to find the cause for why a specific type got
> introspected.
> With this change, we'd like to introduce e.g. a new field within
> ObjectSpecification, that keeps some record on what triggered the
> introspection.
> Could be because discovered by Spring as a Bean candidate, which is the
> trivial case, but then we have cascading triggering via going into type
> hierarchies and also members and action parameters.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
