[
https://issues.apache.org/jira/browse/ISIS-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-1149:
------------------------------
Fix Version/s: (was: 1.10.0)
1.9.0
> New ContentNegotiationService and ContentMappingService SPIs for Restful
> Objects viewer
> ---------------------------------------------------------------------------------------
>
> Key: ISIS-1149
> URL: https://issues.apache.org/jira/browse/ISIS-1149
> Project: Isis
> Issue Type: New Feature
> Components: Core
> Affects Versions: core-1.8.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: 1.9.0
>
>
> The ContentNegotiationService SPI allows multiple implementations to be
> installed, and each are checked in turn (chain of responsibility pattern).
> If any can generate a representation of the result then this is used rather
> than the default RepresentationService.
> The framework provides one default implementation:
> ContentNegotiationServiceXRoDomainType that handles
> "application/...;profile=...;x-ro-domain-type=..." for either XML or JSON,
> and for the main representations (object, property, collection, detail,
> action-result)
> As a further sub-SPI, the ContentMappingService is used by the
> afore-mentioned ContentNegotiationServiceXRoDomainType to attempt to map the
> result domain object to another object before rendering. Typically this is
> to map a domain object to a corresponding DTO.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
