[jira] [Commented] (ISIS-2265) on-the-fly-introspection may occur even though MM was eagerly loaded

["Daniel Keir Haywood (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ISIS-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17016961#comment-17016961 ] 

Daniel Keir Haywood commented on ISIS-2265:
-------------------------------------------

I'm not sure why this should have occurred, because ClassSubstitutorForCollections should prevent this from occurring - when we are asked to introspect AbstractSet, it should skip to just Set.

So, the question is ... why didn't ClassSubstitutor get called?

> on-the-fly-introspection may occur even though MM was eagerly loaded
> --------------------------------------------------------------------
>
>                 Key: ISIS-2265
>                 URL: https://issues.apache.org/jira/browse/ISIS-2265
>             Project: Isis
>          Issue Type: Bug
>            Reporter: Andi Huber
>            Assignee: Andi Huber
>            Priority: Blocker
>             Fix For: 2.0.0
>
>
> +steps to reproduce:+
> e.g. DemoApp (production mode) -> access menu Trees > File System Tree
> java.lang.IllegalStateException
> Cannot introspect class 'java.util.AbstractSet' because the metamodel has been fully introspected and is now locked. One reason this can happen is if you are attempting to invoke an action through the WrapperFactory on a service class incorrectly annotated with Spring's @Service annotation instead of @DomainService. 
> +solutions+
> - either allow on-the-fly-introspection for certain types
> - or find all types in the first place when eagerly loading



--
This message was sent by Atlassian Jira
(v8.3.4#803005)