James, It sounds like you don't understand how WebWork works. With each new request a new Action is created, so you can't do what you're asking. You'd need to make calls out to the session in order to do this kind of stuff. In short: Actions are request scoped.
-Pat ----- Original Message ----- From: "James Pan" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, July 28, 2003 6:54 AM Subject: RE: [OS-webwork] On storing values in actions Hello, > Ahh.. If the OgnlUtil does that, it should be logged as a bug. This is > if the param is not in the params map at all, correct? That would > definitely be a bug. > > > > > I think he means that the action properties are being set to > > null by OgnlUtil.copy(map, object) > > > > I.e. I presume that he has action properties with defaults > > compiled in, then the params-interceptor sets all action > > properties, even those that aren't in the request, overriding > > the compiled defaults. > > > > > > > > I'm not sure what you mean... How are you sending the params > > > to the Action? > > > > > > Actions are created fresh each time, so values shouldn't > carry over. > > > > > > Jason > > > I think this is the problem for me... I'm not quite clear on how to store values on the value stack... which is maybe why I'm seeking alternatives that are rather strange to the trained eyes... 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?? Thank you, James ------------------------------------------------------- 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 ------------------------------------------------------- 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
