Bug 913165
| Summary: | Repeat: input inside repeat in not updated | ||
|---|---|---|---|
| Product: | [Retired] JBoss Enterprise WFK Platform 2 | Reporter: | Pavol Pitonak <ppitonak> |
| Component: | RichFaces | Assignee: | Brian Leathem <bleathem> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Pavol Pitonak <ppitonak> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.2.0 | CC: | kpiwko, maschmid, mnovotny, myarboro, ppenicka, ppitonak |
| Target Milestone: | --- | ||
| Target Release: | 2.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
The HTML input element rendered by the h:inputText JSF component did not contain the "value" attribute. Consequently, when entering text into the input field, submitting it, and trying to clear the input text by clearing the bound value on the server side, the received partial update did not clear the input field in the browser. The issue originated in Mojarra 2.1.13, which is included in JBoss Enterprise Application Platform 6.0.1. No workaround for the issue is known, but it can be solved by upgrading to JBoss Enterprise Application Platform 6.1.0, which contains a different version of Mojarra that is not affected by the issue.
|
Story Points: | --- |
| Clone Of: | Environment: |
RichFaces 4.3.0.Final-redhat-1
Metamer 4.3.0.Final-redhat-1
Mojarra 2.1.13-redhat-1
EAP 6.0.1
Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
Chrome 24.0.1312.70 @ Linux x86_64
|
|
| Last Closed: | 2013-07-16 11:32:50 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Pavol Pitonak
2013-02-20 14:41:10 UTC
Pavol, please update this bz, I can see that linked RF-12512 was closed as OUT OF DATE Marek it was marked as out of date because it works with Mojarra 2.1.16 used for cummunity testing. However, EAP 6.0.1 contain Mojarra 2.1.13 with which it's broken. If you located as 2.1.13 is only problematic, when this is just a documentation issue or will RF team workaround it? Brian Leathem <bleathem> updated the status of jira RF-12512 to Reopened Brian Leathem <bleathem> made a comment on jira RF-12512 Re-opening to target EAP 6.0.1 Brian Leathem <bleathem> made a comment on jira RF-12512 I wrote a _fundamental_ test to reproduce this behaviour. I can confirm: # it worked in Mojarra 2.1.7 (shipped with AS 7.1.1.Final) # it starts failing in Mojarra 2.1.8 # starts working again in Mojarra 2.1.15 I'll next use the _fundamental_ test to investigate if there is something we can do to workaround this issue. Brian Leathem <bleathem> made a comment on jira RF-12512 This in fact has nothing to do with _<a4j:repeat>_ nor any RichFaces component for that matter. I was able to reproduce the behaviour with the following "plain old" JSF: {code} <h:form id='myForm'> "); <h:inputText id='input' value='#{ajaxBean.value}'/> "); <h:commandButton id='submit' value = 'Submit Input'> "); <f:ajax execute='input' render='input' /> "); </h:commandButton> "); <h:commandButton id='clear' value = 'Clear Input'> "); <f:ajax listener='#{ajaxBean.clearValue}' render='input' /> "); </h:commandButton> "); </h:form> {code} Brian Leathem <bleathem> made a comment on jira RF-12512 This in fact has nothing to do with _<a4j:repeat>_ nor any RichFaces component for that matter. I was able to reproduce the behaviour with the following "plain old" JSF: {code} <h:form id='myForm'> <h:inputText id='input' value='#{ajaxBean.value}'/> <h:commandButton id='submit' value = 'Submit Input'> <f:ajax execute='input' render='input' /> </h:commandButton> <h:commandButton id='clear' value = 'Clear Input'> <f:ajax listener='#{ajaxBean.clearValue}' render='input' /> </h:commandButton> </h:form> {code} Brian Leathem <bleathem> updated the status of jira RF-12512 to Resolved Brian Leathem <bleathem> made a comment on jira RF-12512 This turns out then to be entirely an upstream issue: JAVASERVERFACES-2578. Resolving would require a patch to the Mojarra 2.1.13 impl bundled with EAP. Doc text added. Pavol or Brian, please verify it is correct. Added an HTML clarifier before the input tag. Otherwise it looks good to me. Included in the release notes book: @ppitonak, does this issue occurs also on EAP 6.1? If so, please update the RN. Marek, it works correctly in EAP 6.1 which contains Mojarra 2.1.19. Edited doc text for wfk 2.3 release notes. |