Re[2]: Strange problem after upgrading from struts 1.1 to 1.3.8

Hello, P It is part of the HTML spec that disabled fields are not submitted in the P request. This is not a Struts thing but HTML. You should make sure the HTML P is being rendered the same, because that's probably what is causing your P problem. Hmm, I thought it might be like this. I'm just

Re[2]: Strange problem after upgrading from struts 1.1 to 1.3.8

Hi, I just found out that the postdata didn't contain the attributes as well when using struts 1.1. So nothing changed here. But when I get at the beginning of the UserDispatchAction.update(), the dynaform has all values filled in. So I'm wondering where struts fills in the data, and why it

Re: Re[2]: Strange problem after upgrading from struts 1.1 to 1.3.8

--- Arne Brutschy [EMAIL PROTECTED] wrote: But when I get at the beginning of the UserDispatchAction.update(), the dynaform has all values filled in. With what? Something in your application is pre-loading the dynaform with reasonable values, no? I don't really remember S1.1 at this point;

Re: Re[2]: Strange problem after upgrading from struts 1.1 to 1.3.8

--- Arne Brutschy [EMAIL PROTECTED] wrote: But when I get at the beginning of the UserDispatchAction.update(), the dynaform has all values filled in. With what? Something in your application is pre-loading the dynaform with reasonable values, no? I don't really remember S1.1 at this point;