Hi,
I used to filter the request parameters of certain actions. It works
like this: the original bean is stored in the session. When the user
hits update, the filter replaces the paramters submitted by the user
with the original ones. Then, it replaces or deletes the values the
user has changed an
Hi,
D> With what?
Well, that was what I was asking myself. :) Problem is, the app hasn't
been touched since 4 years. So I kind of re-engineering here.
D> Something in your application is pre-loading the
D> dynaform with reasonable values, no? I don't really
D> remember S1.1 at this point; do you
--- 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 poi
--- 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 poi
Hi,
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
A
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 doesn'
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
It is part of the HTML spec that disabled fields are not submitted in the
request. This is not a Struts thing but HTML. You should make sure the HTML
is being rendered the same, because that's probably what is causing your
problem.
Paul
On 9/17/07, Arne Brutschy <[EMAIL PROTECTED]> wrote:
>
> Hi,
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> processorClass="org.apache.struts.action.RequestProcessor"
Hello,
I'm experiencing a strange problem after upgrading from struts 1.1 to
1.3.8. Perhaps the problem is known or expected, I haven't found a
solution yet.
Basic structure:
setupUser.dofills in the form for a user profile
user.jspdisplays the user profile form
e
10 matches
Mail list logo
