Ted, >> The source for the framework actions and objects I use are available in the Scaffold packages. There is a core Scaffold package that was just posted to the Commons sandbox and a Struts-specific companion in the contrib folder. If anyone is interested, see <http://husted.com/struts> for the links. <<
Thanks. Very interesting stuff. I'm trying to absorb a lot very quickly, so please bear with me... but it looks like what you're talking about hinges on a ProcessBean paradigm where you call mybean.execute(Object), which first calls BeanUtils.populate() to parse/pass Object to its own setters. After that, the rest of the execute method does whatever business logic it needs to. I have to admit, I have mixed feelings about this model. On the one hand, you basically lose strong typing to some degree, because you won't know of any clashes until the BeanUtils.populate() call. On the other hand, if typing conflicts never happen then you've saved yourself quite a lot of coding. I'll have to think on this some more, and maybe build a couple of quick Struts/Scaffold sites of my own. Still interested to hear any more thoughts you might have. Especially on the importance of compile-time checking (or whatever you want to call "finding as many structural errors as possible before runtime"). Thanks, -jmc -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
