Hi Ollie, all,
On 7/17/2012 2:22 AM, Oliver Gierke wrote:
> 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?
>
You can obtain a standalone license for the TCK through your Oracle
sales rep. Qualified non-profits can apply for a TCK scholarship.
> 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.)
>
Our TCK team advises me that what would be most helpful is to continue
to describe the cases that you've had problems with in different providers,
as pass that information on. The TCK engineers all track our expert
groups, so they read the feedback that is posted here.
thanks,
-Linda
> 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
>