On 10/14/05, Hubert Rabago <[EMAIL PROTECTED]> wrote: > On 10/14/05, Ted Husted <[EMAIL PROTECTED]> wrote: > > On 10/13/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote: > > > Instead, Action and ActionForm should be combined into one object, which > > > can be: > > > * stateful, if needed > > > * can be accessed from JSP > > > * can be automatically populated > > > * contaned lifecycle methods (via interface, like in Shale) > > > * can respond to input events (like DispatchAction) > > > > The question is getting there from here -- without leaving anyone > > behind. One reason we're changing the request processor is give people > > more flexibility in deciding how things work. As it stands, these sort > > of changes are slated for the Struts 1.5.x series. > > > > * http://struts.apache.org/milestones.html > > > > A simple way to accomplish some of this is to put an execute method on > > an ActionForm and then have the Action delegate to the ActionForm. > > > > -Ted. > > Or the other way around. Request or session-scoped actions that have > instance variables that get populated from the incoming action. I've > done the request/session-scoped action before, and with BeanUtils or > FormDef, populating the instance fields is easy. Combine this with > DispatchAction or ActionDispatcher and you've gone back to The Object > which combine data and methods. > > Hubert
I am all in either for one or another. I am thinking of doing it myself. Hubert, maybe you could share some code of yours ;-) if you already went down this path. But I don't want things *replacing* things. The point of maintaining Struts Classic is to keep compatibility, while enhancing it. I hope, that this new context object or whatever you call it, will not deprecate what we have now, because a lot of people depend on it. Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
