That is what I was saying yesterday Levi, when I mentioned:
"One thing I may suggest is that maybe you dont need to be explicit with the
type of listeners, and just register listeners"
Since we dont know and really will never know what kind of listeners we will
need because it may be specific to an app, maybe the validators should just
take some kind of generic Listeners or Events interface, or both.
.
----- 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
>
