A comment I just made on the new thread about "Extending the scope of the struts
validation", really belongs here on this thread... My problem with tying forms
to JavaBeans is that JavaBeans don't seem to be flexible enough to use for
dynamic forms. If I need to create a form or modify it at runtime, how do I do
it using a JavaBean? How do I add properties to a JavaBean dynamically? If
dynamic forms are going to require more than just a JavaBean, then the
validation framework can't be tied to just JavaBeans.
Will
----- Original Message -----
From: "Levi Cook" <[EMAIL PROTECTED]>
To: "struts-dev" <[EMAIL PROTECTED]>
Sent: Friday, June 22, 2001 3:26 AM
Subject: Struts 1.1 TODO List -- Event and Listener Model
> I realize that the list of 1.1 Event Generators is semi-volatile until
> work-flow and validation fall into place. On the flip side, I think there
> might be a few "interesting" events we can identify now. For instance, what
> do people think of the attached samples and models? What other events are
> people anticipating or hoping for?
>
> (forgive the mixed bag Javadoc/UML notation; ascii is rough :)
>
> java.util.EventObject
> |
> +-- org.apache.struts.action.ActionForm
> + addActionFormListener(ActionFormListener) : void
> + removeActionFormListener(ActionFormListener) : void
> - fireActionFormWasReset() : void
> - fireActionFormValidated() : void
>
> java.util.EventObject
> |
> +-- org.apache.struts.action.event.ActionFormEvent
> + ActionFormEvent(ActionForm source) <<constructor>>
>
> java.util.EventListener;
> |
> +-- org.apache.struts.action.event.ActionFormListener <<interface>>
> + actionFormWasReset(ActionFormEvent) : void
> + actionFormValidated(ActionFormEvent) : void
>
>
> org.apache.struts.action.eventActionFormListener
> |
> +-- org.apache.struts.action.event.ActionFormAdaptor {
> + actionFormWasReset(ActionFormEvent) : void
> + actionFormValidated(ActionFormEvent) : void
>
>
> -- Levi
>
