I had thought the components.xml file would be a natural integration
point for Spring factory beans. To this end, I have written my own
WebWork enabler interface and exposed our Spring factories this way. It
seems lighter weight and a more natural WebWork integration point than
coupling the web-tier and the Spring Framework than creating new
dispatchers/interceptors.
Any thoughts?
P.S.: In my component, I access the factory bean using this type of
construct:
WebApplicationContext appContext =
WebApplicationContextUtils.getWebApplicationContext(
ServletActionContext.getServletContext());
(IntranetSession) appContext.getBean("nameOfSpringFactoryBean");
It doesn't give me any gee-whiz XML configurable component, but the
components.xml file should be made to allow parameters in the <class>
tag at some point. If this is done, then this approach gets more
dynamic.
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
