August 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13107) rich:message is renderer even though it is in non-active switchable panel, causing JSF to fail with mallformedXML error

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13107?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13107: --------------------------------- Note: Visitor which scans for ajaxRenderer components shouldn't descend to subtrees which are not renderered. > rich:message is renderer even though it is in non-active switchable panel, causing JSF to fail with mallformedXML error > ----------------------------------------------------------------------------------------------------------------------- > > Key: RF-13107 > URL: https://issues.jboss.org/browse/RF-13107 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.3.2 > Reporter: Jonáš Trantina > Assignee: Brian Leathem > Fix For: 4.3.4 > > Attachments: bug_reproducer.zip > > > We have a form with a tabPanel component with two tabs A and B. In A there is an input and its rich:message in B the same plus a button that submits and re-renders B. When B is opened (thus A is not rendered) and the form is submitted and validation fails, then no message is shown. > Note that: > 1) switchType must be set to server to ensure the A's rich:message is really not on the page. > 2) button in B must re-render only content of B > This is only a specific scenario, the issue might occur also in other situations (e.g. global messages tag outside of tabPanel is not rendered). > Please find the enclosed reproducer. > Snipper: > {code:xml} > <h:form> > <rich:tabPanel switchType="server"> > <rich:tab> > <h:inputText id="surname" value="#{richBean.surname}"> > <f:validateLength minimum="10"/> > </h:inputText> > <rich:message for="surname"/> > </rich:tab> > <rich:tab> > <h:panelGroup id="content"> > <h:inputText id="name" value="#{richBean.name}"> > <f:validateLength minimum="6"/> > </h:inputText> > <rich:message for="name"/> > </h:panelGroup> > <a4j:commandButton value="Submit" execute="content" render="content" /> > </rich:tab> > </rich:tabPanel> > </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, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-13125) a4j:log does swallow the message from jsf.js's sendError method

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13125?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13125: ---------------------------- Fix Version/s: 4.3.4 5.0.0.Alpha2 > a4j:log does swallow the message from jsf.js's sendError method > --------------------------------------------------------------- > > Key: RF-13125 > URL: https://issues.jboss.org/browse/RF-13125 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.3, 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Fix For: 4.3.4, 5.0.0.Alpha2 > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-13125) a4j:log does swallow the message from jsf.js's sendError method

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13125?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13125: ---------------------------- Affects Version/s: 5.0.0.Alpha1 4.3.3 > a4j:log does swallow the message from jsf.js's sendError method > --------------------------------------------------------------- > > Key: RF-13125 > URL: https://issues.jboss.org/browse/RF-13125 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.3, 5.0.0.Alpha1 > Reporter: Lukáš Fryč > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-13125) a4j:log does swallow the message from jsf.js's sendError method

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13125?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13125: --------------------------------- Verify that issue fixes resolution of issues like RF-13107 > a4j:log does swallow the message from jsf.js's sendError method > --------------------------------------------------------------- > > Key: RF-13125 > URL: https://issues.jboss.org/browse/RF-13125 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Lukáš Fryč > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-13125) a4j:log does swallow the message from jsf.js's sendError method

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13125?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13125: --------------------------------- https://github.com/richfaces/richfaces/commit/2402737962f63a74f4d1c375b74... > a4j:log does swallow the message from jsf.js's sendError method > --------------------------------------------------------------- > > Key: RF-13125 > URL: https://issues.jboss.org/browse/RF-13125 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Lukáš Fryč > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-13125) a4j:log does swallow the message from jsf.js's sendError method

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-13125: ------------------------------- Summary: a4j:log does swallow the message from jsf.js's sendError method Key: RF-13125 URL: https://issues.jboss.org/browse/RF-13125 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Lukáš Fryč -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-13116) Using filters with paging / default filter value in extendeddatatable

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13116?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13116: ------------------------------- Labels: datascroller extendedDataTable filter waiting_on_user (was: datascroller extendedDataTable filter) > Using filters with paging / default filter value in extendeddatatable > --------------------------------------------------------------------- > > Key: RF-13116 > URL: https://issues.jboss.org/browse/RF-13116 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: John Strandmyr > Priority: Critical > Labels: datascroller, extendedDataTable, filter, waiting_on_user > Fix For: 3.3.4.Final > > > I've got an extededdatatable from richfaces and if i add a default value to the filter, so that some rows are excluded on first rendering, and then change the filter to show the rows that were hidden, I don't get any calls to the actionlisteners on the rows that were hidden at first. > It works fine on those rows that was shown in the first page load, but not on those hidden. > The same issue appears when i use paging, and some rows are on page two. if i use the filter to show some rows from another page, the actionlistener isnt triggered. I can still click on those rows that was apparent on the first page, but not on the other pages. > If I don't have a default filter, or a pager, i can add and remove filtering and everything is fine. > {code} > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > <h:head> > <meta http-equiv="content-type" content="text/html; charset=utf-8"/> > <h:outputScript name="jsf.js" library="javax.faces"/> > </h:head> > <h:body> > <h:form> > <rich:extendedDataTable value="#{tiltakServer.tiltak}" var="tiltak" id="tiltakTable"> > <rich:column filter="#{tiltakFilter.tittelImpl}"> > <f:facet name="header"> > <h:outputText value="Tittel" /> > <h:panelGroup styleClass="filter"> > <h:inputText value="#{tiltakFilter.tittelFilter}"> > <a4j:ajax event="keyup" render="tiltakTable@body" execute="@this"/> > </h:inputText> > </h:panelGroup> > </f:facet> > <h:outputText value="#{tiltak.tittel}"/> > </rich:column> > <rich:column> > <f:facet name="header"> > Edit > </f:facet> > <h:commandLink value="Goto"> > <f:actionListener type="no.hmskontoret.hmskontoret.hendelsesregister.TiltakOnEditActionListener"/> > </h:commandLink> > </rich:column> > </rich:extendedDataTable> > </h:form> > </h:body> > </html> > {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, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-13116) Using filters with paging / default filter value in extendeddatatable

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13116?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13116: ------------------------------------ Thanks - but I meant if you re-rendered it explicitly, for instance via clicking some other button. This is just to help us get a better understanding of the problem, and is not meant as an actual workaround. > Using filters with paging / default filter value in extendeddatatable > --------------------------------------------------------------------- > > Key: RF-13116 > URL: https://issues.jboss.org/browse/RF-13116 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: John Strandmyr > Priority: Critical > Labels: datascroller, extendedDataTable, filter > Fix For: 3.3.4.Final > > > I've got an extededdatatable from richfaces and if i add a default value to the filter, so that some rows are excluded on first rendering, and then change the filter to show the rows that were hidden, I don't get any calls to the actionlisteners on the rows that were hidden at first. > It works fine on those rows that was shown in the first page load, but not on those hidden. > The same issue appears when i use paging, and some rows are on page two. if i use the filter to show some rows from another page, the actionlistener isnt triggered. I can still click on those rows that was apparent on the first page, but not on the other pages. > If I don't have a default filter, or a pager, i can add and remove filtering and everything is fine. > {code} > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > <h:head> > <meta http-equiv="content-type" content="text/html; charset=utf-8"/> > <h:outputScript name="jsf.js" library="javax.faces"/> > </h:head> > <h:body> > <h:form> > <rich:extendedDataTable value="#{tiltakServer.tiltak}" var="tiltak" id="tiltakTable"> > <rich:column filter="#{tiltakFilter.tittelImpl}"> > <f:facet name="header"> > <h:outputText value="Tittel" /> > <h:panelGroup styleClass="filter"> > <h:inputText value="#{tiltakFilter.tittelFilter}"> > <a4j:ajax event="keyup" render="tiltakTable@body" execute="@this"/> > </h:inputText> > </h:panelGroup> > </f:facet> > <h:outputText value="#{tiltak.tittel}"/> > </rich:column> > <rich:column> > <f:facet name="header"> > Edit > </f:facet> > <h:commandLink value="Goto"> > <f:actionListener type="no.hmskontoret.hmskontoret.hendelsesregister.TiltakOnEditActionListener"/> > </h:commandLink> > </rich:column> > </rich:extendedDataTable> > </h:form> > </h:body> > </html> > {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, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-12613) rich:select with enablemanualinput selects wrong items

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12613?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12613: ------------------------------------ Thanks for the update [~jigg4]. We'll see if we can take a closer look at this use case. > rich:select with enablemanualinput selects wrong items > ------------------------------------------------------ > > Key: RF-12613 > URL: https://issues.jboss.org/browse/RF-12613 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Final, 4.3.0.M2 > Reporter: geert olaerts > Fix For: 4.5.0.Alpha1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > When using rich:select with enablemanualinput = "true", the wrong item might be selected. If the list of possible items is (in this order): "test test" and "test" and the user selects "test" richfaces will select "test test" as input. The same happens if the user types "test". If the list is "test" and "test test" and the user selects or types "test" the correct item is selected. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-13117) ExtendedDataTable Sorting resets $(window).resize Events

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13117?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13117: ------------------------------------ The line of code in question: [extendedDataTable.js#L754|https://github.com/richfaces/richfaces/blob/ab6...] This was introduced with the resolution of RF-12639. > ExtendedDataTable Sorting resets $(window).resize Events > -------------------------------------------------------- > > Key: RF-13117 > URL: https://issues.jboss.org/browse/RF-13117 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.3 > Environment: Tomcat 7 > JBoss 7.1 > Reporter: Thomas Zuberbuehler > Priority: Critical > Labels: regression > Fix For: 4.3.4 > > > Sorting removes other resize events. > At some point following code is called: > {code} > // extendedDataTable.js > deActivateResizeListener: function() { > $(window).off(this.resizeEventName); > } > {code} > Notice that this.resizeEventName is undefined. > Before code is invoked (Chrome JavaScript console) > {code} > $._data(window,'events').resize > [Object, Object] > {code} > After invoking > {code} > $._data(window,'events').resize > TypeError: Cannot read property 'resize' of undefined > {code} > http://stackoverflow.com/questions/18045891/how-to-check-if-onresize-meth... -- 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, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues August 2013