-----Original Message-----
From: Volkmann, Mark [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 16, 2003 5:52 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [OS-webwork] Woohoo!Can you share with us the justification you used for using WebWork instead of Struts? Others may find it useful. Perhaps you've already done that and I accidently deleted the email. If so, could you resend it to me?
> -----Original Message-----
> From: Jason Carreira [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 16, 2003 3:13 PM
> To: [EMAIL PROTECTED]
> Subject: [OS-webwork] Woohoo!
>
>
> So we had our Webwork vs. Struts talk today, and I was able
> to convince
> people here that there was sufficiently enough better about WW to make
> us use it instead of Struts, even though Struts is the "standard", of
> sorts! Cool.
>
> Off to catch a plane home...
>
> --
> Jason Carreira
> Technical Architect, Notiva Corp.
> phone: 585.240.2793
> fax: 585.272.8118
> email: [EMAIL PROTECTED]
> ---
> Notiva - optimizing trade relationships (tm)
>
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by: Thawte.com
> Understand how to protect your customers personal information
> by implementing
> SSL on your Apache Web Server. Click here to get our FREE
> Thawte Apache
> Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en
> _______________________________________________
> Opensymphony-webwork mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
>
***********************************************************************************
WARNING: All e-mail sent to and from this address will be received or
otherwise recorded by the A.G. Edwards corporate e-mail system and is
subject to archival, monitoring or review by, and/or disclosure to,
someone other than the recipient.
************************************************************************************
Title: Message
Well,
it really came down to usability issues. We looked at things like having to have
separate FormBeans tied to the Actions 1-1 (because you have to cast to the
expected FormBean subclass). Also, we looked at some sample code for Struts
and Webwork (we looked at code for Chiki, a Wiki implemented with Struts, and
Jira. Thanks Mike for having clean code!). It was very apparent that you had to
do a lot of busy work to initialize things and do the setup that the framework
should have done for you in Struts, whereas in Webwork, it was pretty much all
business code. Command driven actions were also a big hit, as our lead architect
came from a Next background, and apparently they did code like that all the
time. In general, I think it was just a general feeling that Webwork was better
abstracted and architected than Struts.
Other
advantages, like the ValueStack and the expression language, were less easy to
express, since they hadn't begun to use them yet.
Some
of the concerns were (in no order):
-Less
userbase - I pointed out that with a smaller project we have a better chance of
making changes and making WW do what we need
-JSTL
and JSF support
-tool
support
- [OS-webwork] Woohoo! Jason Carreira
- Re: [OS-webwork] Woohoo! Robert Nicholson
- RE: [OS-webwork] Woohoo! Kirk Rasmussen
- RE: [OS-webwork] Woohoo! Volkmann, Mark
- Re: [OS-webwork] Woohoo! Jason Carreira
- Re: [OS-webwork] Woohoo! Robert Nicholson