Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Test QueryDSL against Batoo JPA #265
We have a new JPA 2.0 implementation - Batoo JPA that implements the spec in full with the minimum possible diversion from the spec and the primary focus being on the best performance.
We have implemented a test case that suggests the basic functionality works.
I would kindly ask you to include Batoo JPA in your supported JPA backends.
added a commit
Nov 5, 2012
Some issues I ran into
The last one is a blocker, since I don't want to move the annotations, the others are just inconveniences.
I will update the progress soon. The blocker should be resolved tomorrow as this is the only blocker bug to my knowledge. A release candidate will follow the issue's resolution.
Do you mind sharing the branch or the patch to enable Batoo JPA in QueryDSL?
Wow, you're fast ;)
I meant examples of how to use persistence.xml with jdbc parameters instead of a datasource. My settings worked, but there was a BoneCP error logging, so something went wrong.
I will use AccessType for now, but adding EmbeddedId in addition to the Id annotation to infer the access type would be a nice addition.
That basic integration has already been done in the commit referenced in this issue.
To enable the autodetection of Batoo JPA I need to know which class is returned by EntityManager.getDelegate()