|
From: Lars H. <ho...@ar...> - 2004-04-07 13:22:13
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, Am 07.04.2004 um 04:48 schrieb Seth Ladd: > Matt Raible wrote: >> I'm in agreement with Don here. I'm just looking for the >> best/easiest solution to integrate the two. When I first looked at >> this plugin, I didn't like the fact that I had to declare my Action >> twice (once in struts-config.xml and once in applicationContext.xml). >> However, the fact that I could use MockStrutsTestCase, as well as >> set my Managers declaratively on my Actions made me really like it. >> I'd like a minimal-intrusion mechanism, but I'm willing to do >> whatever you feel is best. By minimal-intrusion, I mean I'd like to >> use an existing Action with very little or no changes - only some >> tweaking in an XML file. I don't know if that's possible. > > I integrated Struts + Spring by creating a SpringRequestController and > overriding the createAction method to return from the Spring context. > > This is working really well for us, because no changes to our Actions. > We use xdoclet to make the struts-config, so we didn't want to use > Don's code. > > I passed this idea by Don, but he said this way isn't compatible w/ > Tiles, and something else possibly. He definitely knows better than > I. :) Agreed! I faced the same problem with SAIF. My first implementation ended up with two RequestProcessors: one default and one derived from TilesRequestProcessor. Unfortunately there is now real clean solution due to the bad design of the API. In order to "wrap" any possible other RequestController I ended up with using CGLIB ... Yours, Lars -----BEGIN PGP SIGNATURE----- Version: PGP 8.0.3 iQA/AwUBQHQAzLcyzbDWnRDCEQIrVwCgr0kcdGdnLwiajVvxoLnqhoXdomAAn1LZ EHf/nNV86mQEb7THSSV038p5 =uwss -----END PGP SIGNATURE----- |