Spring-Data JPA CrudRepository returns Iterable, is it OK to cast this to List?


I’m writing a code-gen tool to generate backend wiring code for Spring-boot applications using Spring-Data-Jpa and it’s mildly annoying me that the methods in the CrudRepository return Iterable rather than List, as iterable doesn’t provide quite enough functionality, but List does, so I’m looking for the best way to convert the iterable into a list.

I saw this post on changing an iterable to a collection and I was wondering, rather than using a library like Guava or implementing my own function to do the conversion, why not just cast it to List? Is there something wrong with doing that that I don’t know about?

I ask because since it’s a code-gen tool it’s not reasonable to make it generate code that introduces dependencies on 3rd party libraries, and writing my own function to do the conversion also isn’t really reasonable because it would have to live somewhere and I’d rather not have that in the generated code. A simple cast will work, if a little ugly, but just wondered if there’s something I’m missing?


No, I don’t think it’s OK.

While a List is guaranteed to be an Iterable an Iterable may not be a List. This means that if you do cast an Iterable to a List it may fail at runtime. Even if it works, there’s no guarantee that it will continue to work in the future as it could change in new versions of Spring Data JPA without breaking the interface’s contract.

Instead of using a cast, you should declare your own query methods that return List.

Alternatively you may use Streamable.of(iterable).toList() for doing the conversion. This answer also contains some background why Iterable was chosen as the return type for these methods.

Answered By – Andy Wilkinson

This Answer collected from stackoverflow, is licensed under cc by-sa 2.5 , cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply

(*) Required, Your email will not be published