You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2019/01/04 12:31:00 UTC
[jira] [Updated] (ISIS-1914) Remove the ability to add additional
services to an AppManifest or Module
[ https://issues.apache.org/jira/browse/ISIS-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Haywood updated ISIS-1914:
------------------------------
Summary: Remove the ability to add additional services to an AppManifest or Module (was: Module Building: Adding additional Services fails on Metadata validation)
> Remove the ability to add additional services to an AppManifest or Module
> -------------------------------------------------------------------------
>
> Key: ISIS-1914
> URL: https://issues.apache.org/jira/browse/ISIS-1914
> Project: Isis
> Issue Type: Question
> Reporter: Andi Huber
> Priority: Major
> Fix For: 2.0.0-M2
>
>
> Adding a Service outside of the scope of configured modules fails with
> {noformat}
> java.lang.AssertionError: Metamodel is invalid:
> Domain objects discovered in package 'x.x.x' are not in the set of modules obtained from the AppManifest's top-level module 'y.y.y.MyModule'. Classes are: x.x.x.MyService
> {noformat}
> +Source:+
> {code:java}
> public abstract class DomainAppIntegTestAbstract extends IntegrationTestAbstract3 {
> public DomainAppIntegTestAbstract() {
> super(new MyModule()
> .withAdditionalServices(MyService.class)
>
> ...
>
> ;
> }
> }
> {code}
> If this behavior is intended, than what is the point of adding additional services?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)