can't get SpringBoot and JPA to return 404 for missing entity.

[adhamhf]

Based on the JSON:API spec, if I ask for an entity that does not exist I should get a 404.

When using the spring-boot-simple-example I can only get {"data":null}.

curl http://localhost:8080/api/schedule/1 
   -> {"data":null}%

however, when using one of the non-JPA entities in the sample I get the expected result:

curl http://localhost:8080/api/tasks/10000 
  -> {"errors":[{"status":"404","title":"Project not found!","detail":"Project not found!"}]}

@remmeier it looks like you updated the sample for JPA. Do you have any thoughts?

[adhamhf]

I think the issue is that JpaEntityRepository is not throwing ResourceNotFoundExceptions in findOne or findAll. Also, I think it would be nice if JpaRepositoryFactory relied on an interface instead of the concrete class JpaEntityRepository. This would make it much easier for me to provide an alternative implementation. Right now I have I have to subclass JpaEntityRepository, some of these methods are final it makes a work around ackward.