struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Arne Brutschy <>
Subject Re[3]: Strange problem after upgrading from struts 1.1 to 1.3.8
Date Tue, 18 Sep 2007 08:40:20 GMT

I'm just thinking aloud, so perhaps someone can drop-in and shed some
light here... :)

Post data send by browser is identical on both versions (old: struts
1.1 and new: struts 1.3.8). It contains only the displayed parameters,
nothing else. So in the old version, when the request arrives at
ActionServlet.process(), _all_ parameters and values of the
DynaActionform are in the HttpServletRequest included. In the new
version, there's a CoyoteRequest object, which hold only the submitted
parameters. I wonder what happens before the process() method? I
through the servlet container calls this directly? What method sets
the other parameter/value pairs in the request?


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

A> Arne

A> Paul Benedict wrote:
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.

P>> Paul

P>> On 9/17/07, Arne Brutschy <> wrote:
>>> Hi,
>>> A> I'm not sure if the reason for this is some change in the tags (my
>>> A> tags are simply wrappers around the standard struts tags, ie.
>>> A> XylonTextTag extends TextTag) or the changes in the request wrapper
>>> A> system. I tried to set
>>> A> <controller
>>> A> processorClass="org.apache.struts.action.RequestProcessor" />
>>> A> in the struts config as well, but no change.
>>> After debugging hours through tomcat code, I'm sure the Request
>>> processor is not the problem. At least, as soon as the request hits
>>> the action servlet, the postdata contains only the described
>>> parameters and not the ones the user couldn't write to.
>>> So I guess it's been some change in the tags or something else.. I
>>> will continue tomorrow...
>>> Arne
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail:
>>> For additional commands, e-mail:

Arne Brutschy                    M ++49-170-7568918
Kantstr. 35                      @
04275 Leipzig                    

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message