[
https://issues.apache.org/jira/browse/CAUSEWAY-3499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andi Huber resolved CAUSEWAY-3499.
----------------------------------
Resolution: Resolved
fixed by filtering for specific types
Note: In the context of Causeway, not all Spring imports are managed by Spring.
Hence asking Spring for a bean instance will fail if the type is not managed by
Spring.
> Hint to avoid full introspection doesn't work, due to our custom scope for
> entities.
> ------------------------------------------------------------------------------------
>
> Key: CAUSEWAY-3499
> URL: https://issues.apache.org/jira/browse/CAUSEWAY-3499
> Project: Causeway
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0.0-RC1
> Reporter: Daniel Keir Haywood
> Assignee: Andi Huber
> Priority: Minor
> Fix For: 2.0.0-RC2
>
> Attachments: image-2023-06-23-14-18-34-637.png
>
>
> When running an integ test, got this error:
> 2023-06-23 14:19:20.054 WARN 55544 --- [ main]
> o.a.i.c.m.s.SpecificationLoaderDefault : The metamodel is configured for
> FULL introspection mode, yet missed
> org.estatio.module.party.dom.permit.Permit of sort ABSTRACT during
> application start. This happens when type
> org.estatio.module.party.dom.permit.Permit is not eagerly discovered by the
> metamodel introspection, which (initially) only considers compile-time types
> via reflection. Run-time types, not explicitly referenced to be included with
> Spring's class discovery mechanism, might slip this process. Consider
> importing type org.estatio.module.party.dom.permit.Permit with Spring's
> @Import annotation. Types of sort VALUE should instead register a
> ValueSemanticsProvider with Spring, to be properly understood by the
> framework.
> 2023-06-23 14:19:20.062 WARN 55544 --- [ main]
> o.a.i.c.m.s.SpecificationLoaderDefault : The metamodel is configured for
> FULL introspection mode, yet missed
> org.estatio.module.party.dom.role.PartyRoleTypeEnum of sort VALUE during
> application start. This happens when type
> org.estatio.module.party.dom.role.PartyRoleTypeEnum is not eagerly discovered
> by the metamodel introspection, which (initially) only considers compile-time
> types via reflection. Run-time types, not explicitly referenced to be
> included with Spring's class discovery mechanism, might slip this process.
> Consider importing type org.estatio.module.party.dom.role.PartyRoleTypeEnum
> with Spring's @Import annotation. Types of sort VALUE should instead register
> a ValueSemanticsProvider with Spring, to be properly understood by the
> framework.
>
> and so I added them in:
> !image-2023-06-23-14-18-34-637.png!
>
> But I then got this exception:
>
> Caused by: org.springframework.beans.factory.support.ScopeNotActiveException:
> Error creating bean with name 'permit.dom.Permit': Scope 'isis-domain-object'
> is not active for the current thread; consider defining a scoped proxy for
> this bean if you intend to refer to it from a singleton; nested exception is
> java.lang.IllegalStateException: No Isis Interaction is currently active
>
>
> This is because our entities are meta-annotated (via @DomainObject) to have a
> custom scope.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
