Spring Data JPA 1.0 M2 released

Dear Spring Community,

I am pleased to announce that the second milestone release of the Spring Data JPA project is now available! The release includes:

• Support for Querydsl predicates and thus type-safe JPA queries
• Validation of @Query annotated queries at bootstrap time
• Support for XML based entity mapping
• Support for Distinct, In and NotIn keywords in query methods
• Ported Hades extensions into Spring Data Commons core
• Various bugfixes

Code:

---

<dependency>
  <groupId>org.springframework.data</groupId>
  <artifactId>spring-data-jpa</artifactId>
  <version>1.0.0.M2</version>
</dependency>

<repository>
    <id>org.springframework.maven.milestone</id>
    <name>Spring Maven Milestone Repository</name>
    <url>http://maven.springframework.org/milestone</url>
</repository>

---

Download | JavaDocs | Reference documentation (HTML) | Reference documentation (PDF) | Changelog

Looking forward to your feedback in the forums or the issuetracker.

Great news! Lots of great features here, especially QueryDSL integration. Was hoping the Spring MVC integration would be in this release. Is that coming soon?

It's in the release but in Spring Data Commons actually as the PropertyEditor, Converter and WebArgumentResolver are not depending on JPA specifics but rather the general repository abstraction.

Cheers,
Ollie

Ah yes I see that DATAJPA-19 is marked Fixed. This is super exciting, I'm thrilled by what you are doing with Spring Data - I think it's the most important new Spring technology in a long time!

Congrats, looking forward to GA :D

hi oliver,

i've never been exposed to hades, but i was positively impressed with spring data jpa M1 in terms of the boiler-plate elimination, kudos on the overall design!

i started using the findAll(Specification s) method from the JpaRepository interface in M1, but that seems to have been refactored in M2.

i found i could get similar functionality by also implementing the JpaSpecificationExecutor interface.

what i'm not clear on is the usage pattern for SimpleJpaRepository in terms of when and how i might use that class, if you get a moment can you elaborate briefly?

thanks,
tony.

Hi,

I've found an error and don't know where and how to report it.

Is the forum the right place for it?

JIRA is the best place to do so: https://jira.springframework.org/browse/DATAJPA :)

Hi Tony,

good catch. With the introduction of Querydsl support we decided to extract Specification and (Querydsl) Predicate executing behavior into separate interfaces. This is mostly due to the fact that most users will decide between one or the other API. Thus you now find JpaSpecificationExecutor and QueryDslPredicateExecutor interfaces that you can let your repository interface extend. You can easily add both of them but when you want to stick to Querydsl you're not polluting the repository API with the Specifications. The namespace and thus in turn the FactoryBean will choose the appropriate implementation as proxy backing instance.

There will be a blogpost coming up end of this week (or early next week) and we will have the documentation updated according to these changes with the RC1 release. I've created a ticket [1] for that you might wanna follow to keep track of the progress.

Cheers,
Ollie

[1] https://jira.springsource.org/browse/DATAJPA-43

Quote:

---

Originally Posted by Oliver Gierke

Dear Spring Community,

I am pleased to announce that the second milestone release of the Spring Data JPA project is now available! The release includes:

forums or the issuetracker.

---

Do you plan to update the showcase to pick up the API changes?

Do you see a build error or do you rather want to express we should add samples for the new features? In either case feel free to open up a JIRA and I'll happily approach it :).

Cheers
Ollie