Andi Huber created ISIS-2424:
--------------------------------
Summary: Investigate Unification of Spec-Loader-Cache and
IsisBeanTypeRegistry
Key: ISIS-2424
URL: https://issues.apache.org/jira/browse/ISIS-2424
Project: Isis
Issue Type: Task
Components: Isis Core
Reporter: Andi Huber
Assignee: Andi Huber
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)
