Spring Data REST How to add embedded resources inline

The accepted method of inlining entities is projections, as you identified. Projections are always inlined, so one option is to create projections for each of your entities and combine them like so:

@Projection(name = "personProjection", types = Person.class)public interface PersonProjection {    String getFirstName();    List<CompanyProjection> getCompanies();}@Projection(name = "companyProjection", types = Company.class)public interface CompanyProjection {    String getName();    AddressProjection getAddress();}@Projection(name = "addressProjection", types = Address.class)public interface AddressProjection {    String getStreet();}

A GET people/1?projection=personProjection will still render _links elements, but you will get the nesting you want:

{  "companies" : [ {    "address" : {      "street" : "123 Fake st",      "_links" : {        "self" : {          "href" : "http://localhost:8080/addresses/1{?projection}",          "templated" : true        }      }    },    "name" : "ACME inc.",    "_links" : {      "self" : {        "href" : "http://localhost:8080/companies/1{?projection}",        "templated" : true      },      "address" : {        "href" : "http://localhost:8080/companies/1/address"      }    }  } ],  "firstName" : "Will",  "_links" : {    "self" : {      "href" : "http://localhost:8080/people/1"    },    "person" : {      "href" : "http://localhost:8080/people/1{?projection}",      "templated" : true    },    "companies" : {      "href" : "http://localhost:8080/people/1/companies"    }  }}

Alternatively, if you don't need to expose the Company and Address entities as rest resources, you can mark their repositories with @RepositoryRestResource(exported=false), and they will be inlined wherever they are referenced, without any need for projections.

A final caveat, though - this request is somewhat fighting against the ethos of Spring Data REST and Spring HATEOAS, and inviting big, unwieldy queries suffering the n+1 problem. Remember that Spring Data REST is not a turnkey solution for turning a domain model into an API, and rendering deep object graphs (if that is your intention) is potentially something you might expose as a custom controller endpoint on an ad-hoc basis where you can control the conditions thoroughly.

In the second endpoint , if you don't want links , you have to have a controller and a resource , where you map the data to the resource and return the collection of resource from the controller

I believe the best way to embed a List or a HashMap is via converting it into a json string and back to java object when you read it....

this can be easily be done using

    @Convert(converter = PluginAnalyzerConfigConverter.class)  private PluginAnalyzerConfig configuration;//in Entity Class// declare a converter class like thispublic class PluginAnalyzerConfigConverter implements    AttributeConverter<PluginAnalyzerConfig, String> {  @Override public String convertToDatabaseColumn(PluginAnalyzerConfig config) {    Gson parser = new Gson();    return parser.toJson(config, PluginAnalyzerConfig.class);  }  @Override public PluginAnalyzerConfig convertToEntityAttribute(String source) {    Gson parser = new Gson();    return parser.fromJson(source, PluginAnalyzerConfig.class);  }}

as shown on Spring Data with Mysql JSON type

We have similar thing in Spring Data DynamoDb - for AWS DynamoDB