Details
Description
After a JSF navigation, the next request is not an Ajax one. This happens because the JavaScript which captures form submits is missing in the page.
The problem is org.icefaces.impl.FormSubmit: The "guard against duplicates within the same JSF lifecycle" doesn't work in case of navigation because it relies on a FacesContext attribute. After a navigation the attribute is still there but because the ViewRoot changed the scriptWriter is actually not contained as a children of the form anymore.
The problem is org.icefaces.impl.FormSubmit: The "guard against duplicates within the same JSF lifecycle" doesn't work in case of navigation because it relies on a FacesContext attribute. After a navigation the attribute is still there but because the ViewRoot changed the scriptWriter is actually not contained as a children of the form anymore.
Activity
Field | Original Value | New Value |
---|---|---|
Attachment | icefacesSupport.war [ 13623 ] |
Salesforce Case | [5007000000JLCcm] |
Fix Version/s | 2.1 [ 10241 ] | |
Assignee Priority | P2 | |
Affects Version/s | 2.0.2 [ 10273 ] | |
Assignee | Mircea Toma [ mircea.toma ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #25924 | Fri Oct 14 10:23:56 MDT 2011 | mircea.toma | |
Files Changed | ||||
![]() |
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Fix Version/s | 2.1-Beta2 [ 10294 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Attached a sample project including a patched FormSubmit which fixes the problem (See the "PATCHED" comment).
To reproduce the problem simply remove the patched class and click twice on the button. The second button click will issue a normal request, not an Ajax one and the <script> tag is missing in the DOM.