Test QueryDSL against Batoo JPA

[hceylan]

Hello,

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.

[timowest]

Does Batoo JPA work without any compile time bytecode enhancement? That would make testing a bit more difficult.

[hceylan]

As long as no serialization needed, build time instrumentation is not needed.

[timowest]

Do you mean as long as we don't persist anything it's ok? This sounds like it's needed in our tests. But I will take a closer look at Batoo JPA.

[hceylan]

No, as long as the entity is not serialized out to the outside of the VM, that is not necessary. Hope this clarifies it.

[timowest]

Ok, thanks, that clarified it.

[timowest]

Some issues I ran into

• No persistence.xml examples for usage without datasource
• classpath scan for annotated classes not supported
• logic for taking annotated getters as the property definitions seems to be different from Hibernate and EclipseLink, could you explain how it works, I got an error for this file https://github.com/mysema/querydsl/blob/master/querydsl-jpa/src/test/java/com/mysema/query/jpa/domain4/BookVersion.java

The last one is a blocker, since I don't want to move the annotations, the others are just inconveniences.

[hceylan]

• No persistence.xml -> I have created an issue for that.
• classpath scan -> the issue has just been resolved
• Access Type, unless very complex, this should work. Nevertheless, an issue exists to resolve the ultimate uncertainity.

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?

[timowest]

Wow, you're fast ;)

No persistence.xml -> I have created an issue for that.

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.

classpath scan -> the issue has just been resolved

Nice

Access Type, unless very complex, this should work. Nevertheless, an issue exists to resolve the ultimate uncertainity.

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()

[timowest]

I had some exceptions on EntityManagerFactory startup due to configuration issues. Could you take a look?

You can for example setup Querydsl like this for Eclipse

mvn -Pjenkins,all eclipse:clean eclipse:eclipse

[timowest]

Released in 3.0.0.BETA2