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 06:31:00 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=16933097#comment-16933097 ] 

Andi Huber commented on ISIS-2010:
----------------------------------

Now that we have Spring, we allow the use of stereotypes ...
{noformat}
@Singleton (javax.inject.Singleton)
@Service (org.springframework.stereotype.Service){noformat}
as semantic replacements for

 

 
{code:java}
@DomainService(NatureOfService.DOMAIN)
{code}
So in principle the semantic meaning of the latter could be redefined! eg. to proposed 'can wrap (and perhaps are auto-wrapped)'.

 

> 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)