On 3/13/2013 8:55 AM, Oliver Gierke wrote:
> I haven't looked as deeply into the code as Steve yet, but I'd like to get a general idea of how the feedback process is expected to work. Assuming I'd like to add additional test cases to the TCK or have comments on existing tests, what's the preferred way to communicate those? For the latter emailing the EG mailing list seems to be fine. The former - through Git patches maybe?
>
Hi Ollie,
You should send your suggestions to me.
regards,
-Linda
> Cheers,
> Ollie
>
> Am 13.03.2013 um 16:16 schrieb Steve Ebersole<steve.ebersole_at_redhat.com>:
>
>> As I understand it the current TCK drop is not supposed to be final, but I have found serious problems with it. To the point where it is essentially unusable.
>>
>> First, the signature tests are wrong. Running against the JPA API jar I created for Hibernate testing using the latest Proposed Final Draft I get errors that "javax.persistence.criteria.CommonAbstractQuery" is missing from my jar. But javax.persistence.criteria.CommonAbstractQuery was removed from the spec way back in Draft 6.
>>
>> Second, I am completely unable to run any of the actual persistence tests. Every single one of them fails in perfoming set up. The error is always the same:
>>
>> 03-13-2013 01:22:19: ERROR: Map returned from emf.getProperties() was null,this should never occur
>>
>> However, it is impossible for the Hibernate EMF to return a null Map there. So, since I can't actually debug the tests (or please I'd love to have details on how to actually accomplish that) I fell back to caveman debugging and put throwing exceptions as the first thing I do inside (1) the Hibernate PersistenceProvider#createEntityManagerFactory call and the constructor to the Hibernate EMF impl. Neither gets triggered. So that tells me that the TCK is not even attempting to call out to the configured "alternate provider"
>