I'm not sure I follow this 100%.
Are you saying that a single null propery being passed into the setter of
your model caused a whole new model object to be created?
So you have : firstName, lastName, and address1
address1 was read-only ( disabled or whatever you want to call it ).
your action is ( for example ) :
public class MyAction extends ActionSupport implements ModelDriven<User> {
private User user = new User();
public User getModel() { return user ; }
}
then because address1 was null, a new user was created?
I'm partly confused because disabled properties shouldn't even be
transmitted by the browser ( though some ajax libraries are faulty when
'serializing' a form for use via XMLHttpRequest ).
stanlick wrote:
>
> I had a strange experience last night! My web page parms were being set
> onto my action's model until a null property was encountered. It seems
> one
> of the web page fields was set to readonly and was not passed as a request
> parm. The null property resulted in a new model object being constructed
> and things went down hill from there. Has anyone experienced this one?
>
> --
> Scott
> [EMAIL PROTECTED]
>
>
--
View this message in context:
http://www.nabble.com/ParameterInterceptor-tf4487083.html#a12801035
Sent from the Struts - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
