That was it. Thanks, Patrik.
On 9/16/09 1:23 PM, "Patrik Nordwall" <patrik.nordw...@gmail.com> wrote:
>
>
> That error has to do with the version of DBUnit.
> Change to
> <dependency>
> <groupId>dbunit</groupId>
> <artifactId>dbunit</artifactId>
> <version>2.1</version>
> <scope>test</scope>
> </dependency>
>
>
> /Patrik
>
>
> Jef Pfeiffer wrote:
>> >
>> > On further exploration, it looks like even when the spring.annotation is
>> > set
>> > to false I get the SQL exception on teardown.
>> >
>> > Any ideas?
>> >
>> > java.sql.SQLException: Connection is closed.SQLException: Connection is
>> > closed. at
>> >
>> org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.checkOp
>> > en(PoolingDataSource.java:174) at
>> >
>> org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.prepare
>> > Statement(PoolingDataSource.java:277) at
>> >
>> org.fornax.cartridges.sculptor.framework.util.db.DatabaseExport.getTables(Da
>> > tabaseExport.java:110) at
>> >
>> org.fornax.cartridges.sculptor.framework.util.db.DropAllTablesOperation.exec
>> > ute(DropAllTablesOperation.java:40) at
>> >
>> org.dbunit.AbstractDatabaseTester.executeOperation(AbstractDatabaseTester.ja
>> > va:190) at
>> >
>> org.dbunit.AbstractDatabaseTester.onTearDown(AbstractDatabaseTester.java:109
>> > ) at org.dbunit.DatabaseTestCase.tearDown(DatabaseTestCase.java:169)
>> > at
>> >
>> org.fornax.cartridges.sculptor.framework.util.db.IsolatedDatabaseTestCase.te
>> > arDown(IsolatedDatabaseTestCase.java:89) at
>> > junit.framework.TestCase.runBare(TestCase.java:140) at
>> > junit.framework.TestResult$1.protect(TestResult.java:110) at
>> > junit.framework.TestResult.runProtected(TestResult.java:128) at
>> > junit.framework.TestResult.run(TestResult.java:113) at
>> > junit.framework.TestCase.run(TestCase.java:124) at
>> > junit.framework.TestSuite.runTest(TestSuite.java:232) at
>> > junit.framework.TestSuite.run(TestSuite.java:227) at
>> >
>> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81
>> > ) at
>> >
>> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestRef
>> > erence.java:45) at
>> >
>> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:3
>> > 8) at
>> >
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRu
>> > nner.java:460) at
>> >
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRu
>> > nner.java:673) at
>> >
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.
>> > java:386) at
>> >
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner
>> > .java:196)
>> >
>> > Sculptor configs are...
>> >
>> > project.nature=business-tier deployment.type=ear
>> > deployment.applicationServer=JBoss
>> > generate.jpa.annotation=false generate.test.annotation=false
>> > generate.spring.annotation=false generate.gapClass=true
>> > generate.serviceContext=false
>> > db.product=oracle db.oracle.type.Blob=BLOB javaType.Blob=java.sql.Blob
>> > hibernateType.Blobl=blob
>> >
>> framework.applicationExceptionClass=com.intuit.services.acs.exception.ACSApp
>> > licationException
>> >
>> framework.accessBaseWithExceptionClass=com.intuit.services.acs.accessimpl.AC
>> > SAccessBaseWithException
>> > package.serviceInterface=service.api
>> > package.serviceImplementation=service.impl
>> > package.serviceProxy=service.proxy package.exception=domain.api.exception
>> > package.repositoryInterface=repository.api
>> > package.repositoryImplementation=repository.impl
>> > package.accessInterface=repository.access.api
>> > package.accessImplementation=repository.access.impl
>> > package.domain=domain.impl
>> >
>> > Thanks for any insight you can provide...
>> >
>> >
>>
------------------------------------------------------------------------------
>> > Come build with us! The BlackBerry® Developer Conference in SF, CA
>> > is the only developer event you need to attend this year. Jumpstart your
>> > developing skills, take BlackBerry mobile applications to market and stay
>> > ahead of the curve. Join us from November 9-12, 2009. Register
>> > now!
>> > http://p.sf.net/sfu/devconf
>> > _______________________________________________
>> > Fornax-developer mailing list
>> > Fornax-developer@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/fornax-developer
>> >
>> >
>
> --
> View this message in context:
> http://www.nabble.com/Question-on-error-running-unit-tests-in-eclipse-tp254174
> 29s17564p25477822.html
> Sent from the Fornax-Platform mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Fornax-developer mailing list
> Fornax-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/fornax-developer
>
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Fornax-developer mailing list
Fornax-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fornax-developer
