[JBoss JIRA] (RF-11814) a4j:commandLink in tabPanel disabled if switchtype = ajax
by Friedhelm Kuehn (Created) (JIRA)
a4j:commandLink in tabPanel disabled if switchtype = ajax
---------------------------------------------------------
Key: RF-11814
URL: https://issues.jboss.org/browse/RF-11814
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-a4j-core, component-panels-layout-themes
Affects Versions: 4.1.0.CR2
Environment: Win 7 64 Bit, Tomcat 7.0.23, Mojarra 2.1.3
Reporter: Friedhelm Kuehn
In the following constellation (=extract from real page) the a4j:commandlink action method
is correctly triggered on clicking when tabPanels switchType = "client" but not when switchType = "ajax"
<rich:tabPanel .... switchType="client">
<rich:tab id="Query_Tab" header="Query">
<ui:include src="/pages/_Query.xhtml"/>
</rich:tab>
.....
<rich:tab>
<f:facet name="header">
<a4j:commandLink action="#{XCmrSession.logout}">
<h:graphicImage value="/images/logout.jpg"/>
</a4j:commandLink>
</f:facet>
Logging out, please wait !
</rich:tab>
</rich:tabPanel>
--
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
13 years
[JBoss JIRA] (RF-11860) Data table: The scope attribute on the td element is obsolete
by Pavol Pitonak (Created) (JIRA)
Data table: The scope attribute on the td element is obsolete
-------------------------------------------------------------
Key: RF-11860
URL: https://issues.jboss.org/browse/RF-11860
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: compatibility, component-tables
Affects Versions: 4.1.0.Final
Environment: RichFaces 4.1.1-SNAPSHOT
Metamer 4.1.1-SNAPSHOT r.23118
Mojarra 2.1.5
JBoss AS 7.1.0.CR1
OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux
Chrome 16.0.912.63 @ Linux i686
Reporter: Pavol Pitonak
The column footer is rendered as in following code snippet (can be reproduced in Metamer http://localhost:8080/metamer/faces/components/richDataTable/facets.xhtml):
{code:xml}
<tfoot id="form:richDataTable:tf" class="rf-dt-tft">
<tr id="form:richDataTable:cf" class="rf-dt-sftr">
<td class="rf-dt-sftr-c" scope="col">
<span id="form:richDataTable:columnFooterState">State Footer</span>
</td>
<td class="rf-dt-sftr-c" scope="col">
<span id="form:richDataTable:columnFooterCapital">Capital Footer</span>
</td>
</tr>
<tr id="form:richDataTable:f" class="rf-dt-ftr">
<td class="rf-dt-ftr-c" colspan="2" scope="colgroup">
<span id="form:richDataTable:footer">Footer</span>
</td>
</tr>
</tfoot>
{code}
Attribute *scope* on element td is obsolete in HTML5 and should be set on th element instead.
--
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
13 years
[JBoss JIRA] (RF-11850) RF 4.1.0.Final: Problem using columnResize with more than one extendedDataTable on the same page.
by Christian Peter (Created) (JIRA)
RF 4.1.0.Final: Problem using columnResize with more than one extendedDataTable on the same page.
-------------------------------------------------------------------------------------------------
Key: RF-11850
URL: https://issues.jboss.org/browse/RF-11850
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-tables
Affects Versions: 4.1.0.Final
Environment: Windows 7 x64 or arch linux x86
JBoss 7.0.1 Final or Glassfish 3.1
Reporter: Christian Peter
Priority: Minor
Hello,
I've encountered some problems using richfaces extendedDataTables in RichFace 4.1.0.Final
Here is the facelet:
<h:form>
<rich:extendedDataTable value="#{tableDemoManager.demoList}" var="item" style="height:300px; width:500px;">
<rich:column>
<f:facet name="header">Header7</f:facet>
#{item.name}
</rich:column>
<rich:column>
<f:facet name="header">Header8</f:facet>
#{item.uuid}
</rich:column>
<rich:column>
<f:facet name="header">Header9</f:facet>
#{item.uuid}
</rich:column>
<rich:column>
<f:facet name="header">Header10</f:facet>
#{item.uuid}
</rich:column>
</rich:extendedDataTable>
</h:form>
<h:form>
<rich:extendedDataTable value="#{tableDemoManager.demoList}" var="item" style="height:300px; width:500px;">
<rich:column>
<f:facet name="header">Header7</f:facet>
#{item.name}
</rich:column>
<rich:column>
<f:facet name="header">Header8</f:facet>
#{item.uuid}
</rich:column>
<rich:column>
<f:facet name="header">Header9</f:facet>
#{item.uuid}
</rich:column>
<rich:column>
<f:facet name="header">Header10</f:facet>
#{item.uuid}
</rich:column>
</rich:extendedDataTable>
</h:form>
Resizing the columns on the first table works perfectly, but if someone tries to resize the second tables' columns as well, I've got NullPointer exceptions like:
java.lang.NullPointerException
at org.richfaces.renderkit.SortingFilteringRowsRenderer.updateAttribute(SortingFilteringRowsRenderer.java:135) [richfaces-components-ui-4.1.0.Final.jar:
at org.richfaces.renderkit.ExtendedDataTableRenderer.updateWidthOfColumns(ExtendedDataTableRenderer.java:825) [richfaces-components-ui-4.1.0.Final.jar:]
at org.richfaces.renderkit.ExtendedDataTableRenderer.doDecode(ExtendedDataTableRenderer.java:808) [richfaces-components-ui-4.1.0.Final.jar:]
at org.richfaces.renderkit.RendererBase.decode(RendererBase.java:80) [richfaces-components-ui-4.1.0.Final.jar:]
at javax.faces.component.UIComponentBase.decode(UIComponentBase.java:787) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1]
at org.richfaces.component.UIDataAdaptor.processDecodes(UIDataAdaptor.java:819) [richfaces-components-ui-4.1.0.Final.jar:]
at org.richfaces.context.PartialViewExecuteVisitCallback.visit(PartialViewExecuteVisitCallback.java:53) [richfaces-core-impl-4.1.0.Final.jar:]
at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:321) [richfaces-core-impl-4.1.0.Final.jar:]
at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1319) [richfaces-components-ui-4.1.0.Final.jar:]
at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1]
at javax.faces.component.UIForm.visitTree(UIForm.java:344) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1]
at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1]
at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1]
at org.richfaces.context.ExtendedPartialViewContextImpl.executeComponents(ExtendedPartialViewContextImpl.java:237) [richfaces-core-impl-4.1.0.Final.jar:
at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialExecutePhase(ExtendedPartialViewContextImpl.java:217) [richfaces-core-impl-4.1.0.F
at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:196) [richfaces-core-impl-4.1.0.Final.jar:]
at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:931) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1]
at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:78) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT]
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT]
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT]
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
--
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
13 years
[JBoss JIRA] (RF-11914) Would like to see a dynamic subtable option for extendedDataTable
by Robert Gary (JIRA)
Robert Gary created RF-11914:
--------------------------------
Summary: Would like to see a dynamic subtable option for extendedDataTable
Key: RF-11914
URL: https://issues.jboss.org/browse/RF-11914
Project: RichFaces
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: component-tables
Affects Versions: 4.1.0.Final
Reporter: Robert Gary
Priority: Minor
In RF 3.3.3 extendedDataTable offered the ability for the user to select any column and subgroup on it. This is no longer supported in RF 4.X. We do have the callapsibleSubTable tag but it requires each column to be pre-configured for subtable grouping. Could subtable grouping simply be an attribute on the column???
<rich:column id="name" subgroup="#{bean.subGroupOnName}">
We would also want to allow the user to customize the expand/collapse subtable icon once the subtable grouping is enabled.
-Robert
--
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
13 years