If I add a method in my unit test class which contains the entity as one of the parameters why the dependency won’t get injected ?

I just solved my problem with your nice Article.
In my case, i’m using weblogic 10 and i wanted to inject the beans into the PageFlowController’s

Thank you and congratulations for the great job.

I have to admit I have been reading your blog at a high-pace, so I had probably missed what you just said. It is still on my to-read list. Thanks for your comment!

With the risk of being slightly off topic, I just want to clarify one point regarding my blog article mentioned above.

The solution from my post (number 4) does not do DI for Hibernate instantiated objects only. Instead, we tell Hibernate to use our factories to DI the newly instantiated beans. This way, both a factory method and a Hibernate instantiated bean use the same DI code.

If you were to create a bean for the first time, you would be using the factory and hence the object would also be dependency injected.

The spring-aspects jar also contains some abstract aspects that you can implement to define your own wiring. That way, you do not have to depend on the @Configurable annotation. Personally, I don’t really mind having a dependency on Spring. How big are the odds of you changing the IoC framework? If so, you’ll have to do such a big refactoring, that removing the annotation is just a little extra effort.

The problem with James’ solution #4 is that you only have dependencies injected when you retrieve an object from your hibernate session. When instantiating a new object, these dependencies are not available yet.

I am currently building a small application using Domain Driven Design, just to get a feel for the point of view of “the other guys”. I (still) am a “separate infrastructure and domain” type of guy too. However, I do see that there is a valid point in DDD when they talk about reusability. DDD looks a lot dryer, but you do seem to get a lot of mixing of concerns in return. Spring’s easy-to-do Load Time Weaving might offer an option here. I’ll give DDD a chance, and you’ll see my results on this blog as soon as I am done investigating.

Good stuff; I know from experience how nice it would be from time to time to be able to inject managed resources into the domain layer, so I definitely like the concept. Also, I knew Spring had introduced LTW support but have never looked at it in-depth, so thanks for a clear and short article on how to get it working.

The only thing I don’t like about the current set-up, though, is that it relies on an annotation. This visibly binds the code to Spring in return for DI only. For that reason, if I were to use LTW, I would consider going the last few meters and using AspectJ — as you suggest. It’s still binding to a framework that can provide the capability, but you get a little more bang for your buck.

Thanks again!

Ben.