[jira] [Commented] (ISIS-2424) Separation of Concerns for Spec-Loader-Cache and IsisBeanTypeRegistry

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

ASF subversion and git services commented on ISIS-2424:
-------------------------------------------------------

Commit 933d70c410073f4a009b6d1bc4c59c52e79dcf00 in isis's branch refs/heads/dependabot/maven/org.apache.maven.plugins-maven-toolchains-plugin-3.0.0 from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=933d70c ]

ISIS-2424: fixing test

> Separation of Concerns for Spec-Loader-Cache and IsisBeanTypeRegistry
> ---------------------------------------------------------------------
>
>                 Key: ISIS-2424
>                 URL: https://issues.apache.org/jira/browse/ISIS-2424
>             Project: Isis
>          Issue Type: Improvement
>          Components: Isis Core
>            Reporter: Andi Huber
>            Assignee: Andi Huber
>            Priority: Major
>             Fix For: 2.0.0-M5
>
>
> It would be great to get rid of the quick classification stuff in IsisBeanTypeRegistry, because determining the BeanSort is ultimately a meta-model concern (responsibility of the ObjectSpecificationLoader).
> IsisBeanTypeRegistry can only operate before Spring's Context is available, hence does not have access to provisioned services, while the ObjectSpecificationLoader does.
> IsisBeanTypeRegistry's responsibility should be trimmed down to just
>  * provide alternative bean naming to override Spring's defaults (objectType="...")
>  * determine which types to introspect (inbox for spec-loader)
> BeanSort classification should happen then at a later stage, when Spring's context is available.
>  
>  
>  
>  



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