Hi Vladimir (also Johan)... I've gone ahead and pulled out a domain service to make this pluggable; providing a new implementation of that service will probably be your fastest path to success. You can register your own implementation in isis.properties (see the todoapp example) and this will take precedence over the default impl.
Note that this service only deals with providing alternative representations; it doesn't allow you to change either the resource end-point URLs nor the way in which the in-bound args/bodies are parsed. If this turns out not to provide enough flexibility, you could always write your own JAX-RS service resources. Subclass org.apache.isis.viewer.restfulobjects.server.RestfulObjectsApplication and register in web.xml file. HTH Dan On 6 October 2014 10:28, Vladimir Nisevic (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/ISIS-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160136#comment-14160136 > ] > > Vladimir Nisevic commented on ISIS-917: > --------------------------------------- > > Hi, Dan, since I would pretty soon need first version of this feature, > would be possible a solution where: > > 1. create sample REST service with standard JAX-RS implementeations e.g. > > 1a: jersey archetype ( > https://jersey.java.net/documentation/latest/user-guide.html#new-from-archetype) > or > 1b. jboss resteasy examples ( > https://github.com/resteasy/Resteasy/tree/3.0.9.Final/jaxrs/examples) > > 2. integrate my Isis application into such example so I have access to my > Isis domain services > > I tried with 1a. and copy it from webapp settings, but some startup help > as hints would be great... > > Regs,Vladimir > > > 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.8.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) >
