[
https://issues.apache.org/jira/browse/ISIS-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14695184#comment-14695184
]
ASF subversion and git services commented on ISIS-848:
------------------------------------------------------
Commit 9ebdbfc780dfeb857ed5b30b4a1275e2eee9503d in isis's branch
refs/heads/master from [~jcvanderwal]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=9ebdbfc ]
ISIS-848: consolidated the discovery of domain services, entities and fixture
scripts ...
... so that when an AppManifest is present these are eagerly discovered and are
held in the (slightly hacky) AppManifest.Registry singleton.
The ServicesInstallerFromAnnotation, RegisterEntities and
ClassDiscoveryServiceUsingReflections service have all been updated to look at
this singleton and use if present, else the original behaviour
> Use a single consolidated mechanism for auto-discovery of services, entities
> and fixture scripts.
> -------------------------------------------------------------------------------------------------
>
> Key: ISIS-848
> URL: https://issues.apache.org/jira/browse/ISIS-848
> Project: Isis
> Issue Type: Improvement
> Components: Core
> Affects Versions: core-1.6.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: 1.10.0
>
>
> 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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
