The BaseDaoTestCase extends Spring's AbstractTransactionalDataSourceSpringContextTests - which rolls back each transaction after the test method executes. This is the reason you don't see your database change after running your tests. I believe you can use setComplete() in your test method if you want to change that behavior. See Spring's Javadocs for more information.
Matt On 3/16/07, paulie <[EMAIL PROTECTED]> wrote:
I am using AppFuse 2.0 and have set up the Hibernate tutorial. Having problems saving the Person to the database. I have commented out the code to remove the person (it was failing here anyways) and I would expect that I would be able to see the saved Person on the table after executing PersonDaoTest. Checked the surefile-reports but didn't see any failure messages. The personDao.get(person.getId()) following the save and flush seems to be successful. FindPersonByLastName() also successful. Haven't been able to run inside of Eclipse to debug. Any ideas? -- View this message in context: http://www.nabble.com/PersonDaoTest-not-saving-to-Person-table-tf3414722s2369.html#a9515264 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- http://raibledesigns.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
