You can point the "input" to an action which will populate the request with
the attribute(s) you need, and then forwards to your form.
--- Hubert Rabago <[EMAIL PROTECTED]> wrote:
> This is because when the user submits the form, that already starts a
> different request, so the request attributes are no longer there.
> In your mapping for the action where the form gets submitted to, where does
> the input attribute point to?
>
> Hubert
>
> --- Leandro Melo <[EMAIL PROTECTED]> wrote:
>
> > As i replied many times for this topic, i'd like to
> > expose the situation again and in DETAILS.
> >
> > Suppose a user submits a request that is handled by
> > MyActionDoSomething. Then this action sets a request
> > attribute like this:
> >
> > request.setAttribute("MyObject", obj);
> >
> > and forwards the request to the page
> > myPageDoSomeOtherThing.jsp, wich has some inputs for
> > the user to fill in.
> > This page (myPageDoSomeOtherThing.jsp) uses the bean
> > "obj" that was set in MyActionDoSomething.java ok !?
> >
> > Now suppose the user submits wrong information in
> > myPageDoSomeOtherThing.jsp, what will cause the
> > validate method in the associated ActionForm to return
> > some ActionErrors. BUT when the ActionForm send this
> > page back for the user to re-input data, the bean
> > "obj" that was set at the very beginning in
> > MyActionDoSomething.java is NOT present anymore!
> >
> > I think now it's clear that i'm not talking about the
> > formBean attributes, right !?
> >
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
