|
From: Estes, J. D - S. L. M. <jam...@us...> - 2005-02-04 14:59:32
|
I hadn't heard of MockStrutsTestCase before. After some digging, I think it would work with the CactusStrutsTestCase, but may take a bit of subclassing to make it work with the MockStrutsTestCase. =20 For the MockStutsTestCase to work, I think there would need to be a subclass (SpringMockStrutsTestCase) that would create the parent WebApplicationContext in setup before the ContextLoaderPlugin is initialized (by super.setup()). This could be similar to the BaseSpringTestCases where there is an abstract getConfigLocations method that would be used to build the parent context...then throw it into the ServletContext where the ContextLoaderPlugin will pick it up. James -----Original Message----- From: spr...@li... [mailto:spr...@li...] On Behalf Of Matt Raible Sent: Friday, February 04, 2005 7:48 AM To: spr...@li... Subject: Re: [Springframework-developer] Documenting Web Framework Integration Options This looks like a *very* useful addition. It's similar to WebWork's=20 ActionAutowiringInterceptor and definitely makes configuration easier=20 (a good thing IMO). My only question is whether it works in=20 conjunction with MockStrutsTestCase so your actions will be auto-wired=20 when testing. +1 for adding it to Spring. Matt On Feb 4, 2005, at 6:40 AM, Estes, James D - St. Louis, MO wrote: > Matt, what are your thoughts on this (in the vein of Struts > integration): > http://opensource.atlassian.com/projects/spring/browse/SPR-667 > > > -----Original Message----- > From: spr...@li... > [mailto:spr...@li...] On=20 > Behalf > Of Matt Raible > Sent: Friday, February 04, 2005 7:35 AM > To: spr...@li... > Subject: Re: [Springframework-developer] Documenting Web Framework > Integration Options > > Thanks Alef. I probably won't do this for another week or so, but I > should have it done by the end of Feb. > > Matt > > On Feb 4, 2005, at 2:41 AM, Alef Arendsen wrote: > >> I've moved the Tapestry stuff over to a separate file >> (webintegration.xml) which has by the way changed the chapter number > of >> the later chapters. >> >> I've left the section ids (sect1 id=3D"XXX") the same for the = Tapestry >> section. They usually begin with the chapter identifier (in this case >> webintegration) but since they are used to generate URLs for the html >> documents (#view-tapestry e.g.) I've kept them the same. For new >> content >> in the webintegration.xml file, webintegration-xxx ids can be used... >> >> You can add the patches to the following issue, I'll keep an eye on > it. >> http://opensource.atlassian.com/projects/spring/browse/SPR-685 >> >> Regards, >> Alef >> >> >> >>> -----Original Message----- >>> From: spr...@li... >>> [mailto:spr...@li...] >>> On Behalf Of Juergen Hoeller >>> Sent: Thursday, February 03, 2005 10:16 PM >>> To: spr...@li... >>> Subject: Re: [Springframework-developer] Documenting Web >>> Framework Integration Options >>> >>> Matt, >>> >>> Thanks for volunteering :-) Indeed, there's a big gap in the >>> web framework integration docs. It's probably best to factor >>> the Tapestry section out into a separate chapter of the >>> reference docs and add stuff on the other web frameworks there. >>> >>> Regarding WebWork2, it would be good to mention it. Let's not >>> discuss the details in the Spring docs, though, as we'd have >>> to catch up with the Spring support in the XWork/WebWork >>> optional package then. An overview of the integration >>> approach plus a reference to the OpenSymphony website should >>> be sufficient. >>> >>> Juergen >>> >>> >>> -----Original Message----- >>> From: spr...@li... >>> [mailto:spr...@li...] >>> On Behalf Of Matt Raible >>> Sent: Thursday, February 03, 2005 9:29 PM >>> To: spr...@li... >>> Subject: [Springframework-developer] Documenting Web >>> Framework Integration Options >>> >>> >>> Hey guys, >>> >>> I've noticed that there's a lack of reference documentation >>> on how to integrate the various web frameworks with Spring. >>> There's information on Tapestry, but nothing on JSF, Struts >>> or WebWork. While I can understand the lack of WebWork >>> documentation (since Spring doesn't host the classes), I'd >>> like to help out and contribute what I've written for Struts >>> and JSF. I'd be happy to contribute WebWork as well, but >>> only if you think adding it to Spring's documentation is appropriate. >>> >>> If you're interested, please let me know what reference files >>> I should modify. Tapestry's documentation is under >>> "views.xml" - but it's not really a view. Maybe there should >>> be a new file created that explains generic web framework >>> integration (by getting the ApplicationContext from the >>> servlet context) and specific integration strategies for JSF, >>> Struts, Tapestry and WebWork? >>> >>> I was planning on modifying (or adding) the existing XML >>> files and then submitting patches to JIRA. Is that the best option? >>> >>> Thanks, >>> >>> Matt >>> >>> >>> >>> ------------------------------------------------------- >>> This SF.Net email is sponsored by: IntelliVIEW -- Interactive >>> Reporting Tool for open source databases. Create drag-&-drop >>> reports. Save time by over 75%! Publish reports on the web. >>> Export to DOC, XLS, RTF, etc. >>> Download a FREE copy at http://www.intelliview.com/go/osdn_nl >>> _______________________________________________ >>> Springframework-developer mailing list >>> Spr...@li... >>> > https://lists.sourceforge.net/lists/listinfo/springframework-developer >>> >>> >>> >>> ------------------------------------------------------- >>> This SF.Net email is sponsored by: IntelliVIEW -- Interactive >>> Reporting Tool for open source databases. Create drag-&-drop >>> reports. Save time by over 75%! Publish reports on the web. >>> Export to DOC, XLS, RTF, etc. >>> Download a FREE copy at http://www.intelliview.com/go/osdn_nl >>> _______________________________________________ >>> Springframework-developer mailing list >>> Spr...@li... >>> > https://lists.sourceforge.net/lists/listinfo/springframework-developer >>> >>> >>> >>> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by: IntelliVIEW -- Interactive > Reporting >> Tool for open source databases. Create drag-&-drop reports. Save time >> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. >> Download a FREE copy at http://www.intelliview.com/go/osdn_nl >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting > Tool for open source databases. Create drag-&-drop reports. Save time > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting > Tool for open source databases. Create drag-&-drop reports. Save time > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |