Adam Hardy wrote:
Um? It's not obvious what the rationale is, I assure you. Of course the
Spring object factory is feature rich, but which particular features was
it? Or perhaps the lack of obviousness is just an artifact of the way I
have learnt the ropes of Struts2.
I don't think it's a
The Spring integration isn't something I'd looked into deeply. I just assumed
I'd be repeating my list of actions, knowing only what I have read about so far.
This isn't the first time struts2 has proved my assumptions wrong - and always
in a good way I'm glad to report.
Laurie Harper on
Did you set this in your struts.xml ?
constant name=struts.objectFactory value=spring /
or
constant name=struts.objectFactory value=
org.myorg.mySpringContextFactory /
For Autowiring, it's enable by default. But you can customise it :
http://struts.apache.org/2.0.9/docs/spring-plugin.html
Thanks for the explanation. What would you say the main rationale is then for
using Spring as a factory for the actions instead of the struts objectfactory?
Regards
Adam
[EMAIL PROTECTED] on 13/08/07 08:13, wrote:
Did you set this in your struts.xml ?
constant name=struts.objectFactory
Um, to allow all the capabilities of Spring (dependency injection, AOP
or whatever) to be applied to action instances?
L.
Adam Hardy wrote:
Thanks for the explanation. What would you say the main rationale is
then for using Spring as a factory for the actions instead of the struts
Um? It's not obvious what the rationale is, I assure you. Of course the Spring
object factory is feature rich, but which particular features was it? Or perhaps
the lack of obviousness is just an artifact of the way I have learnt the ropes
of Struts2.
It seems like struts2 says:
1: here's
6 matches
Mail list logo