Hi,
I have run some tests with this problem now with the latest nightly
build (20051106) and it still occurs.
Everything else works fine and I get no error messages or warnings. Is
anyone aware of anything else that can cause this or solve this?
Martin Marinschek wrote:
This problem should be fixed in current head - but not yet in a release.
regards,
Martin
On 11/7/05, Yee CN <[EMAIL PROTECTED]> wrote:
I am using 1.1.1 and I am experiencing this problem.
Recent posting on Load Testing indicates that saving state in client could
be awfully slow, so that may not be an option.
Regards,
Yee
-----Original Message-----
From: Bruno Aranda [mailto:[EMAIL PROTECTED]
Sent: Monday, 7 November 2005 6:34 PM
To: MyFaces Discussion
Subject: Re: Double submit problem
@Pawel: There has been many many changes from 1.0.9 to 1.1.1 but I
don't know now if your problem has been fixed, but I don't experience
it. Could you try a recent version?
@Tim: maybe a workaround is to save the state in the client, although
the performance is lower. Modify the parameter
javax.faces.STATE_SAVING_METHOD in the web.xml file.
Regards,
Bruno
2005/11/7, Tim Davies <[EMAIL PROTECTED]>:
I am having this exact same problem with regards to the back button.
In any page if the user clicks the back button then he will need to
click any submit buttons twice to get the desired result.
I have read around extensively on this issue and understand about the
phases and needing to refresh the view before the action can take place.
However it is still a big problem for use in web sites.
Under RI I find that the double click problem goes away but the result
of the click can often be erroneous. Under MyFaces I always get the
correct result from a click but always have to click twice.
I am using MyFaces 1.1.1.
Does anyone know a solution to this problem or a good workaround. Not
being allowed to use the back button is not a good selling point.
cheers,
Tim D
Kołoszko Paweł wrote:
I have problem with double submit:
1. I fill some inputext components
2. I press submit button
3. I wait a while and then I press submit button again.
4. My current page is then refreshed with all inputext components
cleared, regardless what is the action under the submit button.
I have read that I am not the first one with this problem. So my
questions are:
1. I am using version 1.0.9. Has something changed in next versions?
2. I tried s:token from shale. Problem didn't disappear. Maybe I was
doing something wrong but I checked that code responsible for throwing
validate exception in token component was never invoked in my
cases. How about s:token component in your applications? Does it work?
3. How do you manage with this problem?
PawelK
--
Tim Davies
Analyst Developer
KTS PLC: Service you can bank on
8th Floor, Finsbury Tower,
103-105 Bunhill Row,
London EC1Y 8TY
tel: +44 (0)20 7256 2300
fax: +44 (0)20 7256 2301
email: [EMAIL PROTECTED]
web: http://www.ktsplc.com
--
http://www.irian.at
Your JSF powerhouse -
JSF Trainings in English and German
--
Tim Davies
Analyst Developer
KTS PLC: Service you can bank on
8th Floor, Finsbury Tower,
103-105 Bunhill Row,
London EC1Y 8TY
tel: +44 (0)20 7256 2300
fax: +44 (0)20 7256 2301
email: [EMAIL PROTECTED]
web: http://www.ktsplc.com
