[
https://issues.apache.org/jira/browse/ISIS-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14170177#comment-14170177
]
Dan Haywood commented on ISIS-917:
----------------------------------
Hi Vladimir,
glad you've had a chance to play with this and you've made some progress.
With respect to the buildResponse() method, you've done the right thing by
ignoring; I added it mostly just so I could easily test the pluggability by
adding in an additional X- http header. But my expectation was that "in
reality" the entire methods would need to be overridden, exactly as you've done.
With respect to the processing of the inbound requests, we could certainly
provide a separate pluggable service for that too, (eg a
RequestHandlerService); I did think that there'd be some sort of need. Then
again a final solution will also need to tie together these different
representation generators and request handlers and also to make them switchable
on the Accept header/Content-Type.
Ideally, it'd be nice to provide an implementation for some of the common media
types out there, eg HAL, Collection+JSON or Siren. And use "Accept" header to
switch between any of these plus also the "native" RO representation.
If you have any further ideas, do please say; keen to iterate here.
Cheers
Dan
> Support pluggable representations for the RO viewer (object and list
> representations)
> -------------------------------------------------------------------------------------
>
> Key: ISIS-917
> URL: https://issues.apache.org/jira/browse/ISIS-917
> Project: Isis
> Issue Type: New Feature
> Components: Core: Viewer: RestfulObjects
> Affects Versions: core-1.6.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: core-1.7.0
>
>
> This ticket is to factor out the logic in the RO viewer that builds the JSON
> representation and put it behind a @DomainService.
> As a first cut, I think it's only the object representation and list
> representations that need to be pluggable.
> Ultimately I would like to get to a point where the representation used
> honours the Accept header (Content-Type), but will probably iterate to get
> there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
