Subject: Rest services


I'm glad we're discussing this.

By "front-end source code", are we referring to code generated by a utility
such as swagger-codegen [1]?  If so, then I would look at that utility to
customize its output to your organization's standards.

About the content negotiation service: I haven't implemented one yet, so
can someone please verify if I have this right?  It looks to me that the
docs [2] are saying that the content negotiator service overloads the use
of the profile portion of the Accept header to give a response that is
different from what is defined in the Restful Objects API specification
that is created when the application is built.   Writing client code to
consume this would be manual, but it would be as simple as the profile you
implement in your content negotiation service.  The output from this
service is an instance of a JAXB serializable class, like a view model [3] .

[1] https://github.com/swagger-api/swagger-codegen
[2]
https://isis.apache.org/guides/ugvro/ugvro.html#_ugvro_simplified-representations_apache-isis-profile
[3]
https://isis.apache.org/guides/ugfun/ugfun.html#_ugfun_building-blocks_types-of-domain-objects_view-models
On Mon, Apr 15, 2019 at 7:25 AM Rade, Joerg / Kuehne + Nagel / HAM GI-DP <
[EMAIL PROTECTED]> wrote: