sergiorussia
commented
6 years ago why not use SpringJDBC then? JPA annotations give additional metadata like tables or columns names etc, also there should be at least some clue on which columns makes primary id for select or delete.
anyway, if the only thing you need is map result set to pojo, i'd suggest to make a pull request, see Introspected class where the Column annotation is searched.
I am wondering if there is any way JPA dependency can be avoided and instead resultset can be directly mapped to POJO just like Spring JDBC template. In my opinion it'll be one less dependency to worry about.