[JBoss JIRA] (RF-13687) TabPanel header is not updated after switching of tabs
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13687?page=com.atlassian.jira.plugin.s... ]
Juraj Húska commented on RF-13687:
----------------------------------
Note that the issue can be reproduced in {{5.0.0-SNAPSHOT}} as well as in {{5.0.0.Alpha3}}, and obviously in {{4.5.0-SNAPSHOT}}.
It is related to RF-13278, and imho it was introduced with EPVC refactoring - RF-13505.
> TabPanel header is not updated after switching of tabs
> ------------------------------------------------------
>
> Key: RF-13687
> URL: https://issues.jboss.org/browse/RF-13687
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha3, 5.0.0.Alpha4
> Reporter: Juraj Húska
>
> If {{TabPanel}} header is updated dynamically with AJAX, then switching among the tabs shows not the updated value of the header, but the initial one. Its updated after refresh of the page.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RF-13673) Backport the plain skin fix from RF 5
by Sebastian Cramer (JIRA)
[ https://issues.jboss.org/browse/RF-13673?page=com.atlassian.jira.plugin.s... ]
Sebastian Cramer commented on RF-13673:
---------------------------------------
Yikes... :-)
Now I got a problem: I am stuck with JDK6 for the time being (our build-target is Websphere 8 - and that only supports JDK6). JDK7 support is included with WAS8.5 but that is in a distant future for ops at our place. :(
I guess getting 4.5.x to build for JDK6 is a bigger task so I will try to come up with a solution for 4.3.x. I'll get back to you as soon as I figured something out.
> Backport the plain skin fix from RF 5
> -------------------------------------
>
> Key: RF-13673
> URL: https://issues.jboss.org/browse/RF-13673
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: skinning
> Reporter: Brian Leathem
> Assignee: Brian Leathem
> Fix For: 4.5.0.Alpha3
>
>
> Backport RF-11103.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RF-13687) TabPanel header is not updated after switching of tabs
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13687?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-13687:
-----------------------------
Description: If {{TabPanel}} header is updated dynamically with AJAX, then switching among the tabs shows not the updated value of the header, but the initial one. Its updated after refresh of the page. (was: If {{TabPanel}} header is updated dynamically with AJAX, then switching among the tabs shows not the updated value of the header, but the default one. Its updated after refresh of the page.)
> TabPanel header is not updated after switching of tabs
> ------------------------------------------------------
>
> Key: RF-13687
> URL: https://issues.jboss.org/browse/RF-13687
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha4
> Reporter: Juraj Húska
>
> If {{TabPanel}} header is updated dynamically with AJAX, then switching among the tabs shows not the updated value of the header, but the initial one. Its updated after refresh of the page.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RF-13687) TabPanel header is not updated after switching of tabs
by Juraj Húska (JIRA)
Juraj Húska created RF-13687:
--------------------------------
Summary: TabPanel header is not updated after switching of tabs
Key: RF-13687
URL: https://issues.jboss.org/browse/RF-13687
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-output
Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha4
Reporter: Juraj Húska
If {{TabPanel}} header is updated dynamically with AJAX, then switching among the tabs shows not the updated value of the header, but the default one. Its updated after refresh of the page.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RF-13685) ExtendedPartialViewContext.release causes IllegalStateException
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13685?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-13685.
--------------------------------
Resolution: Done
[~lafr] I've committed a fix to the 4.5.x branch, it resolves the problem as I was able to reproduce it in the showcase. If you could test it out that would be much appreciated.
> ExtendedPartialViewContext.release causes IllegalStateException
> ---------------------------------------------------------------
>
> Key: RF-13685
> URL: https://issues.jboss.org/browse/RF-13685
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha3
> Reporter: Frank Langelage
> Assignee: Brian Leathem
> Fix For: 4.5.0.Alpha3
>
>
> When using latest WildFly 9.0-SNAPSHOT including JSF 2.2.7 I get an exception immediately after login from my web-app which is using richfaces-5.0.0-SNAPSHOT.
> According to Farah Juma this is an error in RichFaces which comes up now because of a fix in JSF:
> "This is a bug in RichFaces that was introduced by this recent Mojarra fix:
> https://java.net/jira/browse/JAVASERVERFACES-3203
> The RichFaces ExtendedPartialViewContext class just needs to be updated accordingly."
> Stacktrace fragment:
> {code}
> Caused by: java.lang.IllegalStateException
> at com.sun.faces.context.FacesContextImpl.assertNotReleased(FacesContextImpl.java:705) [jsf-impl-2.2.7-jbossorg-1.jar:]
> at com.sun.faces.context.FacesContextImpl.getAttributes(FacesContextImpl.java:237) [jsf-impl-2.2.7-jbossorg-1.jar:]
> at org.richfaces.context.ExtendedPartialViewContext.setInstance(ExtendedPartialViewContext.java:55) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT]
> at org.richfaces.context.ExtendedPartialViewContext.release(ExtendedPartialViewContext.java:64) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT]
> at org.richfaces.context.ExtendedPartialViewContextImpl.release(ExtendedPartialViewContextImpl.java:473) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT]
> at com.sun.faces.context.FacesContextImpl.release(FacesContextImpl.java:591) [jsf-impl-2.2.7-jbossorg-1.jar:]
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:665) [jboss-jsf-api_2.2_spec-2.2.7.jar:2.2.7]
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RF-13678) Render @all does not work for nested a4j:region in collapsibleSubTable
by Michal Petrov (JIRA)
[ https://issues.jboss.org/browse/RF-13678?page=com.atlassian.jira.plugin.s... ]
Michal Petrov commented on RF-13678:
------------------------------------
It seems there is some premature removal of the "list" from ExternalContext's RequestMap, if I switch the subtables - i.e. make the output nested in the second one ({{list\[0\].sex == 'FEMALE'}}) - it works fine again.
> Render @all does not work for nested a4j:region in collapsibleSubTable
> ----------------------------------------------------------------------
>
> Key: RF-13678
> URL: https://issues.jboss.org/browse/RF-13678
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.5.0.Alpha3
> Reporter: Juraj Húska
> Assignee: Michal Petrov
> Labels: regression
> Fix For: 4.5.0.Alpha3
>
>
> Suppose nested {{regions}} in a {{collapsibleSubTable}}.
> Those regions are not updated when a {{commandButton}} with {{render}} attribute set to {{@all}} is submitted.
> IMHO it is somehow connected with RF-13677, however, this issue occurs only with combination of {{regions}} and {{collapsibleSubTable}}, other iteration components works in this matter.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months