> What I want to is actually very simple: to allow > some kind of link with parameters, like > > .../mylink?parm1=hello&parm2=world > > but to allow for omitting parameters as I see fit... > so after that call above, the data (parm1=hello and > parm2=world) should be stored somewhere, and then if > a second call like this > > .../mylink?parm1=goodbye > > comes along, then the data gets modified to > (parm1=goodbye and parm2=world), with the previous > parm2 value carried over... > > I don't think I touched on anything that was a bug, > because if parm2 was defaulted to "wonderland" in > the action itself, then that's what it'll become > after a second call to the action... > > and if you say that an action is created new each > time, then this is the expected behaviour... I was > just hoping for some easy way of retaining data... > > What do you think is a good way to solve my problem, > i.e. retain values from the request string so that > they don't have to be specified every time??
You could store map of parameters in session scope. Would it be an option? Or maybe bean in IoC container... regards, ===== ----[ Konstantin Pribluda ( ko5tik ) ]---------------- Zu Verstärkung meines Teams suche ich ab Sofort einen Softwareentwickler[In] für die Festanstellung. Arbeitsort: Mainz Skills: Programieren, Kentnisse in OpenSource-Bereich ----[ http://www.pribluda.de ]------------------------ __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
