[
https://issues.apache.org/jira/browse/ISIS-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Keir Haywood updated ISIS-2010:
--------------------------------------
Description:
One idea:
- NatureOfService.MODULE_API
For the API, can wrap (and perhaps are auto-wrapped)
For the DOMAIN, 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 MODULE_API vs DOMAIN.
was:
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.
> Define a formal API for programmatic interactions between modules Define a
> new natureOfService of MODULE_API, for programmatic interactions via wrapper
> across module trust boundaries.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ISIS-2010
> URL: https://issues.apache.org/jira/browse/ISIS-2010
> Project: Isis
> Issue Type: Improvement
> Components: Isis Applib (programming model)
> Affects Versions: 1.16.2
> Reporter: Daniel Keir Haywood
> Priority: Major
>
> One idea:
> - NatureOfService.MODULE_API
> For the API, can wrap (and perhaps are auto-wrapped)
> For the DOMAIN, 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 MODULE_API vs
> DOMAIN.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
