But... what if I have a component that wants to make service calls but is not itself an Avalon Framework component, and is not itself loaded by the Avalon container?
This might be, say, a Servlet, or a Portlet. These things have their own container, which doesn't know anything about "Serviceable".
I think it comes down to two different possible ways for a component to get the service manager to make calls:
1 - the Avalon way, where the component is given the manager to use by it's container
2 - where there's a static class method somewhere that anybody (within the same classloader, of course) can call to get the service manager to make calls.
Turbine (old turbine) uses method #2.
I don't see any other ways - do you?
So, it seems like the solution to let a Portlet make Avalon Framework component calls is to have our Avalon Framework container include a static class that will give up the service manager on request.
But I wonder if this has already been addressed by the Avalon community, and if so, if there's a more elegant solution.
Thanks,
- Glenn
Glenn R. Golden CHEF Architect System Research Programmer III School of Information + Media Union @ University of Michigan [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
