[CAUSEWAY-2424] Separation of Concerns for Spec-Loader-Cache and IsisBeanTypeRegistry

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.0-M5
• Component/s: Core
• Assignee: Andi Huber
• Reporter: Andi Huber
• Created: 02/Sep/20 07:48
• Updated: 24/Oct/20 18:46
• Resolved: 23/Oct/20 19:43

Description

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.

 

 

 

 

Issue Links

• is related to: CAUSEWAY-2382 Concurrent Spec Loading is broken (possible race condition)