Hi, We are working with Appfuse and we really appreciate it. We have defined a custom manager that uses several daos. It does not extends any of appfuse manager classes.
It perfectly works in a test case when the test class used extends one of Appfuse test classes available. We followed indications found in this thread : http://www.nabble.com/-Appfuse2.0--Best-Practise-Design-Pattern-for-Multiple-Dao-Access-from-managers-td14116309s2369.html#a14370264 But, we get some errors when we try to test the same manager with a Junit or a Spring Test Case. The errors are about lazy loading. How should we define our custom manager so that it works without a specific appfuse context ? There must be some best practices to do this with appfuse. Could you please give us more information on how to handle this ? Thank you. Regards, Jonathan Dray
