In the Cocoon case your example is a very good solution, as component lookups would be handled as they should; through the internal Component manager.
yes, the joy of avalon container interoperability :)
In cases where no internal Component/Service managers exist, Avalon based or not, it gets messier. Luckily I don't think I have any case where the entry servlet's code is closed. In that case some hack overriding init( ServletConfig conf ) or service( ... ) could work, or just AltRMI.
AltRMI would work in that case. What would be *really* cool is a RemotingServiceManager or such that you could use in a client container, that would pass all lookups over AltRMI (or such) to an external container :)
What are the plans for the Sevak project btw? Is it going to be released at some point? What is still missing? Would jetty- jo- and catalina-sevak be different releases? Would it be released here at Avalon?
It will probably be released here at Avalon at some point. The main thing that is missing is documentation. I can envision an API-release and then separate releases of the different implementations.
-pete
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
