Hi Aaron, J Aaron Farr wrote: > 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.
We've done something like this for our own internal framework. > 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. The basic idea for initialization was to use an application listener that initializes (and deinitializes) the Fortress container. This container is saved in the servlet context. The servlet itself requests the container in Servlet.init i.e. you would have to subclass AcctionServlet for Struts and keeps it in a private field. Each incoming request is then routed to the root Fortress container working as a Struts RequestProcessor. > I'm just barely starting to look into this, but it seems possible. It definitely is. Regards, J�rg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
