I've not really finished it yet. When it is it should expose an interface that would allow blocks to depend on it and add hosts and webapps/war files. It should be quite good.
It still won't help in your communication with Coocoon using RMI. Cocoon is not a block in it's own right *yet*. I guess if it was it would also solve your problem. I've talked to Berin about this and he thinks that it could, in the future, be a block as well as a WAR file deployable app.
Having Cocoon as a block would solve my problem, or having the ability for webapps running inside of the Bay wrapper to depend on other blocks would too.
Correct me if I'm wrong here, but a block that implement Composable gets a handle to the ComponentManager that contains all other loaded blocks (or blocks that the Composable blocks has marked as dependencies). Could that ComponentManager be made availble via the JNDI InitialContext that Tomcat4 provides to webapps? That ComponentManager could then be set as the parent CM for the one Cocoon creates for itself. Then whenever an attempt it made to look up a dependent block, it will fall through to the CM we got via the InitialContext.
If this sounds feasible, let me know. I'm more than happy to help implement it. -pete
-- peter royal -> [EMAIL PROTECTED] managing partners, inc. -> http://www.managingpartners.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
