I never thought I would find dependency injection all that interesting until this past week when I realized how useful it could actually be. In an effort to tinker with aspects further, I ended up creating an aspect that can look up and inject an EJBHome. Sure, it’s not much but it’s amazing how much cleaner you code can be when using dependency injection like this. Now sure, EJB3 sports dependency injection which is great, but what do you do about the client side of things? With those dependencies being handled in the container, how or can a rich client take advantage of EJB3’s dependency injection? I’m digging in some more and I’m sure I’ll be tinkering a bit more over the holidays.
2 thoughts on “Dependency Injection on the Client”
Comments are closed.
It is taking every ounce of personal restraint to not make a really rude joke in your comment section about hot dependency injections.
LikeLike
It is taking every ounce of personal restraint to not make a really rude joke in your comment section about hot dependency injections.
LikeLike