> From: Michael McKibben [mailto:[EMAIL PROTECTED]] > > Isn't this a chicken-and-the-egg problem? The CM must know > which component instance to call lookup() on! Perhaps if it > was a static method that was introspected, but I'm not sure > that is a viable solution. JNDI has some nifty solutions that > might be possible to borrow from, e.g. the Referenceable > interface and the ObjectFactory/ObjectFactoryBuilder.
Any solution which uses static accessors to get an instance will be vetoed on grounds of breaking IOC. It also makes it a whole lot more difficult to enforce proper security. The closer we get to JNDI, the more I will push using JNDI. Peter and I have both done implementations of JNDI lookup, and it is not that fun. However, it would make us more aligned with J2EE principles. As has been pointed out a long time ago, we want to be able to define a container that works in a constrained environment. That is one of the principle reasons JNDI was ruled out. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
