Welcome Glenn! Comments inline below:
> -----Original Message----- > From: Glenn R. Golden [mailto:[EMAIL PROTECTED] <snip/> > 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? With Servlets and Fortress, you can get a hold of the ServiceManager fairly easily. See http://jadetower.org/vqwiki/jsp/Wiki?FortressServlet for an example of putting the ServiceManager in a ServletContext. Not sure what the best way to do this in Merlin is. I think someone was working on it. A better solution would be to have JNDI lookups of services. I've been working a little on this for Merlin, but don't have anything available yet. Point is, there are definitely other ways and hopefully this will become simpler in the future. > 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. If you search the mail archives, there have been several discussions about using Avalon in servlets, EJB's, and other contexts. jaaron --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
