Hi Willie, Welcome to the users@ mailing list,
comments within... On 13 October 2015 at 19:02, Willie Loyd Tandingan <[email protected]> wrote: > Hi! > > We're quite new to Apache ISIS and would like to use it for our backend > mainly using the restful objects viewer for the frontend implemented as > SPA. We only use the wicket viewer in development and prototyping. So far, > we've gotten highly positive, much amaze feedbacks from the developers due > to its free UI and they can focus more on business logic. > > Lovely to hear that your team's experience so far has been so positive! > Most entities usually have CRUD pages and a view page in the form of a > grid. In the wicket viewer, actions that return list are shown as tables > with the properties as columns while honoring UI hints. Is it possible to > apply this behaviour to restful objects? The short answer is no. I'm not averse to enhancing this with extensions as they make sense. But the longer answer is that there a couple of SPI services that allow you to customize the representations, [1], [2]. The default RO representations are performed by an implementation of [1]. Eventually I'm thinking that Isis might provide out-of-the-box implementations for HAL, Collection+JSON, Siren etc... but you might find that your client-side (Javascript?) widget UI libraries work best with some other more "adhoc" representations. What these SPI services *don't* allow is for the resources defined by RO (or their input JSON) to change. I don't see any particular need to customize this, though. > Currently, actions returning a > list of domain objects only return links with the title and I would like it > to include/exclude other properties that are seen/unseen in the wicket > viewer. The user guide [1] shows an option to allow UI hints but it seems > to only apply specifically to collections rendering eagerly. > > I had a quick look at the restful objects renderer code and it seems that > what I needed is ListReprRenderer with DomainObjectReprRenderer. The action > returning the list of domain object always has a parameter for pagination. > > If you can specify exactly what's needed, we can take it from there. Or, since you've already started getting familiar with the codebase, happy to review any pull requests. Or, as I say, go your own way with a custom SPI implementation of [2] or [3]. HTH Dan > Thanks in advance! > > [1] https://isis.apache.org/guides/ug.html#7.1.-features > [2] http://isis.apache.org/guides/rg.html#_rg_services-spi_manpage-RepresentationService [3] http://isis.apache.org/guides/rg.html#_rg_services-spi_manpage-ContentMappingService
