Uploaded image for project: 'Isis'
  1. Isis
  2. ISIS-1149

New ContentNegotiationService and ContentMappingService SPIs for Restful Objects viewer

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: core-1.8.0
    • Fix Version/s: 1.9.0
    • Component/s: Core
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              danhaywood Dan Haywood
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: