Bug 877560
| Summary: | RichFaces Showcase portlet throws Exception when switching skins multiple times | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Portal Platform 6 | Reporter: | Ken Finnigan <kfinniga> |
| Component: | PortletBridge | Assignee: | hfnukal <hfnukal> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0.x | CC: | bdawidow, epp-bugs, pmensik |
| Target Milestone: | --- | ||
| Target Release: | 6.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
JSF Component events were being retained between an Action and a Render of the portlet on the UIViewRoot. Removing or adding JSF components in the page was occurring twice, which caused exceptions about components no longer being present or already added. The JSF Mojarra implementation is now updated to remove events that may be present when setting a UIViewRoot directly onto the FacesContext, as is the case with PortletBridge. Exceptions about components being removed or added too many times no longer occur, and the page now behaves as expected.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-11-07 14:23:57 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
Ken Finnigan
2012-11-16 21:27:56 UTC
So to make it clear there is nothing we can do with this issue at this point - until it gets fixed in EAP. This may need to be postponed after JPP 6 Stan Silvert <ssilvert> made a comment on jira AS7-5970 Are you guys satisfied that this is fixed now that JAVASERVERFACES-2609 is done? Upstream fix should be integrated now. Can we close this? Ken Finnigan <ken> made a comment on jira AS7-5970 I don't see a problem with that. Safe to close from my perspective Stan Silvert <ssilvert> updated the status of jira AS7-5970 to Resolved According to JIRA/BZ this is resolved in EAP 6.1 Alpha |