Re: Submit problem
The problem was in Tobago SecretPhaseListener. It blocked all jsf phases
after a restore phase. I just added
create-session-secretfalse/create-session-secret and
check-session-secretfalse/check-session-secret in tobago-config.xml then
the problem was gone. I hope it will be useful to someone.
-Исходное сообщение-
From: Leonardo Uribe
Sent: Tuesday, May 13, 2014 5:13 PM
To: MyFaces Discussion
Subject: Re: Submit problem
Hi
You should check if the html output is correct. Probably it could be a
conflict between Tobago and the default JSF renderers, after all
RenderKitWrapper was added in JSF 2.0. Even if you set
renderKitId=”HTML_BASIC”, probably Tobago renderkit is still on top.
regards,
Leonardo Uribe
2014-05-08 10:42 GMT+02:00 Anton Sysoev bogatyr-h...@yandex.ru:
Hi. I have a project based on Tobago 2.0 alpha 3 + Tomcat 7.0.34 +
MyFaces Core 2.1.14 and it works fine. Now I need one page based on core
jsf components only. I try to add a page like below in the project
f:view xmlns=http://www.w3.org/1999/xhtml;http://www.w3.org/1999/xhtml
xmlns:h=http://java.sun.com/jsf/html;http://java.sun.com/jsf/html
xmlns:f=http://java.sun.com/jsf/core;
renderKitId=”HTML_BASIC”
html
h[image: Дразнюсь]ody
h:form
h:inputText value=”#{mybean.number}”/
h:commandButton value=”submit” action=”#{mybean.store}”/
h:form
/h[image: Дразнюсь]ody
html
/f:view
Page is rendered but values are not submitted. Is this a bug or I’m doing
something wrong? Thanks.
Re: Submit problem
Hi
You should check if the html output is correct. Probably it could be a
conflict between Tobago and the default JSF renderers, after all
RenderKitWrapper was added in JSF 2.0. Even if you set
renderKitId=”HTML_BASIC”, probably Tobago renderkit is still on top.
regards,
Leonardo Uribe
2014-05-08 10:42 GMT+02:00 Anton Sysoev bogatyr-h...@yandex.ru:
Hi. I have a project based on Tobago 2.0 alpha 3 + Tomcat 7.0.34 +
MyFaces Core 2.1.14 and it works fine. Now I need one page based on core
jsf components only. I try to add a page like below in the project
f:view xmlns=http://www.w3.org/1999/xhtml;http://www.w3.org/1999/xhtml
xmlns:h=http://java.sun.com/jsf/html;http://java.sun.com/jsf/html
xmlns:f=http://java.sun.com/jsf/core;
renderKitId=”HTML_BASIC”
html
h[image: Дразнюсь]ody
h:form
h:inputText value=”#{mybean.number}”/
h:commandButton value=”submit” action=”#{mybean.store}”/
h:form
/h[image: Дразнюсь]ody
html
/f:view
Page is rendered but values are not submitted. Is this a bug or I’m doing
something wrong? Thanks.
Submit problem
Hi. I have a project based on Tobago 2.0 alpha 3 + Tomcat 7.0.34 + MyFaces Core
2.1.14 and it works fine. Now I need one page based on core jsf components
only. I try to add a page like below in the project
f:view xmlns=http://www.w3.org/1999/xhtml;
xmlns:h=http://java.sun.com/jsf/html;
xmlns:f=http://java.sun.com/jsf/core;
renderKitId=”HTML_BASIC”
html
hody
h:form
h:inputText value=”#{mybean.number}”/
h:commandButton value=”submit” action=”#{mybean.store}”/
h:form
/hody
html
/f:view
Page is rendered but values are not submitted. Is this a bug or I’m doing
something wrong? Thanks.
Re: [TRINIDAD] Re: Partial submit problem - Page got stuck in Myfaces 1.1.5 with trinidad 1.0.8
Do the following:
1. Put your form's content inside a tr:document
binding=#{mybean.document1}/.
2. In the action method of the submit button put
document1.setInitialFocusId(subform's clientid).
3. RequestContext.getCurrentInstance().addPartialTarget(subform's client id);
This should help. In step 2 we are setting the focus on the subform. This would
bring the focus on the starting point of the subform.
cheers.Dushyant.
--- On Thu, 26/6/08, Scott O'Bryan [EMAIL PROTECTED] wrote:
From: Scott O'Bryan [EMAIL PROTECTED]
Subject: [TRINIDAD] Re: Partial submit problem - Page got stuck in Myfaces
1.1.5 with trinidad 1.0.8
To: MyFaces Discussion users@myfaces.apache.org
Date: Thursday, 26 June, 2008, 3:24 AM
My suggestion is to put TRINIDAD in the subject. :) There are people
that filter on this and you'll find more help by including the proper
prefix.
Scott
Bhushan wrote:
Hi everybody, I'm getting a problem when i click the submit button
(partial submit) which is inside a subform. Problem is, I am having a
subform with some input Text boxes in that few are mandatory and 2
partial submit buttons. when I click the submit button with out
entering any of the mandatory fileds it is displaying error message
properly but the focus is going out and page got stuck to enter the
details. when i click outside the page and come back it is allowing to
enter. any solution / Suggestions? Thanks in advance, Bhushan
View this message in context: Partial submit problem - Page got stuck
in Myfaces 1.1.5 with trinidad 1.0.8
http://www.nabble.com/Partial-submit-problem---Page-got-stuck-in-Myfaces-1.1.5-with-trinidad-1.0.8-tp18110652p18110652.html
Sent from the MyFaces - Users mailing list archive
http://www.nabble.com/MyFaces---Users-f181.html at Nabble.com.
Bollywood, fun, friendship, sports and more. You name it, we have it on
http://in.promos.yahoo.com/groups/bestofyahoo/
Partial submit problem - Page got stuck in Myfaces 1.1.5 with trinidad 1.0.8
Hi everybody, I'm getting a problem when i click the submit button (partial submit) which is inside a subform. Problem is, I am having a subform with some input Text boxes in that few are mandatory and 2 partial submit buttons. when I click the submit button with out entering any of the mandatory fileds it is displaying error message properly but the focus is going out and page got stuck to enter the details. when i click outside the page and come back it is allowing to enter. any solution / Suggestions? Thanks in advance, Bhushan -- View this message in context: http://www.nabble.com/Partial-submit-problem---Page-got-stuck-in-Myfaces-1.1.5-with-trinidad-1.0.8-tp18110652p18110652.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
[TRINIDAD] Re: Partial submit problem - Page got stuck in Myfaces 1.1.5 with trinidad 1.0.8
My suggestion is to put TRINIDAD in the subject. :) There are people that filter on this and you'll find more help by including the proper prefix. Scott Bhushan wrote: Hi everybody, I'm getting a problem when i click the submit button (partial submit) which is inside a subform. Problem is, I am having a subform with some input Text boxes in that few are mandatory and 2 partial submit buttons. when I click the submit button with out entering any of the mandatory fileds it is displaying error message properly but the focus is going out and page got stuck to enter the details. when i click outside the page and come back it is allowing to enter. any solution / Suggestions? Thanks in advance, Bhushan View this message in context: Partial submit problem - Page got stuck in Myfaces 1.1.5 with trinidad 1.0.8 http://www.nabble.com/Partial-submit-problem---Page-got-stuck-in-Myfaces-1.1.5-with-trinidad-1.0.8-tp18110652p18110652.html Sent from the MyFaces - Users mailing list archive http://www.nabble.com/MyFaces---Users-f181.html at Nabble.com.
Re: Calendar Tomahawk Submit Problem
Nobody have this problem? Its son strange I click in any place of the jsp page and the set method of the calendar is call :( On Nov 16, 2007 10:07 AM, daniel ccss [EMAIL PROTECTED] wrote: Anybody??? On 11/15/07, daniel ccss [EMAIL PROTECTED] wrote: Hi all, I'm using the tomahawk calendar, all works fine :) but i have a problem, no matter where do I click on the JSP the set method is call. I only want that when I click on a day of the calendar, how can I fix that? Thanks all
Re: Calendar Tomahawk Submit Problem
You probably should use a valueChangeListener instead. Look at the documentation (or maybe at the example). The setter being called is correct. daniel ccss schrieb: Nobody have this problem? Its son strange I click in any place of the jsp page and the set method of the calendar is call :( On Nov 16, 2007 10:07 AM, daniel ccss [EMAIL PROTECTED] wrote: Anybody??? On 11/15/07, daniel ccss [EMAIL PROTECTED] wrote: Hi all, I'm using the tomahawk calendar, all works fine :) but i have a problem, no matter where do I click on the JSP the set method is call. I only want that when I click on a day of the calendar, how can I fix that? Thanks all
Re: Calendar Tomahawk Submit Problem
Anybody??? On 11/15/07, daniel ccss [EMAIL PROTECTED] wrote: Hi all, I'm using the tomahawk calendar, all works fine :) but i have a problem, no matter where do I click on the JSP the set method is call. I only want that when I click on a day of the calendar, how can I fix that? Thanks all
Calendar Tomahawk Submit Problem
Hi all, I'm using the tomahawk calendar, all works fine :) but i have a problem, no matter where do I click on the JSP the set method is call. I only want that when I click on a day of the calendar, how can I fix that? Thanks all
TabbedPane submit problem II
role-nameuser/role-name /auth-constraint user-data-constraint descriptionper adesso non ma prima o poi integral/description transport-guaranteeNONE/transport-guarantee /user-data-constraint /security-constraint login-config auth-methodFORM/auth-method realm-namePMS/realm-name form-login-config form-login-page/login.jsp/form-login-page form-error-page/loginError.jsp/form-error-page /form-login-config /login-config security-role descriptionUtente loggato/description role-nameuser/role-name /security-role resource-ref res-ref-namejdbc/pmsRead/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth res-sharing-scopeShareable/res-sharing-scope /resource-ref /web-app * faces-config.xml: ?xml version=1.0 encoding=UTF-8? !DOCTYPE faces-config PUBLIC -//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN http://java.sun.com/dtd/web-facesconfig_1_1.dtd; faces-config converter id=AziendaConv converter-for-classit.pride.pms.dtos.AziendaBean/converter-for-class converter-classit.pride.pms.customImpl.AziendaConverter/converter-class /converter converter id=ContattoConv converter-for-classit.pride.pms.dtos.ContattoBean/converter-for-class converter-classit.pride.pms.customImpl.ContattoConverter/converter-class /converter converter id=UserConv converter-for-classit.pride.pms.dtos.UserBean/converter-for-class converter-classit.pride.pms.customImpl.UserConverter/converter-class /converter managed-bean [...] /managed-bean [..] managed-bean [...] /managed-bean managed-bean [...] /managed-bean managed-bean managed-bean-nameproposteControl/managed-bean-name managed-bean-classit.pride.pms.controls.ProposteControlBean/managed-bean-class managed-bean-scopesession/managed-bean-scope /managed-bean navigation-rule [.] /navigation-rule referenced-bean referenced-bean-namecurProposta/referenced-bean-name referenced-bean-classit.pride.pms.dtos.PropostaBean/referenced-bean-class /referenced-bean /faces-config ** -- View this message in context: http://www.nabble.com/TabbedPane-submit-problem-II-tf2310178.html#a6422771 Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: TabbedPane submit problem II [some More news]
-nameMyFacesExtensionsFilter/filter-name url-pattern/faces/*/url-pattern /filter-mapping servlet servlet-nameFacesServlet/servlet-name servlet-classjavax.faces.webapp.FacesServlet/servlet-class load-on-startup1/load-on-startup /servlet servlet-mapping servlet-nameFacesServlet/servlet-name url-pattern*.jsf/url-pattern /servlet-mapping servlet-mapping servlet-nameFacesServlet/servlet-name url-pattern/faces/*/url-pattern /servlet-mapping welcome-file-list welcome-filehome.jsp/welcome-file welcome-filehome.html/welcome-file /welcome-file-list security-constraint display-namePMS security/display-name web-resource-collection web-resource-namePagine private/web-resource-name url-pattern/private/*/url-pattern /web-resource-collection auth-constraint descriptionUtente loggato ruolo fittizio = user/description role-nameuser/role-name /auth-constraint user-data-constraint descriptionper adesso non ma prima o poi integral/description transport-guaranteeNONE/transport-guarantee /user-data-constraint /security-constraint login-config auth-methodFORM/auth-method realm-namePMS/realm-name form-login-config form-login-page/login.jsp/form-login-page form-error-page/loginError.jsp/form-error-page /form-login-config /login-config security-role descriptionUtente loggato/description role-nameuser/role-name /security-role resource-ref res-ref-namejdbc/pmsRead/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth res-sharing-scopeShareable/res-sharing-scope /resource-ref /web-app * faces-config.xml: ?xml version=1.0 encoding=UTF-8? !DOCTYPE faces-config PUBLIC -//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN http://java.sun.com/dtd/web-facesconfig_1_1.dtd; faces-config converter id=AziendaConv converter-for-classit.pride.pms.dtos.AziendaBean/converter-for-class converter-classit.pride.pms.customImpl.AziendaConverter/converter-class /converter converter id=ContattoConv converter-for-classit.pride.pms.dtos.ContattoBean/converter-for-class converter-classit.pride.pms.customImpl.ContattoConverter/converter-class /converter converter id=UserConv converter-for-classit.pride.pms.dtos.UserBean/converter-for-class converter-classit.pride.pms.customImpl.UserConverter/converter-class /converter managed-bean [...] /managed-bean [..] managed-bean [...] /managed-bean managed-bean [...] /managed-bean managed-bean managed-bean-nameproposteControl/managed-bean-name managed-bean-classit.pride.pms.controls.ProposteControlBean/managed-bean-class managed-bean-scopesession/managed-bean-scope /managed-bean navigation-rule [.] /navigation-rule referenced-bean referenced-bean-namecurProposta/referenced-bean-name referenced-bean-classit.pride.pms.dtos.PropostaBean/referenced-bean-class /referenced-bean /faces-config ** -- View this message in context: http://www.nabble.com/TabbedPane-submit-problem-II-tf2310178.html#a6427943 Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: h:commandLink and h:form submit problem
Hello, Has anyone had similar problem? Submitting JSF form directly to JSF page and not going via portal front-end URL makes integration with portal very difficult. Any insight on this would be greatly appreciated. Thanks a lot, --MG Mikhail Grushinskiy wrote: Hello, My jsf page can only be accessed via URL which forwards to this JSF for security reasons. Before doing forward server put other required stuff into session context (as user permissions, mode for extra/intranet viewing). Depending via which page it got into jsf this information in the context will be different. The only way to get to jsf page is via this set of URLs which do internal forward. Now I've started using jsf form h:form and h:commandLink and hit a major roadblock. h:commandLink submits only to JSF which contains parent h:form and it does it by direct reffering to JSF. It simply ignores current URL path. EX: http://localhost/portal/JsfApp/form.jsf http://localhost/portal/JsfApp/form.jsf is only accessible via http://localhost/portal/externalModeCheck?app=JsfApppage=form.jsf http://localhost/portal/externalModeCheck?app=JsfApppage=form.jsf or http://localhost/portal/internalModeSecurityCheck?app=JsfApppage=form.jsf http://localhost/portal/internalModeSecurityCheck?app=JsfApppage=form.jsf and has a form and commandLink and commandLink submits it directly to http://localhost/portal/JsfApp/form.jsf http://localhost/portal/JsfApp/form.jsf which is not accessible It should go via http://localhost/portal/internalModeCheck?app=JsfApppage=form.jsfadditionalParams=blabla http://localhost/portal/internalModeCheck?app=JsfApppage=form.jsfadditionalParams=blabla or http://localhost/portal/externalModeCheck?app=JsfApppage=form.jsfadditionalParams=blabla http://localhost/portal/externalModeCheck?app=JsfApppage=form.jsfadditionalParams=blabla depending on how I got there in first place. One case where I need to use h:commandLink is tomahawk master/detail dataTable. What is the workaround for this case with myfaces? Thanks, --MG
h:commandLink and h:form submit problem
Hello,My jsf page can only be accessed via URL which forwards to this JSF for security reasons. Before doing forward server put other required stuff into session context (as userpermissions, mode for extra/intranet viewing). Depending via which page it got into jsf this information in the context will be different. The only way to get to jsf is via this set of URLs which do internal forward. Now I've started using jsf form h:form and h:commandLink and hit a major roadblock.h:commandLink submits only to JSF which contains parent h:form and it does it by direct reffering to JSF. It simply ignores current URL path. EX: http://localhost/portal/JsfApp/form.jsf is only accessible viahttp://localhost/portal/externalModeCheck?app=JsfApppage=form.jsf orhttp://localhost/portal/internalModeSecurityCheck?app=JsfApppage=form.jsf and has a form and commandLinkand commandLink submits it directly to http://localhost/portal/JsfApp/form.jsf which is not accessibleIt should go via http://localhost/portal/internalModeCheck?app=JsfApppage=form.jsfadditionalParams=blablaor http://localhost/portal/externalModeCheck?app=JsfApppage=form.jsfadditionalParams=blabla depending on how I got there in first place.What is the workaround for this case with myfaces?Thanks,--MG
h:commandLink and h:form submit problem
Hello, My jsf page can only be accessed via URL which forwards to this JSF for security reasons. Before doing forward server put other required stuff into session context (as user permissions, mode for extra/intranet viewing). Depending via which page it got into jsf this information in the context will be different. The only way to get to jsf page is via this set of URLs which do internal forward. Now I've started using jsf form h:form and h:commandLink and hit a major roadblock. h:commandLink submits only to JSF which contains parent h:form and it does it by direct reffering to JSF. It simply ignores current URL path. EX: http://localhost/portal/JsfApp/form.jsf http://localhost/portal/JsfApp/form.jsf is only accessible via http://localhost/portal/externalModeCheck?app=JsfApppage=form.jsf http://localhost/portal/externalModeCheck?app=JsfApppage=form.jsf or http://localhost/portal/internalModeSecurityCheck?app=JsfApppage=form.jsf http://localhost/portal/internalModeSecurityCheck?app=JsfApppage=form.jsf and has a form and commandLink and commandLink submits it directly to http://localhost/portal/JsfApp/form.jsf http://localhost/portal/JsfApp/form.jsf which is not accessible It should go via http://localhost/portal/internalModeCheck?app=JsfApppage=form.jsfadditionalParams=blabla http://localhost/portal/internalModeCheck?app=JsfApppage=form.jsfadditionalParams=blabla or http://localhost/portal/externalModeCheck?app=JsfApppage=form.jsfadditionalParams=blabla http://localhost/portal/externalModeCheck?app=JsfApppage=form.jsfadditionalParams=blabla depending on how I got there in first place. One case where I need to use h:commandLink is tomahawk master/detail dataTable. What is the workaround for this case with myfaces? Thanks, --MG
Form submit problem on IE only
Hi,I have this simple page:?xml version="1.0" encoding="ISO-8859-1" ?!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"html xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core" xmlns:t="http://myfaces.apache.org/tomahawk"body f:view h:form h:inputText value="#{results.term}" size="60"/#160;#160;
h:commandButton value="Search"action=""//h:form /f:view /body/htmlThe action is invoked on IE only if i press the submit button, if the focus is on the input field and i hit enter, it just refreshes the page but no action is invoked. I tested this with Firefox, and there everything works as expected.Any of you know what might be the problem?Thanks in advance,Catalin
What are the most popular cars? Find out at Yahoo! Autos
Double submit problem
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
Re: Double submit problem
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
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
Re: Double submit problem
Cheers Bruno, Yeah I did think about client side state saving but our app is used on pdas so probably dont want to go there. I think RI 1.2 is supposed to have resolved some of these issues so may just have to wait til then. Tim Bruno Aranda wrote: @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 -- 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
RE: Double submit problem
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
Re: Double submit problem
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
Re: Double submit problem
Excellent, MyFaces wins the race again! Is there any estimate on a release date. Could save me writing a very ugly workaround... T 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
Re: Double submit problem
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
