Hi, We have tried to rewrite the built-in UserManager of appfuse, and came up with our own UserManager. For the test case of our UserManager, given a code which accesses a collection field, it returns LazyInitializationException, i.e. user.getAccounts().get(0).
The collection field is configured as FetchType.LAZY. Did I miss something here?? At the DAO test case, it works fine, (got some readings on AbstractTransactionalDataSourceSpringContext, and it seems like, this one solves the Lazy loading problem on the DAO test case), but when it comes to the Service test case, it fails, found out that BaseManagerTestCase extends the AbstractDependencyInjectionSpringContext and not the class DAO base test case uses. Does it matter? How come? Thanks. -- View this message in context: http://www.nabble.com/LazyInitializationException-in-XXManagerTestCase-tf3684711s2369.html#a10299277 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
