Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IllegalArgumentException: JdbcValue must be not null at this point [DATAJDBC-378] #603

Closed
spring-projects-issues opened this issue May 24, 2019 · 3 comments
Assignees

Comments

@spring-projects-issues
Copy link

@spring-projects-issues spring-projects-issues commented May 24, 2019

Yuri Konotopov opened DATAJDBC-378 and commented

I had received attached exception with message "java.lang.IllegalArgumentException: JdbcValue must be not null at this point. Please report this as a bug."

 

This exception is caused by using "CrudRepository.findAllById" method with empty Iterable.

Passing empty collection is for sure bug in my code, but I decided to report this behavior because of exception message.

I think this message may be improved in case empty collection is passed to findAllById()


Affects: 1.1 M4 (Moore)

Attachments:

Referenced from: pull request #155

Backported to: 1.0.9 (Lovelace SR9)

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented May 24, 2019

Jens Schauder commented

Thanks for reporting the issue.
That sounds like we should check for null and actually create an instance for collections.

Could your provide the entity classes with which you triggered the exception?

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented May 24, 2019

Yuri Konotopov commented

Here is simple app with this issue: https://github.com/nE0sIghT/DATAJDBC-378

1 similar comment
@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented May 25, 2019

Yuri Konotopov commented

Here is simple app with this issue: https://github.com/nE0sIghT/DATAJDBC-378

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants