[CAUSEWAY-848] Use a single consolidated mechanism for auto-discovery of services, entities and fixture scripts.

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: core-1.6.0
• Fix Version/s: 1.9.0
• Component/s: Core
• Assignee: Unassigned
• Reporter: Daniel Keir Haywood
• Created: 30/Jul/14 21:30
• Updated: 01/Sep/15 19:49
• Resolved: 13/Aug/15 13:33

Description

ie... implement AppSpecs/ClusterSpecs.

~~~
Isis core now supports auto-discovery (behind the scenes using org.reflections.Reflections) of entities, of services and of fixture scripts. But the configuration of these is all over the place:

• entities are discovered:
• in the app using WEB-INF/persistor_datanucleus.properties
• in the integtests in the XxxSystemBuilder#testConfiguration()
• services are discovered:
• in the app using WEB-INF/isis.properties
• in the integtests in the XxxSystemBuilder#(constructor)
• fixture scripts are discovered:
• in the app in the constructor of the subclass of FixtureScripts.

~~~
some other aspects to consider:

isis.properties, persistor.properties etc.

Shiro realm, whether to enable or not (shiro.ini)

web.xml fragments (filters/servlets)

per publishmq add-on, this means:

• cxf
• jolokia
• hawt.io
• RO

• spring
• bootstraps in turn camel/activemq
• could tackle with a different spring file ?
• reconfigure spring.properties

Issue Links

• incorporates: CAUSEWAY-847 RegisterEntities isn't called prior to the metamodel validation, thus we currently rely on priming the metamodel through the services... not good.