How about this then: Define all publishing to be global and via JNDI.
A container is told to publish services X, Y and Z, and to bind them to certain points in the JNDI context: <publish service="<service id>" as="java:/SomeName"/> <publish service="<other service id>" as="java:/SomeOtherName"/> and in the super-container: <import service="<service id>" from="java:/SomeName"/> <import service="<other service id>" from="java:/SomeOtherName"/> The super-container can then access these services via JNDI and import them into its namespace that way. > You also missed out on a bunch of good stuff because you have > already decided in your mind that you want to publish > interfaces. You will kill whatever hopes of success you have > when you make up your mind and *refuse* to hear any other conclusion. The only thing I'm saying is that publishing *does* have a place in the Avalon architecture, and that it *can* be done in a predictable and secure way. Let's not get into a discussion about how open- or closed-minded you or I am. Take a look at the publishing-via-JNDI above and tell me if it seems OK. /LS -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
