Ahhh, now I follow what you were saying.
I think both event dispatching mechanisms exist becuase they provide support
for semantically separate issues. The first form is notification that
something "interesting" just happened. The second form is the prevention of
placing an object into an invalid or inconsistent state.
Actually, this really goes back to the JavaBean specification where bound &
constrained properties are defined. This ultimately leads me to question
whether its appropriate, and beneficial to treat ActionForms as JavaBeans
(aka. java's component architecture for building modular software
components)?
The benefits for treating forms as Beans would generally be described as:
1) are usable by programming tools
2) follow a standard naming convention
3) have a conscise public interface
4) helps keep the learning curve shallow
To bean or not to bean, that is the question :)
Any other ideas or opinions on this?
-- Levi
> -----Original Message-----
> From: Jonathan Asbell [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 22, 2001 7:06 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Struts 1.1 TODO List -- Event and Listener Model
>
>
> 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.
>
