Hubert Rabago wrote:
On 10/12/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
Do you want to say, that Struts somehow gets to know that a form was
submitted? How exactly does it do that? Can you show it in the code?
There is nothing in request which says "this stuff comes from an HTML
form"
On 10/12/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
> Well, that means that I should patch RequestProcessor/RequestUtils
> myself. Thanks for clarification. Still, that enhancement in Bugzilla,
> it is important despite the fact that it is outside of FormDef's
> scope. All I am asking for is
On 10/12/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
> I am telling you that checkbox values should be cleared, you are
> telling me that reset() is get called. Don't you think these are
> different things? ;-)
I don't think there are any disagreements there. :) We're discussing
clearing th
> > So, returning back to what should be done: the checkbox values should
> > be cleared, before they are populated with request values.
>
> And this is what Struts does now, assuming you have the correct code
> in reset(). http://struts.apache.org/userGuide/struts-html.html#checkbox
I am telling
On 10/12/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
> I really want to use your stuff, but I need to differentiate between
> request types (more generally, between input and output phases, but in
> 95% of cases it boils down to request type).
It seems your concerns are outside the scope of F
On 10/12/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
> It is not *my* GET ;-) Ok, I will try to analyze what happens on
> request, please correct me if I am wrong.
>
> HTML form is submitted to an action (in 99% of cases via POST);
>
> 1) RequestProcessor.process() is called:
>
> 2) Action
On 10/12/05, Hubert Rabago <[EMAIL PROTECTED]> wrote:
> Still not quite getting you. Are you saying that reset will be called
> during your GET? Is this because you've configured your action with
> the same form?
It is not *my* GET ;-) Ok, I will try to analyze what happens on
request, please co
Still not quite getting you. Are you saying that reset will be called
during your GET? Is this because you've configured your action with
the same form?
On 10/12/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
>
> > If you're prepopulating your form, none of this matters, since either
> > (1)
On 10/12/05, Hubert Rabago <[EMAIL PROTECTED]> wrote:
> I'm not sure we're understanding each other about this request type.
>
> When a form is submitted, here's what happens:
>
> * Struts receives a request for an action
> * Struts sees that a form was configured for the mapping, so it calls
> ret
I'm not sure we're understanding each other about this request type.
When a form is submitted, here's what happens:
* Struts receives a request for an action
* Struts sees that a form was configured for the mapping, so it calls
retrieves the form (if it can find it) or creates a new one
[processA
That would be great, but please don't forget the request type. Usually
I need to do this for POST requests only, this separation by type is
really important to me. So instead of reset="true" I would rather
have:
where "reset" can be:
* "true" or "ALL" to reset for any request type;
* "POST" or
Wow, you've got good timing, because someone is calling for this very
feature in FormDef, patch provided:
https://formdef.dev.java.net/issues/show_bug.cgi?id=2
The quick answer to your question is "no". FormDef doesn't meddle
with how Struts populates the form. It's more of a utility class you
c
12 matches
Mail list logo
