DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=14669.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Does anyone have any opinion on this?
http://issues.apache.org/bugzilla/show_bug.cgi?id=37057
I would like to tackle this problem, but both solutions I can think of
have gotchas. Is it too late for a DTD change in 1.3?
Hubert
I like the second, I suppose, but it does open up a can of worms :/
Don
Hubert Rabago wrote:
Does anyone have any opinion on this?
http://issues.apache.org/bugzilla/show_bug.cgi?id=37057
I would like to tackle this problem, but both solutions I can think of
have gotchas. Is it too late for a
We'd pretty much have to go with (2), I think.
The reset flag seems all right, especially if you can distingish
between GET and POST, as Micheal was asking. This would jive well with
the new form feature that makes it easy to submit back (or post back)
to the same action.
I would not consider
Yeah, I like the second, too.
Which can of worms are you talking about, though? The DTD change? I
was thinking, since we don't have a release yet, it ain't locked yet.
Right?
Hubert
On 10/12/05, Don Brown [EMAIL PROTECTED] wrote:
I like the second, I suppose, but it does open up a can of
I'm still trying to understand why the distinction is important. :)
Someone help me!
Hubert
On 10/12/05, Ted Husted [EMAIL PROTECTED] wrote:
We'd pretty much have to go with (2), I think.
The reset flag seems all right, especially if you can distingish
between GET and POST, as Micheal was
No, by can of worms, I'm referring to the adding of configuration data to form
properties ala action mappings. I suppose such additions are inevitable, so it
isn't a big concern.
As for making DTD changes now, I have no problem with it.
Don
Hubert Rabago wrote:
Yeah, I like the second,
At 3:06 PM -0700 10/12/05, Don Brown wrote:
No, by can of worms, I'm referring to the adding of configuration
data to form properties ala action mappings. I suppose such
additions are inevitable, so it isn't a big concern.
FormPropertyConfig extends BaseConfig, which is the nexus of
Moved from: User List, [FORMDEF] Resetting booleans for session-scoped dynaforms
On 10/12/05, Hubert Rabago [EMAIL PROTECTED] wrote:
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.
On 10/12/05, Hubert Rabago [EMAIL PROTECTED] wrote:
I'm still trying to understand why the distinction is important. :)
Someone help me!
Right now, a lot of Java web applications flit from action to action.
We migth use one action to display the page the first time, and then
submit to another
-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 12, 2005 5:44 PM
To: Struts Developers List
Subject: Re: Reset for DynaActionForm
Right now, a lot of Java web applications flit from action to action.
We migth use one action to display the page
Apologies, I'm on my way out. I only wanted to respond to a couple of
items, below:
On 10/12/05, Michael Jouravlev [EMAIL PROTECTED] wrote:
No, what I'm saying is Struts doesn't distinguish between the two
(AFAIK). However, you seem to.
I do, but Struts don't. You have said before, that
On 10/12/05, Ted Husted [EMAIL PROTECTED] wrote:
On 10/12/05, Hubert Rabago [EMAIL PROTECTED] wrote:
I'm still trying to understand why the distinction is important. :)
Someone help me!
Right now, a lot of Java web applications flit from action to action.
We migth use one action to
On 10/12/05, Michael Jouravlev [EMAIL PROTECTED] wrote:[snip]
No. reset() is supposed to be overriden by an application developer,
it is empty by default. But I cannot override reset() on a dynabean,
can I? I suppose that I cannot, please correct me if I am wrong.
Sure you can.
* Write a
On 10/12/05, Michael Jouravlev [EMAIL PROTECTED] wrote:
On 10/12/05, Ted Husted [EMAIL PROTECTED] wrote:
On 10/12/05, Hubert Rabago [EMAIL PROTECTED] wrote:
In an environment like JSF or ASP.NET, the framework makes a clear
distinction between the initial GET and subsequent POSTs. During
/show_bug.cgi?id=14669
reset() in DynaActionForm act the same as ActionForm
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED
16 matches
Mail list logo
