On Mon, 11 Feb 2002 09:15, MCCAY,LARRY (HP-NewJersey,ex2) wrote: > Perhaps now is a good time to reintroduce the idea of actually using JNDI? > > I think that it would be an acceptable alternative to introducing a new > package. > > I realize that JNDI seems a bit heavy for the immediate use but the > advantages of using the standard registry interface outweigh the negatives > IMHO.
For some users of Avalon/Framework JNDI would be fine - one example being Phoenix. However for other users of ant (Cocoon, Myrmidon etc) the overhead and complexity is not justified. Especially when there are a lot of people who are writing their own containers. Compare the complexity of org.apache.avalon.excalibur.naming.* to the complexity of DefaultComponentmanager. Sure you could make a more lightweigh JNDI implementation but even then it is considerably more complex than our basic DCM which is basically a facade on a hashmap. -- Cheers, Pete The avalanche has already started. It is too late for the pebbles to vote. -Ambassador Kosh -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
