QueryTest and Co. are broken in TestNg.

[jmoore]

All subclasses of the Spring transaction-managing test are broken with testng. The configuration of the context is somehow going amiss.

ome.conditions.InternalException:  Wrapped Exception: (org.springframework.transaction.IllegalTransactionStateException):
Pre-bound JDBC Connection found - HibernateTransactionManager does not support running within DataSourceTransactionManager if told to manage the DataSource itself. It is recommended to use a single HibernateTransactionManager for all transactions on a single DataSource, no matter whether Hibernate or JDBC access.
	at org.springframework.orm.hibernate3.HibernateTransactionManager.doBegin(HibernateTransactionManager.java:430)
	at org.springframework.transaction.support.AbstractPlatformTransactionManager.getTransaction(AbstractPlatformTransactionManager.java:283)
	at org.springframework.transaction.interceptor.TransactionAspectSupport.createTransactionIfNecessary(TransactionAspectSupport.java:234)
 	at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:93)

[jmoore]

http://tearesolutions.com/blog/?p=9 seems to be explain some of these problems. Specifically, that the mixing of direct JDBC and Hibernate managed calls can lead to problems. This has apparently surfaced with the TestNG-ification of our JUnit tests.

[jmoore]

r677 updates testng framework so it can be more easily run from Eclipse. This problem has been verified in Eclipse and Ant, but only when running multiple tests from testng.xml.

[anonymous]

r683 cleans up tests and shows this as fixed. Currently some 127 tests are passing, 9 failing, and a dozen disabled (in server/).