Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Oct 9, 2012
  1. @olivergierke

    DATAJPA-261 - Clarify usage of countQuery attribute in @Query.

    olivergierke authored
    Clarified that we derive the count query from the method name if no manual query is defined or from the manually defined query if defined.
  2. @olivergierke

    DATAJPA-262, DATAJPA-258 - Fixed dependency setup.

    olivergierke authored
    Switched from SpringSource snapshot repository to release one. Excluded JUnit 3.8.1 dependency transitively pulled in through OpenJPA.
Commits on Oct 8, 2012
  1. @olivergierke
Commits on Sep 21, 2012
  1. @olivergierke

    DATAJPA-257 - Make count query execution in SimpleJpaRepository more …

    olivergierke authored
    …robust.
    
    The execution of a count query can potentially return multiple values instead of just a single one. This causes persistence providers to throw an exception as we trigger ….getSingleResult() in SimpleJpaRepository. We're now calling …getResultList() and sum up all values returned.
Commits on Aug 30, 2012
  1. @olivergierke

    DATAJPA-253 - Fixed application of Specifications.not(…).

    olivergierke authored
    Specifications.not(…) now also gets applied correctly when used without where(…) wrapper. Polished Specifications class, JavaDoc and added not null assertions.
Commits on Aug 24, 2012
  1. @spring-buildmaster
  2. @spring-buildmaster
  3. @olivergierke
Commits on Aug 13, 2012
  1. @olivergierke

    DATAJPA-244 - Use ClassLoader of EntityManager for implementation loo…

    olivergierke authored
    …kup.
    
    JpaClasUtils.isEntityManagerOfType(…) now uses the given EntityManager's ClassLoader to try to load the given concrete classname. We're actually using the EntityManager's delegate here which is usually some provider specific implementation (e.g. a Hibernate Session). This assumes that the ClassLoader who initially loaded the class to create the delegate instance will also see the special EntityManager interface.
  2. @olivergierke

    DATAJPA-245 - Listing all compile time dependencies directly.

    olivergierke authored
    We've been relying on some compile time dependencies being pulled in transitively. This is now fixed by declaring those locally.
Commits on Aug 2, 2012
  1. @olivergierke
Commits on Jul 31, 2012
  1. @olivergierke
Commits on Jul 23, 2012
  1. @spring-buildmaster
  2. @spring-buildmaster
  3. @olivergierke
  4. @olivergierke
  5. @olivergierke
Commits on Jul 19, 2012
  1. @olivergierke

    DATAJPA-232 - Fixed parameter binding in SimpleJpaRepository.findAll(…

    olivergierke authored
    …Iterable<ID> ids).
    
    We bound the given Iterable<ID> using List as parameter type which gets rejected if you hand in something that's not a List actually (e.g. HashSet). Changed parameter binding to hand in Iterable now.
Commits on Jul 18, 2012
  1. @olivergierke

    DATAJPA-226 - Working around ambiguities in the JPA spec.

    olivergierke authored
    We now expect a much broader range of exceptions possibly popping up from EntityManager.createQuery(…). It turns out the spec is not very strict about what must be returned from the call in case the provided query String is invalid. E.g. Hibernate seems to throw an IllegalStateException in case the query seems generally acceptable but has a typo in some keyword.
    
    We now catch RuntimeException invoking the call and simply rethrow the original exception if it is an IllegalArgumentException indeed but wrap any other into an IAE.
    
    See http://java.net/projects/jpa-spec/lists/jsr338-experts/archive/2012-07/message/17
Commits on Jun 6, 2012
  1. @olivergierke
Commits on Jun 1, 2012
  1. @olivergierke

    DATAJPA-217 - Added Hibernate JPA model generator.

    olivergierke authored
    We now distribute the JPA Criteria API meta-model classes for AbstractPersistable and AbstractAuditable.
Commits on May 23, 2012
  1. @olivergierke
  2. @olivergierke
Commits on May 16, 2012
  1. @spring-buildmaster
  2. @olivergierke
  3. @olivergierke
  4. @olivergierke
  5. @olivergierke

    DATAJPA-212 - Polished pom for release.

    olivergierke authored
    Removed obsolete staging profile. Fixed inception year. Fixed site deployment URL. Removed deployment repositories as we're releasing through Artifactory.
  6. @olivergierke

    DATAJPA-211 - Documented CDI integration.

    olivergierke authored
    Added brief section on how to use the CDI extension. Poslished documentation in general: updated copyright year, removed revision history, fixed links to Maven repositories, added missing section ids to create stable links, improved CSS for HTML rendering, improved PDF rendering.
  7. @olivergierke

    DATACMNS-171 - Let JpaQueryMethod new method of QueryMethod.

    olivergierke authored
    Drop custom method to determine whether a query method returns an entity and rather use the newly introduced method in Spring Data Commons' QueryMethod.
Commits on May 15, 2012
  1. @olivergierke

    Improve project setup.

    olivergierke authored
    Reactivated test cases that were not executed because they were named *Test, not *Tests. Upgraded to Maven Surefire Plugin 2.12 and activated parallel test execution per method. Upgraded Maven Compiler Plugin to 2.4.
  2. @olivergierke

    DATAJPA-207 - Fixed query creation for projections on native queries.

    olivergierke authored
    When executing a projecting query through a native query we must not use em.createNativeQuery(String, Class<?>) as this expects an entity type as type parameter. We now use the newly introduced isQueryMethodForEntity() on JpaQueryMethod to determine whether the query is actually projecting and rather use the plain em.createNativeQuery(String).
    
    Fixed dependency configuration for Hamcrest and JUnit (upgrade to JUnit 4.10, depending on junit-dep).
Commits on May 11, 2012
  1. @olivergierke
  2. @nebhale @olivergierke

    DATAJPA-210 - System property control of Bundlor configuration

    nebhale authored olivergierke committed
    Added the ability to control whether Bundlor will fail on warnings or whether it is enabled at all, using Java system properties. By default, Bundlor will be enabled and will fail on warnings. Specifying `-DfailOnWarnings=true/false` and `-Dbundlor.enabled=true/false` as part of the Maven command will now
    control Bundlor's operation.
Commits on May 2, 2012
  1. @olivergierke
Something went wrong with that request. Please try again.