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

JPA dependency and automatic Bean mapping #3

Open
pixmize opened this issue Oct 29, 2015 · 1 comment
Open

JPA dependency and automatic Bean mapping #3

pixmize opened this issue Oct 29, 2015 · 1 comment

Comments

@pixmize
Copy link

pixmize commented Oct 29, 2015

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.

@sergiorussia
Copy link
Collaborator

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.

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

No branches or pull requests

2 participants