Do you have a wildcard configuration in the XML that might be overriding your @Result? I can't remember the exact order of evaluation, but I think Conventions (assuming you're using Conventions, but we'll need version numbers and plugins to know better) is sort of the last-guy-on-the-totem-pole.
You might try to take a look at the config-browser plugin so that you can see your effective configuration on the action in question. -Wes On Tue, Dec 29, 2009 at 10:10 AM, Steve Mitchell <smitch...@byteworksinc.com> wrote: > I’m doing a redirect with annotations: @Result(name = “success”, > type=”redirect”, location=”home.action”), however, the resulting > ActionInvocation is a ServletDispatcherResult instead of > ServletRedirectResult. This is an issue because I'm attempting to use the > RedirectMessageInterceptor which expects a ServletRedirectResult. Why would > @Result type "redirect" result in a ServletDispatcherResult ? > > Steve Mitchell > http://www.ByteworksInc.com > -- Wes Wannemacher Head Engineer, WanTii, Inc. Need Training? Struts, Spring, Maven, Tomcat... Ask me for a quote! --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
