|
From: Keith D. <ke...@in...> - 2005-04-05 17:21:29
|
I am running into issues preparing a simple flow execution test sample for the phonebook app. Specifically I need the following: - 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? - 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. Keith Keith Donald Interface21 - http://www.springframework.com <http://www.springframework.com/> - Spring Training, Consulting and Support - "From the Source" |