Hi David, It has been a while, but the details and suggestions on running app-composer test made my July very busy - refactoring a vast selection of OpenEJB tests (making it run significantly faster). I like the idea of @PreProcess and @PostProcess - this looks like something I'm looking for. My intention is to leverage tools like Mockito or Easymock. I'm still not sure if that's gonna work - I hope so. At the moment I'm building inner classes, which mock certain pits and pieces of functionality and use them in application composer to build the context. This is not as flexible as I'd love to - but works better in my tests that complete classpath scanning. What you've shown in examples from OpenEJB 4.0 looks similar and it seems sufficient for everything I can imagine. A little bit more verbose, but it's not an issue (at least from my perspective).
The other issue I was initially trying to solve, disappeared when I used app-composer approach. In my application I have multiple implementation of same business interface, deployed among multiple ears. During tests with OpenEJB I have little control over what gets injected where. Now, I can build and deploy multiple EjbJar, knowing exactly what gets wired and where. Honestly, after this discussion and after trying out a few things I don't feel I need any other 'frameworks' and in terms of testing OpenEJB works great for me. I'll be still pushing 3.1.4 version (which is one I'm currently using) and I'm looking forward to 4.0 :-) Once again - many thanks --Jakub -- View this message in context: http://openejb.979440.n4.nabble.com/override-annotation-based-configuration-with-ejb-jar-xml-tp3628804p3699370.html Sent from the OpenEJB User mailing list archive at Nabble.com.
