On Tue, 2003-07-01 at 04:15, Laurent Rieu wrote: > You mean having Struts Action deployed as Avalon components and accessed by > the RequestProcessor through the Avalon container ? > > Laurent
Essentially yes. The new RequestProcessor would host an embedded container like Fortress or Merlin. Actions would be retrieved via the container. Currently Actions are just instantiated by getting the local classloader and creating a new instance. Instances are then held in a hashmap. The only real trick to this would be getting the configuration or assembly information to the container. It would be fairly easy to just use ContainerUtils and have the RequestProcessor be a simple container, but I would rather see the RequestProcessor host an entire container that way you could use other standard avalon services. I've done a number of struts apps but quite honestly I'm not very intimately familiar with the internals. Looks like there may be one RequestProcessor per module, so we may need a singleton instance of the container. Also handling the configuration of both the Actions and the container would be a little tricky. But you might be able to do all this without extending the ActionServlet, although that may be the easier route. I'm just barely starting to look into this, but it seems possible. -- jaaron <http://jadetower.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
