This is the fundamental way the value stack works - if it can't evaluate
an expression at the topmost level, it starts to work it's way down
until the expression can be evaluated.
I guess my question really is "why are you trying to set value on a null
object?" It sounds to be like you need to:
(1) do the initialization in the prepare method, so the model is not null
(2) change the order of the stack, so that the model interceptor happens
after the modelDriven interceptor
[EMAIL PROTECTED] wrote:
If your action class implements ModelDriven and Preparable and your prepare
method returns a null object, ParameterInterceptor tries to set the parms
which are names appropriate to properties in model object that is expected
to be on the top of stack. However, since model was null, it was NOT SET on
top of the stack and all the parameters are now looked for in the action
class. They are not found there (naturally) so all the parm setters fail.
Should the ModelDriven interceptor create a model when it is null?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
