[JBoss JIRA] (RF-12145) RF4.2: Oncomplete not evaluated after invokeApplication if command is not rendered anymore
by Michael Heinen (JIRA)
Michael Heinen created RF-12145:
-----------------------------------
Summary: RF4.2: Oncomplete not evaluated after invokeApplication if command is not rendered anymore
Key: RF-12145
URL: https://issues.jboss.org/browse/RF-12145
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.2.0.Final
Environment: MyFaces 2.1.6
Tomcat 6.0.35
Reporter: Michael Heinen
Priority: Critical
Sample use case:
The last page of a wizard contains a commandButton with an EL expression in the oncomplete attribute.
This button renders an outer component in order to close the wizard. The button itself is not rendered anymore after clicking it.
As a consequence the EL expression of the oncomplete attribute is not evaluated after the invocation of an actionListener.
This worked well with richfaces 3.3.3, therefore it's a critical regression.
I'll attach a sample webApp for richfaces 4.2 and for riochfaces 3.3.3
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] Created: (RF-9428) 'render' is not processed for non-rendered component
by Nick Belaevski (JIRA)
'render' is not processed for non-rendered component
----------------------------------------------------
Key: RF-9428
URL: https://jira.jboss.org/browse/RF-9428
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-a4j-core
Affects Versions: 4.0.0.Milestone3
Reporter: Nick Belaevski
Assignee: Nick Belaevski
Fix For: 4.0.0.Milestone4
Test case:
<h:form>
<h:commandLink action="#{testBean.toggle}" value="Toggle" rendered="#{testBean.rendered}">
<a4j:ajax render="timePanel" />
</h:commandLink>
</h:form>
<h:panelGroup id="timePanel">
#{testBean.time}
</h:panelGroup>
package org.richfaces.demo;
import javax.faces.bean.ManagedBean;
import javax.faces.bean.SessionScoped;
@ManagedBean
@SessionScoped
public class TestBean {
private boolean rendered = true;
public void toggle() {
rendered = !rendered;
}
public boolean isRendered() {
return rendered;
}
public String getTime() {
return System.currentTimeMillis() + "";
}
}
Time should be updated when link is clicked, but it isn't.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] Created: (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
by Frederick Kämpfer (JIRA)
Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
-------------------------------------------------------------------------------
Key: RF-11382
URL: https://issues.jboss.org/browse/RF-11382
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-tables
Affects Versions: 4.0.0.Final, 4.1.0.Milestone2
Environment: Fedora 15, Glassfish 3.1.1, CDI (Weld)
Reporter: Frederick Kämpfer
In Richfaces 4 both datatable and extendedDatatable evaluate the value attribute even when rendered is set to false, even though it is not necessary. This makes it hard to achieve performance by trimming parts of the view tree. The built-in h:dataTable behaves correctly in that case.
To reproduce simply try this snipplet:
{code:xml}
<h:form>
<rich:dataTable value="#{myBean.property}" rendered="false">
</rich:dataTable>
</h:form>
{code}
Side note: The reason I'm posting this is, that i want to embed a rich:dataTable in a ajax loaded rich:togglePanelItem which is loaded on demand. Probably fixing the "render" problem will also make the dataTable lazy-loadable when switching to the corresponding togglePanelItem.
I hope this is no duplicate, I only found RichFaces 3 issues mentioning this problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] Created: (RF-10442) extendedDataTable: add state saving functionality
by Ilya Shaikovsky (JIRA)
extendedDataTable: add state saving functionality
-------------------------------------------------
Key: RF-10442
URL: https://issues.jboss.org/browse/RF-10442
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-tables
Affects Versions: 4.0.0.Milestone5
Reporter: Ilya Shaikovsky
Assignee: Konstantin Mishin
Fix For: 4.Future
developer should be able to store column width'es, order and so on between requests.
TO discuss: use tableState as before or maybe create set of specific attributes for every required properties set.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] Created: (RF-10958) Unnecessary attributes in message component
by Jan Jamrich (JIRA)
Unnecessary attributes in message component
-------------------------------------------
Key: RF-10958
URL: https://issues.jboss.org/browse/RF-10958
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: cdk, component
Affects Versions: 4.1.0.Milestone1
Environment: RichFaces 4.1.0-SNAPSHOT r.22442
Metamer 4.1.0-SNAPSHOT r.22441
Mojarra 2.0.4-b09
Apache Tomcat 6.0.29
Java(TM) SE Runtime Environment 1.6.0_19-b04 @ Linux
Chrome 12.0.718.0 @ Linux i686
Reporter: Jan Jamrich
There are some unnecessary attributes in faces-config.xml for rich:message component, such as: rendererType, rendersChildren. childCount, children, family, facets.
These attributes doesn't occurs in rich:messages component as well.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 12 months