getTeamMapping是否应该从Spring-Data-JPA方法获取数据？

Question

Have a look at the below code

teamMappingEntity = (List<TeamMappingEntity>) adminUtilityRequest
    .getTeamMappingRepository()
    .findAllByUserEntityAndIsDeleted(userEntity, Boolean.FALSE);

I am getting a NullPointerException at this line because getTeamMappingRepository in AdminUtilityRequest class is null at this point. But what I don't understand is if I am calling the Spring-Data-JPA method findAllByUserEntityAndIsDeleted in the above line the data which I get from the Spring Data JPA method should be saved in getTeamMappingRepository but it doesn't. WHY????

Although this line works fine.

teamMappingEntity =  teamMappingRepository
    .findAllByUserEntityAndIsDeletedFalse(userEntity);

Any explanation will be appreciated.

Answer 1

if I am calling the Spring-Data-JPA method findAllByUserEntityAndIsDeleted in the above line the data which I get from the Spring Data JPA method should be saved in getTeamMappingRepository but it doesn't.

Nope. findAllByUserEntityAndIsDeleted will return some data. That's it. It won't store it anywhere. And certainly not in getTeamMappingRepository :

1. That is a method. You can't store anything in a method. You would need a field for that.
2. It is of the wrong type. findAllByUserEntityAndIsDeleted returns a List , but getTeamMappingRepository returns a repository. Two very distinct things.
3. findAllByUserEntityAndIsDeleted doesn't contain any information about the existence of getTeamMappingRepository . There is no way it can manipulate it in any way.

Your real problem is that there is no repository in adminUtilityRequest . We would need to see what you did to get a repository in there.

Possibly you are missing an @Autowired annotation, or adminUtilityRequest is not a Spring bean so it doesn't get anything injected.

Answer 2

Probally in your adminUtilityRequest you need to add @Autowired annotation for "teamMappingRepository" attribute

If the annotation exist, maybe you object "adminUtilityRequest" was built manually outside of Spring context. Should be good you review who this object is created.