I'm curious about the relationship between
EJB 3 and the test-driven development community, or even the lightweight
Java community, in general. It looks like EJB 3 was influenced to a degree by the ideas coming out of those communities, so if the authors have any story they'd care to share about that, I'd like to read it, positive or negative.
Also, I'm curious about the odd style of dependency injection that EJB 3 appears to have adopted. I admit that I've only looked at it briefly, but it appears not to have what I consider the true benefit of dependency injection, and that is an easy way to substitute
test doubles for EJB dependencies to make testing easier. I can see that the annotation-style injection removes the need for duplicating all the JNDI lookup code, but is that all it does?
Thanks. After years of telling people how to work around EJB, it's nice to see the potential for not having to give out that advice any more.
Take care.