On 10/14/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote: > > > > 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.
Well, if you check out the msg I sent to the Struts + AJAX thread over at user@, you'll see where my time is going right now. However, I meant to write a demo app illustrating this very concept for some time now, and now that someone has expressed interest, I think I'll go ahead with it. > 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. > The data+behavior action I've used did replace the CreateAction part of the chain (and led me to http://svn.apache.org/viewcvs?rev=209987&view=rev), but that was about it. I specified the scope using the <set-property> that Joe introduced. The updated validator behavior I'm playing with uses a forked set of taglibs. I haven't modified much, so I may get away with overriding certain tags instead, but for my POC I just went ahead and copied everything right away. The itch needed scratching ASAP. Hubert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
