> I would prefer to add ParameterDispatchAction now and defer a decision > about > merging the three actions. > To me, that would be 'the simplest thing that could possibly work' :-)
The downside to doing that is if we decide to combine them we have to go through the deprecation phase, document the changes, and explain it to confused users. I'd prefer it if we took a look at all 3 classes now and decided on an implementation before committing anything new. David > Steve > > > > -----Original Message----- > > From: Craig R. McClanahan [mailto:[EMAIL PROTECTED] > > Sent: August 1, 2003 10:42 AM > > To: Struts Developers List; [EMAIL PROTECTED] > > Subject: RE: Addition of two new actions > > > > > > So, what you really want is LookupDispatchAction without requiring the > > developer to create the map-related methods? I think you already get > the > > abililty to combine CRUD related actions and things like that. If so, > > then implementing a default getKeyMethodMap() in LookupDispatchAction > > might accomplish the same goal, without requiring another action. > Such a > > default implementation could examine the current LookupDispatchAction > > subclass and create the mapping information automatically. > > > > Don't get me wrong ... I like the idea behind what you're proposing. > I > > just think we might already have it (with the potential to improve > ease of > > use by not forcing people to implement getKeyMethodMap() for a common > use > > case). > > > > > > Craig > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
