I can't say that I see the problem, but I do see a few small issues.
> <bean id="springManagedProsocActionUpdateEmail"
> class="uk.co.prodia.prosoc.struts2.action.ActionUpdateEmail">
> <property name="sessionFactory"
ref="sessionFactoryProsocForum"/>
> </bean>
be sure to add scope="prototype". S2 actions are per-request (since they
have getters and setters with request specific information being set on
them). Basically, they're not thread-safe, so they can't be singletons.
> 5) Set the following constant in my struts.xml file:
>
> <constant name="struts.objectFactory.spring.autoWire" value="type" />
>
> 6) Set the following property on my spring-config <beans
> default-autowire="autodetect"> tag.
Technically those shouldn't be necessary. The struts autowire
capabilities of the spring-struts plugin are a little hard to
understand, but basically, here's how it works.: if the spring-struts
plugin can find an Action with the appropriate name that is managed by
Spring, it will use that one. If it can't, it will instantiate one and
then attempt to 'autowire' it itself. Here's where the autowire settings
come into play.
In your case, you want the first option (where the bean is fully spring
managed) so the struts autowire settings aren't really going to be used.
> 4) Modified the action class attribute to point to the id of the bean
in the
> spring-config file so that it looks like the following:
> <action name="update-email!*"
class="springManagedProsocActionUpdateEmail"
> method="{1}">
> <results in here ... ...>
> </action>
That seems like it should work. Have you tried it without the method
name pattern matching to see if it can find your Spring bean?
By the way, do you have Spring's
org.springframework.web.context.ContextLoaderListener setup as a
listener in web.xml? (it basically starts Spring up)
Brad Cupit
Louisiana State University - UIS
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
