You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Andi Huber (Jira)" <ji...@apache.org> on 2019/09/19 07:18:00 UTC

[jira] [Comment Edited] (ISIS-2010) Define a formal API for programmatic interactions between modules

    [ https://issues.apache.org/jira/browse/ISIS-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16933117#comment-16933117 ] 

Andi Huber edited comment on ISIS-2010 at 9/19/19 7:17 AM:
-----------------------------------------------------------

Yes, to be more precise:
 # The Singleton/Service stereotypes are information directed at the Inversion of Control Container (IoCC). Meaning, we want instances of this classes to be inject-able into our domain-objects. (But these won't contribute to the meta-model.)
 # The DomainService annotation however, might be interpreted as an intent to contribute something to the meta-model.

However any 'DomainService' annotated class is also regarded 'inject-able'. Meaning it is managed by the IoCC.


was (Author: hobrom):
Hmm, maybe this is open for discussion:
 # The Singleton/Service stereotypes are information directed at the Inversion of Control Container (IoCC). Meaning, we want instances of this classes to be inject-able into our domain-objects. (But these won't contribute to the meta-model.)
 # The DomainService annotation however, might be interpreted as an intent to contribute something to the meta-model.

However any 'DomainService' annotated class is also regarded 'inject-able'. Meaning it is managed by the IoCC.

> Define a formal API for programmatic interactions between modules
> -----------------------------------------------------------------
>
>                 Key: ISIS-2010
>                 URL: https://issues.apache.org/jira/browse/ISIS-2010
>             Project: Isis
>          Issue Type: Improvement
>    Affects Versions: 1.16.2
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>            Priority: Major
>             Fix For: 2.0.3
>
>
> One idea:
> - NatureOfService.DOMAIN_API vs NatureOfService.DOMAIN (latter interpreted as IMPL)
> For the API, can wrap (and perhaps are auto-wrapped)
> For the IMPL, are not wrapped, and don't introspect the methods to create actions.
> It's not clear to me which of the Isis services should be DOMAIN_API vs DOMAIN.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)