|
From: Rod J. <ro...@in...> - 2005-04-06 10:55:01
|
Keith I will try to make any required enhancements today. > - the ability to DISABLE dependency checking by object for the autowired > test – sometimes defaults really do make sense, why always require a set > method to be called for each public setter? I've added a dependencyCheck property which you can call in a constructor. I've preserved the default dependency checking, which I think is useful. > - the ability to turn off/on transaction management – right now > AbstractFlowExecutionTests is runnable only in the context of a database > transaction. While this is great and all, if I want to integration test > flows outside of any transactional context, I’m screwed. I can’t > exactly subclass DependencyInjectedContextTests, as I still WANT THE > OPTION of being able to test flows in a transaction context – for the > flows that demand it. But the current structure doesn’t give me that > choice. I don't quite understand what you want here. Can you please be more specific? How would you drive this option? Rgds Rod |