You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by bu...@apache.org on 2001/11/14 03:49:11 UTC
DO NOT REPLY [Bug 4856] -
Make ActionForm an Interface
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4856>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4856
Make ActionForm an Interface
husted@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
------- Additional Comments From husted@apache.org 2001-11-13 18:49 -------
ActionForm was originally an interface, but after careful deliberation, it was
changed to an abstract class.
For more see,
http://www.mail-archive.com/struts-user@jakarta.apache.org/msg08070.html
and
http://www.husted.com/struts/FAQ/controller-ejb.htm
A *very* important aspect of the ActionForm is that it is a firewall between
HTTP and your business logic beans. The ActionForms objects give you the chance
to validate (and reject) data before handing it off to your business logic
beans. It also prevents other properties on your business logic beans from being
populated inadvertently. Every public property (including nested properties) on
an ActionForm bean can be populated from a HTTP request, which could include
properties you did not intend to expose.
-Ted.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>