Another thought on ModelDriven action. Consider this use case:
public class Model {
String field = null;
public String getField() { return this.field; }
public void setField(String field) { this.field = field; }
}public class ModelDrivenAction
extends ActionSupport
implements ModelDriven {String actionField = null;
public String getActionField() { return this.actionField; }
public void setActionField(String actionField) { this.actionField = actionField; }
Model model = new Model();
public Object getModel() { return this.model; }}
The actionField action property is never set, because the ParametersInterceptor just set the model properties if an action is a ModelDriven. Is this the supposed behaviour ?
I think that's much better to make the ParametersInterceptor work directly on the value stack, so it can set the model properties and, if a property isn't found, go down the stack looking for a suitable property in the action.
Any comments ?
Marco
------------------------------------------------------- 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
