John, Hmm... seems that the action or model should be pushed on the stack, and then properties could be set at that point. Open a bug about this and we'll look in to it (there may have been a good reason, but it's way too early for me to think about it).
-Pat ----- Original Message ----- From: "John Patterson" <[EMAIL PROTECTED]> To: "Webwork" <[EMAIL PROTECTED]> Sent: Friday, July 25, 2003 3:26 PM Subject: [OS-webwork] Properties not set on action When using a model driven action the property setting interceptor does not use the value stack to set the properties like I expected it to. Instead it replaces the OGNL root with EITHER the action or the model. This is not how the rest of the application works and seems rather strange. I want to set some properties on my model and have the rest fall through to the action. Why make an exception to the value stack behaviour in this instance? Does anyone else find this unusual? John. ------------------------------------------------------- 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
