I fixed this by adding

@JsonIdentityInfo(generator=ObjectIdGenerators.PropertyGenerator.class, property="id")
public class User {

to my User.java class

You could add @JsonBackReference to the other site of the relation. Which by the way is missing or not correct implemented. Add:

@JsonBackReference
@ManyToOne
@JoinColumn(name = "autoServiceId", nullable = false)
private AutoService autoService;

instead of private long autoServiceId;.

Also the AutoService needs to be adjusted with:

@JsonManagedReference
@OneToMany(mappedBy = "autoService", fetch=FetchType.EAGER)
private List<Service> services = new ArrayList<>();

You reference the name user-movement more than once in your object tree as @JsonBackReference. You'll need to rename one of them. The two cases are:

@JsonBackReference(value="user-movement")
    public Set<Device> getDevice() {
        return devices;
    }

And

@JsonBackReference(value="user-movement")
    public Main_schedule getMain_schedule_schedule_id(){
      return main_schedule;
     }

See more: Jackson: Multiple back-reference properties with name 'defaultReference'

You need to configure Jackson so it can serialize / deserialize Guava's imutable collections. See https://github.com/FasterXML/jackson-datatypes-collections/tree/master/guava.

I wouldn't suggest exposing entities directly to your controller. Entities should only contain JPA annotations in your case. You can expose a DTO (Data Transfer Object) to your controller and then map the DTO to the corresponding entity.

ReviewDto

public class ReviewDto {
    private String reviewDescription;

    private double courseRating;

    private CourseDto course;

    // getters, setters, etc
}

CourseDto

public class CourseDto {
    private Long id;

    private String name;

    private String description;

    // professorDto, getters, setters, etc
}

An example demonstrating how your controller class will be

@RestController
public class DemoController {
    private final ReviewDtoMapper reviewDtoMapper;
    private final ReviewService reviewService;

    public DemoController(ReviewDtoMapper reviewDtoMapper,
                          ReviewService reviewService) {
        this.reviewDtoMapper = reviewDtoMapper;
        this.reviewService = reviewService;
    }

    @PostMapping(value = "demo")
    public ResponseEntity<String> postReview(@RequestBody ReviewDto reviewDto) {
        final Review review = reviewDtoMapper.mapFrom(reviewDto);

        reviewService.save(review);

        return ResponseEntity.ok("");
    }
}

The class to map from reviewDto to review entity and the opposite.

@Component
public class ReviewDtoMapper {

    public ReviewDto mapTo(final Review entity) {

        ReviewDto reviewDto = new ReviewDto();
        reviewDto.setReviewDescription(entity.getReviewDescription());
        // set all the properties you want
        return reviewDto;
    }


    public Review mapFrom(ReviewDto dto) {

        Review review = new Review();
        review.setReviewDescription(dto.getReviewDescription());
        // set all the properties you want
        return review;
    }
}

Of course, you have to make adjustments according to your needs.

If you like this way of doing things I would suggest you check MapStruct, it will automatically make the mappers for you.

The proper way to solve this without a default constructor is to add JsonCreator and JsonProperty annotations to your class constructor.

class MyClass {

    String name;

    @JsonCreator
    MyClass(@JsonProperty("name") String name) {
        this.name = name;
    }
    ...
}