Trying to gear up my code for eventual migration to using
something like struts, while still allowing the client's
developer to take small evolutionary steps that he'll be
able to grok. So the first thing I've done is set up a
generic form listener that is associated with a java bean
(much like struts). I don't want to re-invent the wheel,
but I don't want to throw too much at him at once.

I'm not sure this is the best thing to do, though. It's
too easy for him to take my implementation as holy. Which
is not what I want. I don't want too much of the existing
code to stay in its NIH mindset. But there is alot of code
to change to make it fit something like struts.