jsr338-experts@jpa-spec.java.net

[jsr338-experts] Improving the TCK

From: Oliver Gierke <ogierke_at_vmware.com>
Date: Tue, 17 Jul 2012 02:22:25 -0700

Hi all,

during my development on Spring Data JPA I've stumbled over a few issues in various persistence providers [0], [1]. I wondered why they were not discovered by the TCK actually as the ones I listed clearly could have. So I wonder whether it was possible to tighten the TCK in this regard which leads to the following questions:

1. The original JSR for JPA 2.0 [2] stated in section 2.18:

> The Java Persistence API, version 2.0 Technology Compatibility Kit (TCK) will be available both as a standalone TCK and included as part of the Java EE 6 Compatibility Test Suite (CTS). The Java Persistence API, version 2.0 Reference Implementation (RI) will be available both separately and as part of the Java EE 6 RI.

Where can one get access to the standalone version of the JPA 2.0 TCK?

2. How can we actually help out to improve the TCK? I wouldn't mind investing some time to actually work on the code (assuming the TCK consists of JUnit tests e.g.)

Cheers,
Ollie

[0] https://bugs.eclipse.org/bugs/show_bug.cgi?id=322579
[1] https://hibernate.onjira.com/browse/HHH-6896
[2] http://jcp.org/en/jsr/detail?id=317

-- 
/**
 * @author Oliver Gierke - Senior Member Technical Staff
 *
 * @param email ogierke_at_vmware.com
 * @param phone +49-351-30929001
 * @param fax   +49-351-418898439
 * @param skype einsdreizehn
 * @see http://www.olivergierke.de
 */