I also want to know how I can run an EJB test that saves to the DB, but then roll back the data after the test is complete?
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, June 28, 2004 9:25 AM To: [EMAIL PROTECTED] Subject: EJB Test Design help? I need to see if someone an help me to design my Cactus tests for my EJB's. I have a composite DTO that has Entities that match: CreditAppDto |--> BusinessCard1 |--> Bank Account 1 |--> Bank Account 2 |-->BusinessLine |--> Guarantor[1..*] Now, this DTo get saved all at once in my Use Case. I have spit up the CreditApplicationManager methods into smaller chunks: CreditApplicationManager.createCreditApplicaton(...) CreditApplicationManager.createBusinessCard(...) CreditApplicationManager.createBusinessLine(...) CreditApplicationManager.createGuarantor(...) But, they all still get called from: CreditApplicationManager.conclude(CreditApplicationDto) Any design thoughts on how to test this scenario? --- > Thanks... > Mick Knutson > > 525 Market Street, SF, CA 94103 > (415) 222-1020 > [EMAIL PROTECTED] > MAC A0103-223 --- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
