Don
Matt Raible wrote:
I'll assume from the lack of responses that no one cares what we do with this plugin. Nice! ;-) I think this is a great plugin, especially since it enables Struts Actions to be tested using MockStrutsTestCase instead of CactusStrutsTestCase. I've changed my mind about renaming the "beansConfig" property to "context" because most plugins have "Config" in them, so we might as well stick with a Struts convention since it is a Struts plugin.
I do think we should try to enhance this plugin so it will recognize if Spring's context has already been loaded (via a Listener or Servlet).
I'd also like to see the ability to use the plugin as an alternative to Spring's default loaders (Listener or Servlet). In other words, if you specify the plugin, you don't need to add anything for Spring to your web.xml file.
I'll work on both of these.
Another thing that would be great is to figure out a way to make this a bit more XDoclet friendly. I generate all my action-mappings using XDoclet, so I cannot use XDoclet on my actions if I use this plugin. I know, it's trivial - but it would be nice if it wasn't necessary to define a mapping/bean twice (once in struts-config.xml and once in applicationContext.xml). I'm open to suggestions here. I don't know if it would be possible to do with a SpringAware interface on an Action, but that sounds like a clean mechanism.
Lastly, I talked to both Ted (Struts) and Rod (Spring) this weekend about adding this plugin to one of their respective projects. They were both open to adding it - so I'm willing to do whatever it takes to make it a robust 1.0 implementation - and get it moved to a proper parent project. Of course, I'm willing to leave it here if that seems like a good idea too.
Matt
> To all those who use the Spring Plugin for Struts:
>
> I'm using (and writing about) the Spring plugin for Struts. What do you
> think about changing the default beansConfig location to be
> "/WEB-INF/applicationContext.xml" - since this is the standard naming
> convention for Spring? Maybe even changing the name from "beansConfig"
> to be "context" or "contextFile"?
>
> This would allow (in most cases) for developers to simply have the
> following in their struts-config.xml file:
>
> <plug-in className="org.twdata.struts.SpringPlugIn"/>
>
> Instead of:
>
> <plug-in className="org.twdata.struts.SpringPlugIn">
> <set-property property="beansConfig"
> value="/WEB-INF/applicationContext.xml"/>
> </plug-in>
>
> Thanks,
>
> Matt
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Struts-apps mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/struts-apps
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Struts-apps mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/struts-apps
