Code: Select all
@Transactional
public User login(String username, String password, String ipAddress, boolean needDevRoleCheck)
throws CatalogAPIException, LoginFaultException {
return internalLogin(username, password, ipAddress, needDevRoleCheck);
}
Code: Select all
private User internalLogin(String username, String password, String ipAddress, boolean needDevRoleCheck)
throws CatalogAPIException, LoginFaultException {
User user = null;
try {
user = userService.getUserByUsername(username.toUpperCase());
} catch (ServiceException e) {
logger.error(e);
}
authorizationService.checkDevModeLocked(user);
}
Code: Select all
public User getUserByUsername(String username) throws ServiceException {
User user = userRepository.findByUsername(username.toUpperCase());
if (user == null) {
throw new ServiceException("definition.user.not.found", localeService.getMessage("definition.user.not.found", username));
}
return user;
}
Code: Select all
public void checkDevModeLocked(User user) throws LoginFaultException {
///some more logic and then
user.setDevLogin(Constants.TRUE);
}
Aber dieselbe Codebasis Springboot2.6.6/JPA/Hibernate5 hat gut funktioniert, aber jetzt wird die neueste Version von Springboot3.4.1/JPA/Hibernate-core6.6.4 verwendet.
Gibt es irgendwelche größeren Änderungen von Hibernate zu bewältigen? Die @Transactional ?