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.

Reply via email to