Jason, and it seems Patrick, are not in favor of XDoclet much. XDoclet exists because folks choose to duplicate themselves all over the place, which is evil. With validations (and I'm not up to speed on the aliasing that is possible yet), we'll easily be able to generate those and I'll gladly create the module to do it after I do this stuff by hand a little and get familiar with all the pieces. With Struts, you end up with a form bean as a placeholder. With WW2, if you are presenting your model directly to the presentation from the actions it doesn't really make sense to tag validations on them but rather create a separate mapping by hand. But (and I still withhold judgment a bit on this), I like being able to display what the user typed in error for non-String fields. I'm vaguely thinking that some type of specialized interceptor could deal with this scenario though and keep all request fields in a Map and if validation fails, feed it back to the presentation when redisplaying the page. While typing that last sentence I realize its probably not easily possible though, except I think that OGNL has an interceptor hook too (thoughts on this anyone?).
As for Cactus... screw Cactus! :) Its too slow and the beauty of WW2 is that actions aren't tied to container objects like HttpServletRequest. Mocking is the way to go. IoC rules. Actually Cactus still has its place. In our current app we use stateless session beans that have role-based security attached to them - testing these with Cactus will still be done. We had sparse coverage of our Struts code mainly because it was a pain to run tests for it (and our Struts actions were very thin "proxies"). Using WW2 will make it possible to boost our coverage up another tier. So Cactus makes sense to test the thin layer of container managed things and should be used to ensure that those interactions are working, although mock is always recommended until you actually need to verify the actual container.
WW supporting indexed properties... ha! It uses OGNL and an object stack, not the weaker BeanUtils syntax. On this note though, please upgrade WW2 to the latest/newest OGNL release (I noticed Drew posted a note about it to the Tapestry list - it pays to keep tabs on all the frameworks! ;) I may be speaking too soon here as I've not given it a try, but I'd be way surprised if WW2 cannot do what Struts can do in this respect, and do it even better.
As for me defecting... still remains to be seen if I defect my larger day job projects where Struts has momentum. I'm pragmatic and wouldn't switch gears without buy-in from all the other developers. But Struts has serious design flaws (and no, I didn't just discover it, I've known it all along). Tapestry is definitely on the radar, but even Howard Lewis-Ship admits that Tapestry code is hard to test. WW2 has a nice middle-ground in terms of web flexibilty and "components" (no question that Tapesty's web componentization is slick) and IoC/command/interceptor framework. I'm definitely going to give WW2 a good thorough try.
Erik
On Tuesday, July 1, 2003, at 05:09 PM, Raible, Matt wrote:
If you can give me XDoclet generation of the validations (server-side +
client side) like Struts has, and provide Cactus integration like
StrutsTestCase, I might be interested. Of course, then I'll have to learn
SiteMesh over Tiles (or use Tiles with WW) and hope that WW supports indexed
properties (I'm sure it does).
Erik has defected... damn... ;-)
Raible
-----Original Message----- From: Hani Suleiman [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 01, 2003 2:57 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] WebWork2, here I come!
On Tuesday, July 1, 2003, at 04:52 PM, Jason Carreira wrote:
We're just glad to have you... Next we'll convert Matt Raible, then we'll teach Craig McClanahan the error of his ways... LOL
All that'd be left to do after that is get him to drop the devil-spawn abomination sometimes knows as JSF, and there might hope yet for the web portion of j2ee.
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/ 01
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/ 01
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
