Wes Wannemacher wrote:
http://struts.apache.org/2.1.6/struts2-
core/apidocs/com/opensymphony/xwork2/spring/interceptor/ActionAutowiringInterceptor.html
It's a bit confusing, but it really depends on how you want autowiring to
happen.
I've been happily using the spring plugin which wires up my actions
(because they're defined as spring beans--I think I'd missed that
point--thanks for the clarification :-).
The bit that's been causing me grief lately isn't autowiring the
actions, though, but autowiring a custom interceptor based on
http://cwiki.apache.org/WW/hibernateandspringenabledexecuteandwaitinterceptor.html
That interceptor needs the hibernate SessionFactory so it can create a
long-lived session to go along with the long-running process.
I've not focused on debugging this, yet (bigger fish to fry at the
moment) but I believe in 2.1.6 I'm having difficulty because this
interceptor isn't always being wired up correctly.
I did recently add a definition for this interceptor to my
WEB-INF/action-servlet.xml -- maybe that was the source of my troubles?
I don't think that cleared up my issues, though. When I have time to
track this down I'll find out.
The interceptor depends on the SpringObjectFactory, so it is necessary to have
the Spring plugin installed.
Is it appropriate for struts to be distributed with an interceptor that
doesn't work without the plugin? Doesn't that argue that the
interceptor should be packaged *with* the plugin?
-Dale
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
