You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/10/19 12:53:02 UTC
[jira] [Commented] (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=16656764#comment-16656764 ]
ASF subversion and git services commented on ISIS-2010:
-------------------------------------------------------
Commit 5296ce67d43fc341926d2f704f0e15361d750ec7 in isis's branch refs/heads/ISIS-2010 from danhaywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=5296ce6 ]
ISIS-2010: work in progress going through references to DOMAIN
Have added DOMAIN_API, now need to look at existing uses of DOMAIN and see how they should be handled.
> 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.0-M2
>
>
> 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
(v7.6.3#76005)