--- On Fri, 6/13/08, Page <[EMAIL PROTECTED]> wrote: > http://struts.apache.org/2.x/docs/writing-interceptors.html > > > > The result has already been rendered after the invoke, > so header > > modification would be a bit superfluous ;) > > > > I guess I'm going about this the wrong way. I want the > other developers on > the team to be able to write actions without worrying about > adding in code > to support the in-house framework, so an interceptor that > could execute > after the action seemed like a fit - except that it > can't modify the > request. So is there a better approach that could still > keep my actions > clean?
I think you may have missed the nub of my gist; I'm saying that the colored box at [1] with the blurb about the PreResultListener may be what you need. Dave [1] http://struts.apache.org/2.x/docs/writing-interceptors.html --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
