struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Husted <hus...@apache.org>
Subject Re: Multiple controller servlets
Date Tue, 04 Dec 2001 03:37:56 GMT
These wouldn't exist as such on the ActionResource interface I
suggested. These are really just shortcuts to the API for the underlying
resources, like 

formBeans.addFormBean(formBean);

So, if someone wanted to do them through an ActionResources object, they
could do the same thing

actionResources.getFormBeans().addFormBean(formBean);

I believe the real reason they are on ActionServlet is for the digester.
The admin Actions are fun, but I doubt that they are used much, except
for reload, which calls a different set of methods.

But, again, my first thought for the ActionResource interface was to
expose the resources to other components. 

The big ticket on ActionServlet would be to refactor those nasty
process*  methods into a coherent helper object.

Donnie Hale wrote:
> 
> Ted,
> 
> There are a number of public methods on ActionServlet right now like:
> 
> addDataSource
> addFormBean
> addForward
> addMapping
> 
> Some of them are used in various actions package classes to do things
> dynamically. I'm guessing that there are deployed Struts apps out there
> which also use these methods as well.
> 
> Do you have any thoughts on how this functionality should be supported?
> Would these be additional methods on your proposed interface?
> 
> Thanks,
> 
> Donnie

--
To unsubscribe, e-mail:   <mailto:struts-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-dev-help@jakarta.apache.org>


Mime
View raw message