[jira] Commented: (OPENJPA-61) Missing usage of TransactionSynchronizationRegistry

[ http://issues.apache.org/jira/browse/OPENJPA-61?page=comments#action_12443877 ] Kevin Sutter commented on OPENJPA-61: - It's turning out that we have two problems to resolve via this defect. The first (more immediate) problem is to remove

[jira] Assigned: (OPENJPA-61) Missing usage of TransactionSynchronizationRegistry

[ http://issues.apache.org/jira/browse/OPENJPA-61?page=all ] Kevin Sutter reassigned OPENJPA-61: --- Assignee: Kevin Sutter > Missing usage of TransactionSynchronizationRegistry > --- > > Key

[jira] Commented: (OPENJPA-61) Missing usage of TransactionSynchronizationRegistry

[ http://issues.apache.org/jira/browse/OPENJPA-61?page=comments#action_12443882 ] Kevin Sutter commented on OPENJPA-61: - Question: From a pure JPA perspective, you would need WebSphere v6.1 Application Server in order to use OpenJPA within

[jira] Commented: (OPENJPA-61) Missing usage of TransactionSynchronizationRegistry

[ http://issues.apache.org/jira/browse/OPENJPA-61?page=comments#action_12443894 ] Patrick Linskey commented on OPENJPA-61: I'd say that we (OpenJPA) should not worry about the older versions -- we (BEA) will just need to add the appropri

Re: svn commit: r465623 - in /incubator/openjpa/trunk/openjpa-persistence-jdbc/src/test/java/org/apache/openjpa/persistence/generationtype: ./ IdentityGenerationType.java TestGenerationType.java

Hi, I like to have both setUp and tearDown in my test cases. In another project, we created a "mother of all test cases" and defined a setUp and tearDown there that did some routine stuff that many test cases needed, such as removing persistent instances that would cause subsequent test c