Ok, then I know what is wrong. You are using a combination that is not supported generate.jpa.annotation=false generate.test.annotation=true (by default)
This will cause the junit test classes to extend AbstractDbUnitJpaTests, which requires other things. JPA, Spring annotations and JUnit annotations are new default features in Sculptor 1.6.0. If you still want to use the old style you need to add these properties: generate.jpa.annotation=false generate.spring.annotation=false generate.test.annotation=false With this configuration the junit tests will extend IsolatedDatabaseTestCase. I don't think generate.spring.annotation=false has anything to do with this issue, and it might be possible to use spring annotations = true in combination with jpa and test = false, but that is an area that is not well tested. /Patrik Jef Pfeiffer wrote: > > I¹m using 1.6.0 > > I have no EntityManagerFactory-text.xml. > Nor does my applicationContext-test.xml refer to one. > > ApplicationContext-test is (trimmed): > > <beans> <context:annotation-config/> <context:component-scan > base-package="com.intuit.services"/> <import > resource="classpath:/SessionFactory-test.xml"/> <import > resource="classpath:/Interceptor-test.xml"/> <import > resource="classpath:/more-test.xml"/> </beans> > > Sculptor generator properties: > deployment.type=ear deployment.applicationServer=JBoss db.product=oracle > generate.jpa.annotation=false #generate.repository.hibernateSupport=true - > bug report accepted 9/14 generate.gapClass=true > generate.serviceContext=false project.nature=business-tier > 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 > > Starting from scratch (deleting everything but src/main/resource) I get > the > same issue (no EntityManagerFactory-test.xml). > > Can you reply with the bean definition I need? > > On 9/14/09 11:41 AM, "Patrik Nordwall" <patrik.nordw...@gmail.com> wrote: > >> >> >> txManager is normally generated in EntityManagerFactory-test.xml, which >> is >> imported by applicationContext-test.xml >> >> Please verify EntityManagerFactory-test.xml. >> >> What version of sculptor and configuration are you using? >> >> /Patrik >> >> >> >> >> >> Jef Pfeiffer wrote: >>> > >>> > When I take the flag out I get a different problem. >>> > >>> > Specifically: >>> > >>> > 4376 WARN TestContextManager - Caught exception while allowing >>> > TestExecutionListener >>> > >>> [org.springframework.test.context.transaction.TransactionalTestExecutionList >>> > e...@7fc4a2d3] to process 'before' execution of test method [public >>> void >>> > >>> com.intuit.services.acs.service.api.FirmManagerTest.testAddUpdateFirm() >>> > throws java.lang.Exception] for test instance >>> > [null(com.intuit.services.acs.service.api.FirmManagerTest)] >>> > org.springframework.beans.factory.NoSuchBeanDefinitionException: No >>> bean >>> > named 'txManager' is defined >>> > >>> > Any ideas? >>> > >>> > >> >> -- >> View this message in context: >> http://www.nabble.com/Question-on-error-running-unit-tests-in-eclipse-tp254174 >> 29s17564p25439226.html >> Sent from the Fornax-Platform mailing list archive at Nabble.com. >> >> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >> 30-Day >> trial. Simplify your report design, integration and deployment - and >> focus on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> Fornax-developer mailing list >> Fornax-developer@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/fornax-developer >> > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > 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-tp25417429s17564p25440683.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Fornax-developer mailing list Fornax-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fornax-developer
