Given time and hand sight, I have looked at what's available for a developer looking for the magical tiger palm to ease the JNDI object lookup blisters.
The first suggested to me is the Service Locator, which I have found to be nothing more than a glorified Façade used to address a shortcoming in the resource binding mechanism (aka JNDI) of the J2EE.
I also read on theserve rside about a light weight EJB 3 proposal. This proposal does simplify the component model to a certain degree. But I would still like to have it simpler, especially with dependency injections. I see no reason why the code should define the semantics of resource lookup when structured configuration could do the job.
For a while I have known about the Inversion Of Control movement but never really understood it until now. I have used frameworks like Avalon, which place an emphasis on inverting control to a lightweight container. This container configures, start, dispatches invocation (performing argument validation to free the code from that), and shutting down the component. In between it provides concurrency management enabling the component to deal exclusively with business domain logic. Now I fully apprehend the IoC concept and I support it. If only the specification over at JCP can reflect this thought pattern things would be great for the enterprise developer community.
