January 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12717) “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1.

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12717?page=com.atlassian.jira.plugin.s... ] Brian Leathem edited comment on RF-12717 at 1/29/13 11:38 PM: -------------------------------------------------------------- This issue is resolved in RichFaces 4.3.0.CR1 with an earlier commit. was (Author: bleathem): This issue is resolved in RichFaces 4.3.0.CR2 with an earlier commit. > “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1. > --------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12717 > URL: https://issues.jboss.org/browse/RF-12717 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.3.Final > Reporter: Ilia Vassilev > Assignee: Brian Leathem > Fix For: 4.3.0.CR2 > > Attachments: sample.rar > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > This is a problem with <richataTable>. The component id for each row is reused. If you change the markup to use an ordinary <h:dataTable> and <h:column> then it works correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12717) “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1.

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12717?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12717: ------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.CR2) > “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1. > --------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12717 > URL: https://issues.jboss.org/browse/RF-12717 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.3.Final > Reporter: Ilia Vassilev > Assignee: Brian Leathem > Fix For: 4.3.0.CR1 > > Attachments: sample.rar > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > This is a problem with <richataTable>. The component id for each row is reused. If you change the markup to use an ordinary <h:dataTable> and <h:column> then it works correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12717) “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1.

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12717?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12717: ------------------------------- Fix Version/s: 4.3.0.CR2 > “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1. > --------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12717 > URL: https://issues.jboss.org/browse/RF-12717 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.3.Final > Reporter: Ilia Vassilev > Assignee: Brian Leathem > Fix For: 4.3.0.CR2 > > Attachments: sample.rar > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > This is a problem with <richataTable>. The component id for each row is reused. If you change the markup to use an ordinary <h:dataTable> and <h:column> then it works correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12717) “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1.

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12717?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-12717. -------------------------------- Resolution: Done This issue is resolved in RichFaces 4.3.0.CR2 with an earlier commit. > “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1. > --------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12717 > URL: https://issues.jboss.org/browse/RF-12717 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.3.Final > Reporter: Ilia Vassilev > Assignee: Brian Leathem > Fix For: 4.3.0.CR2 > > Attachments: sample.rar > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > This is a problem with <richataTable>. The component id for each row is reused. If you change the markup to use an ordinary <h:dataTable> and <h:column> then it works correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12762) Duplicate id problem in ExtendedDatatable with dynamic columns

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12762?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12762: ------------------------------------ [~blamlam] can you confirm if this is a problem with Mojarra as well? > Duplicate id problem in ExtendedDatatable with dynamic columns > -------------------------------------------------------------- > > Key: RF-12762 > URL: https://issues.jboss.org/browse/RF-12762 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.CR1 > Environment: Windows 7 , weblogic10.4.3, Myfaces 2.1.10, IE 9, FireFox 14.0.1 > Reporter: blam lam > Priority: Critical > > When the ExtendedDataTable contains dynamic columns (i.e. using for:each), "java.lang.IllegalStateException: component with duplicate id" will occur after the second submit from a commandButton. > The problem does not appear in 4.2.3 Final but found in 4.3 CR1 > Sample source code: > {code} > <h:form id="frmMarkUpdate"> > <a4j:outputPanel id="resultPanel"> > <rich:extendedDataTable id="studentVoMarkInputTab" > value="#{updateMarkBean.studentVoMarkAmends}" > var="studVo" > selectionMode="none" > height="100%"> > > <rich:column width="200px" > > <f:facet name="header"> > Status > </f:facet> > <h:outputText value="#{studVo.student.markAmendStatus}" /> > </rich:column> > > <c:forEach items="#{updateMarkBean.taskVos}" var="tvo" varStatus="s"> > <rich:column width="100px"> > <f:facet name="header"> > <h:outputText value="#{tvo.task.taskName}" /> > </f:facet> > <h:inputText id="task#{s.index}_amk" > value="#{studVo.getTaskMarkMap().get(tvo.task.taskId).amendedMark}" > size="1" maxlength="3"/> > </rich:column> > </c:forEach> > </rich:extendedDataTable> > > <a4j:commandButton id="btnSave" value="Save" > action="#{updateMarkBean.doBeforeSave}" > styleClass="button blue"> > </a4j:commandButton> > > </a4j:outputPanel> > </h:form> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12765) Rich:tabPanel not possible to switch tabs

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12765?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12765: ------------------------------- Steps to Reproduce: Remove from example that comes with richfaces distribution first static tab for dynamic tabs and you'll be able to reproduce this behaviour. richfaces/tabPanel/samples/dynamic-sample.xhtml {code} <rich:tabPanel activeItem="#{dynamicPanelBean.activeTab}"> <ui:remove> <rich:tab header="Static"> This tab is static one. All of the following tabs are dynamically generated using a4j:repeat. </rich:tab> </ui:remove> <a4j:repeat value="#{skinBean.skins}" var="skinName"> <rich:tab header="#{skinName}" name="#{skinName}"> <f:facet name="header">#{skinName}</f:facet> All the controls below are just standard JSF components skinned with RichFaces: <hr /> <h:form> {code} was: Remove from example that comes with richfaces distribution first static tab for dynamic tabs and you'll be able to reproduce this behaviour. richfaces/tabPanel/samples/dynamic-sample.xhtml <rich:tabPanel activeItem="#{dynamicPanelBean.activeTab}"> <ui:remove> <rich:tab header="Static"> This tab is static one. All of the following tabs are dynamically generated using a4j:repeat. </rich:tab> </ui:remove> <a4j:repeat value="#{skinBean.skins}" var="skinName"> <rich:tab header="#{skinName}" name="#{skinName}"> <f:facet name="header">#{skinName}</f:facet> All the controls below are just standard JSF components skinned with RichFaces: <hr /> <h:form> > Rich:tabPanel not possible to switch tabs > ------------------------------------------ > > Key: RF-12765 > URL: https://issues.jboss.org/browse/RF-12765 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.0.M3, 4.3.0.CR2 > Environment: Linux, windows any browser Chrom, Mozilla > Reporter: Tali Han > > Rih:Tab panel functionality is broken. > If you have dynamically generated tabs, you'll be able to switch from first to last, and then to first, but you'll not be able to switch to any other tab again. > Remove from example that comes with richfaces distribution first static tab for dynamic tabs and you'll be able to reproduce this behaviour. > richfaces/tabPanel/samples/dynamic-sample.xhtml > <rich:tabPanel activeItem="#{dynamicPanelBean.activeTab}"> > <ui:remove> > <rich:tab header="Static"> > This tab is static one. > > All of the following tabs are dynamically generated using a4j:repeat. > </rich:tab> > </ui:remove> > <a4j:repeat value="#{skinBean.skins}" var="skinName"> > > <rich:tab header="#{skinName}" name="#{skinName}"> > <f:facet name="header">#{skinName}</f:facet> > All the controls below are just standard JSF components skinned with RichFaces: > <hr /> > <h:form> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12765) Rich:tabPanel not possible to switch tabs

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12765?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12765: ------------------------------- Description: Rih:Tab panel functionality is broken. If you have dynamically generated tabs, you'll be able to switch from first to last, and then to first, but you'll not be able to switch to any other tab again. Remove from example that comes with richfaces distribution first static tab for dynamic tabs and you'll be able to reproduce this behaviour. richfaces/tabPanel/samples/dynamic-sample.xhtml {code} <rich:tabPanel activeItem="#{dynamicPanelBean.activeTab}"> <ui:remove> <rich:tab header="Static"> This tab is static one. All of the following tabs are dynamically generated using a4j:repeat. </rich:tab> </ui:remove> <a4j:repeat value="#{skinBean.skins}" var="skinName"> <rich:tab header="#{skinName}" name="#{skinName}"> <f:facet name="header">#{skinName}</f:facet> All the controls below are just standard JSF components skinned with RichFaces: <hr /> <h:form> {code} was: Rih:Tab panel functionality is broken. If you have dynamically generated tabs, you'll be able to switch from first to last, and then to first, but you'll not be able to switch to any other tab again. Remove from example that comes with richfaces distribution first static tab for dynamic tabs and you'll be able to reproduce this behaviour. richfaces/tabPanel/samples/dynamic-sample.xhtml <rich:tabPanel activeItem="#{dynamicPanelBean.activeTab}"> <ui:remove> <rich:tab header="Static"> This tab is static one. All of the following tabs are dynamically generated using a4j:repeat. </rich:tab> </ui:remove> <a4j:repeat value="#{skinBean.skins}" var="skinName"> <rich:tab header="#{skinName}" name="#{skinName}"> <f:facet name="header">#{skinName}</f:facet> All the controls below are just standard JSF components skinned with RichFaces: <hr /> <h:form> > Rich:tabPanel not possible to switch tabs > ------------------------------------------ > > Key: RF-12765 > URL: https://issues.jboss.org/browse/RF-12765 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.0.M3, 4.3.0.CR2 > Environment: Linux, windows any browser Chrom, Mozilla > Reporter: Tali Han > > Rih:Tab panel functionality is broken. > If you have dynamically generated tabs, you'll be able to switch from first to last, and then to first, but you'll not be able to switch to any other tab again. > Remove from example that comes with richfaces distribution first static tab for dynamic tabs and you'll be able to reproduce this behaviour. > richfaces/tabPanel/samples/dynamic-sample.xhtml > {code} > <rich:tabPanel activeItem="#{dynamicPanelBean.activeTab}"> > <ui:remove> > <rich:tab header="Static"> > This tab is static one. > > All of the following tabs are dynamically generated using a4j:repeat. > </rich:tab> > </ui:remove> > <a4j:repeat value="#{skinBean.skins}" var="skinName"> > > <rich:tab header="#{skinName}" name="#{skinName}"> > <f:facet name="header">#{skinName}</f:facet> > All the controls below are just standard JSF components skinned with RichFaces: > <hr /> > <h:form> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12765) Rich:tabPanel not possible to switch tabs

by Tali Han (JIRA)

Tali Han created RF-12765: ----------------------------- Summary: Rich:tabPanel not possible to switch tabs Key: RF-12765 URL: https://issues.jboss.org/browse/RF-12765 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-output Affects Versions: 4.3.0.CR2, 4.3.0.M3 Environment: Linux, windows any browser Chrom, Mozilla Reporter: Tali Han Rih:Tab panel functionality is broken. If you have dynamically generated tabs, you'll be able to switch from first to last, and then to first, but you'll not be able to switch to any other tab again. Remove from example that comes with richfaces distribution first static tab for dynamic tabs and you'll be able to reproduce this behaviour. richfaces/tabPanel/samples/dynamic-sample.xhtml <rich:tabPanel activeItem="#{dynamicPanelBean.activeTab}"> <ui:remove> <rich:tab header="Static"> This tab is static one. All of the following tabs are dynamically generated using a4j:repeat. </rich:tab> </ui:remove> <a4j:repeat value="#{skinBean.skins}" var="skinName"> <rich:tab header="#{skinName}" name="#{skinName}"> <f:facet name="header">#{skinName}</f:facet> All the controls below are just standard JSF components skinned with RichFaces: <hr /> <h:form> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12717) “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1.

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12717?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12717: ------------------------------- Workaround Description: Set the _context-param_ _javax.faces.PARTIAL_STATE_SAVING_ to _true_. (was: Set the _context-param_ _javax.faces.PARTIAL_STATE_SAVING_ to _false_.) > “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1. > --------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12717 > URL: https://issues.jboss.org/browse/RF-12717 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.3.Final > Reporter: Ilia Vassilev > Assignee: Brian Leathem > Attachments: sample.rar > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > This is a problem with <richataTable>. The component id for each row is reused. If you change the markup to use an ordinary <h:dataTable> and <h:column> then it works correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12764) rich:select - javascript error when using myfaces with french locale

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12764?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12764: ------------------------------- Fix Version/s: 5-Tracking > rich:select - javascript error when using myfaces with french locale > -------------------------------------------------------------------- > > Key: RF-12764 > URL: https://issues.jboss.org/browse/RF-12764 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.CR2 > Reporter: Dupont Dupont > Fix For: 5-Tracking > > > Using RF 4.3.0.CR2, using rich:select with french locale on Myfaces produces the following javascript error : > {code} > Uncaught SyntaxError: Unexpected identifier. > {code} > It appears when javax.faces.component.UISelectOne.INVALID error message has a value containing a single quote. > To reproduce it, just add the following line in your jsf messages properties : > {code} > javax.faces.component.UISelectOne.INVALID = {0} : Erreur de validation : la valeur n''est pas valide. > {code} > And add a rich:select in your JSF page. > We end up with the javascript : > {code} > RichFaces.csv.addMessage({ 'UISELECTONE_INVALID': {detail:'{0} : Erreur de validation : la valeur n'est pas valide.',summary:'{0} : Erreur de validation : la valeur n'est pas valide.',severity:2} }); > {code} > This error impacts users of Websphere 8 (tested on 8.0.0.3) with french locale (myfaces provides a default message containing simple quotes). > Resolved locally by modifying AddCSVMessageScript#appendcript > But perhaps I've missed some side effects. > {code:java} > @Override > public void appendScript(Appendable target) throws IOException { > String summary = facesMessage.getSummary(); > String detail = facesMessage.getDetail(); > int severity = facesMessage.getSeverity().getOrdinal(); > StringBuilder builder = new StringBuilder(); > ScriptUtils.appendEncodedString(builder, summary); > summary = builder.toString(); > builder = new StringBuilder(); > ScriptUtils.appendEncodedString(builder, detail); > detail = builder.toString(); > > String script = MessageFormat.format(MESSAGE_OBJECT, messageId, summary, detail, severity); > target.append(script); > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues January 2013