Martin Cooper wrote:
> Just curious - in what situations might I want to use a class other than
> ActionFormBean to represent <form-bean> entries?
>
There is not much need for this in a standard Struts application, but consider
what would happen if you wanted to attach some additional configuration
information to a form (such as what fields should be edited in what way), and
you wanted to configure that stuff in the "struts-config.xml" file. One way
would be to define your own ActionFormBean class, which Struts would use instead
of the standard one, and which would pick up additional properties that you set
with a <property> element nested inside the <form-bean> element.
Same basic philosophy would apply to overriding the default classes for
ActionForward and ActionMapping as well.
>
> --
> Martin Cooper
> Tumbleweed Communications
>
Craig
