It sounds like you're on the right track on processPopulate(). There was a mention before of adding a populate() method in ActionForm, but AFAIK it's never been thoroughly discussed, so I wouldn't hold my breath. If you're not going to call the default processPopulate() method in your subclass, study the existing code to make sure you don't miss any functionality that it's providing.
Hubert On Apr 12, 2005 8:22 AM, David Evans <[EMAIL PROTECTED]> wrote: > Hello, > > I posted this question yesterday, and got no replies, figured i'd try > rephrasing/simplifying the question. > > I have an application which i want to migrate to struts. It needs to be > able to use a different populate method depending on the information in > the submitted request. I am interested in different approaches to this > sort of thing. What would seem easiest is if there was a populate method > for the ActionForm. Is there any plan to include this in future struts > versions? Are there other frameworks that work like struts but have a > populate method for their equivelence of an ActionForm? I can create my > own RequestProcessor implementation that overrides processPopulate, what > implications might this have? Can anyone point to any online discussions > of varying approaches to the need for greater flexablility in the > populate phase of the request proccessing? > > Thanks > > Dave > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
