On Mon, February 14, 2005 11:45 am, Joe Germuska said: > Didn't get many reactions on the ActionForm side -- any concerns > about changes to it?
Well, I'll ask what seems like the obvious question... should ActionForms be commands as well? I guess you get into the question of how far to take the chain exercise at some point, but still... I occurs to me that since some requests use ActionForms while others do not, if they are Commands in a user-defined Action-level chain, then you simply reconfigure the chain for a given request removing the ActionForm step when applicable. Plus, you could then have multiple ActionForms for a given Action per request (not sure why you'd want to, but it would be possible). Also, if making Actions POJOs is the way to go, I'd say the same should be true of ActionForms too. Question: does a Command actually have to implement the Command interface? More to the real point: when we say a class is a POJO, is it a POJO if it is forced to implement a given interface? It's a question of semantics on one level, but on another it's not... It would be great if Actions and ActionForms didn't have to extend OR implement anything, so in what case is it really considered a POJO? I'd personally say it's only really a POJO when I'm not forced to extend OR implement anything. > Joe -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com > -- > Joe Germuska > [EMAIL PROTECTED] > http://blog.germuska.com > "Narrow minds are weapons made for mass destruction" -The Ex > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
