On Tue, Oct 19, 2010 at 8:07 AM, Phil Adams <padam...@gmail.com> wrote:
> Hi Lukasz, > Thanks for the information... I read about ExecuteAndWaitInterceptor > but it seems as though that must create a new thread as well, since it > also uses the BackgroundProcess class to execute the action, right? > In this particular situation, I need to find a way for the action's > execute() method to be called on the servlet container's original > thread, rather than on some new thread created by Struts. > > Thanks > > Is there a reason why the customer's action is using the ExecuteAndWaitInterceptor? I guess what I am saying is that I am hearing conflicting information. You want the action to execute in the container's request handling thread, but you are using exec&wait. You can't have both... Remove the exec&wait interceptor from the action's interceptor stack and see if you get the results you are looking for... However, (warning), if the original developer configured the action to use exec&wait, he/she may have had a reason and removing the interceptor may have unintended side effects. -Wes -- Wes Wannemacher Head Engineer, WanTii, Inc. Need Training? Struts, Spring, Maven, Tomcat... Ask me for a quote!
