-
1. Re: a4j:commandButton incorrectly generated when rerendering
ilya_shaikovsky Dec 20, 2008 5:53 AM (in response to bastian_knight)can't reproduce under 3.3.0
-
2. Re: a4j:commandButton incorrectly generated when rerendering
bastian_knight Dec 21, 2008 5:34 AM (in response to bastian_knight)I have tried the latest stable version and the latest 3.3.0 snapshot and I still encounter this issue. Maybe I should mention that the whole content of the table changes on selecting an option in the listbox.
I can provide the source code for my test case and WAR. I can upload it on my HTTP server on Monday. -
3. Re: a4j:commandButton incorrectly generated when rerendering
bastian_knight Dec 22, 2008 6:23 AM (in response to bastian_knight)I have uploaded a NetBeans project with my testcase. It is available at the following location:
http://www.eti.pg.gda.pl/katedry/kask/pracownicy/Michal.Piotrowski/RichTestCaseApplication.zip
Project includes compiled WAR in dist directory. In the test case I use latest stable version (3.2.2.SR1) but I have tested it with 3.3.0 snapshot and the effect was the same.
If you deploy the WAR on JBoss or Glassfish you can see that when you select "1st" in listbox and click a button in the first row of a table than in an application server log you see text "one". When you select in listbox "2nd" then after clicking button in the first row there will be "one" in the server log and after clicking button in the second row there will be "null" in the server log but there should be "two" and "three" printed in the log.
I have tested it on Linux with JDK 6.0_11 on Glassfish 2 and JBoss 4.2.3, Firefox 3 and Konqueror 4.1 -
4. Re: a4j:commandButton incorrectly generated when rerendering
ilya_shaikovsky Dec 22, 2008 9:19 AM (in response to bastian_knight)change the scope of your bean to session or at list add keepAlive for ajax requests in this case for this bean.
-
5. Re: a4j:commandButton incorrectly generated when rerendering
bastian_knight Dec 22, 2008 2:48 PM (in response to bastian_knight)"ilya_shaikovsky" wrote:
change the scope of your bean to session or at list add keepAlive for ajax requests in this case for this bean.
Thank You very much!