Nicola Ken Barozzi wrote: > That's also why many outsiders say: "Hey, we have commons-logging, > JNDI, JMX, why do you want to rewrite all?".
But the point is not to re write anything. Straight OO is terrific if you don't mind tight coupling inside your code base. But if you want to use JXXX and have looseCoupling/reUse/COP then you take the JXXX implementation, make a separate JXXX Avalon interface for it, and presto changeo, you have a loosely coupled JXXX that can take any number of competing JXXX (or similar) implementations. Do one thing. Do it well. Avalon is for looseCoupling/reUse/COP. That is it's promise. Neither complex nor hard to grasp. Fulfill that promise first, play later. And if acheived, the holy grail of open source, because tightly coupled open source sux. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
