--- Ted Slusser <[EMAIL PROTECTED]> wrote: > Yes. You've already solved the problem, but:
(1) You only need to define your actions explicitly if you're wiring them manually. (2) Normally action beans are configured to the "prototype" scope (the current Spring plugin docs [1] are for Spring version < 2; if you're using Spring 1 then they're correct). I don't know of any particular reason using request scope wouldn't work, I've just never done it. Including a problematic Spring action configuration would have assisted in helping more quickly; it would have eliminated another call/response cycle. d. [1] http://struts.apache.org/2.x/docs/spring-plugin.html [tags: s2, spring, config] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
