December 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12676) Drag and drop doesnt work with PSS disabled

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12676?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12676: ------------------------------- Fix Version/s: 5-Tracking > Drag and drop doesnt work with PSS disabled > ------------------------------------------- > > Key: RF-12676 > URL: https://issues.jboss.org/browse/RF-12676 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-drag/drop > Affects Versions: 4.2.3.Final > Environment: tomcat6 > Reporter: Anton Zukovskij > Fix For: 5-Tracking > > Attachments: dragAndDrop.zip > > > When using drag and drop with partial state saving disabled (javax.faces.PARTIAL_STATE_SAVING=false) on drop event NPE is thrown from org.richfaces.event.MethodExpressionDropListener. This is caused by methodExpression being null. Its not null when class instance is first time constructed. Reproducible both in sample app and in Rich Faces showcase 4.2.3.Final -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12654) PartialViewRender skips check for whether column is rendered before checking if children can be rendered

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12654?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12654: ------------------------------- Fix Version/s: 5-Tracking > PartialViewRender skips check for whether column is rendered before checking if children can be rendered > -------------------------------------------------------------------------------------------------------- > > Key: RF-12654 > URL: https://issues.jboss.org/browse/RF-12654 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.M2 > Environment: JBoss 7.1.1.Final > Reporter: Ken H > Labels: lazy-loaded > Fix For: 5-Tracking > > > When using rendered on a component within a rich:column of a rich:dataTable, the EL on the component is executed even if the column is not rendered. > The expected behavior (per my loose understanding of the JSF spec) would suggest that the traversal should have short-circuited before checking the unrendered column's children. > This behavior exists at least as far back as 4.1.0.Final. > Given this minimal example: > {code} > <rich:dataTable value="#{bean.foos}" var="foo"> > <rich:column rendered="false"> > <h:outputText value="#{foo.bar}" rendered="#{foo.propertyDoesNotExist != null}" /> > </rich:column> > <rich:column> > <a4j:commandButton value="Test" action="#{bean.noop}" > execute="@this" render="@form" /> > </rich:column> > </rich:dataTable> > {code} > Clicking the Test button would result in a stack trace similar to the following: > {code} > /index.xhtml @33,96 rendered="#{foo.propertyDoesNotExist != null}": The class 'org.richfaces.tests.Foo' does not have the property 'propertyDoesNotExist'. > at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:111) [jsf-impl-2.1.7-jbossorg-2.jar:] > at javax.faces.component.ComponentStateHelper.eval(ComponentStateHelper.java:194) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:413) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponent.isVisitable(UIComponent.java:1669) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1602) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at org.richfaces.component.UIDataAdaptor$DataVisitorForVisitTree.process(UIDataAdaptor.java:199) [richfaces-components-ui-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at org.ajax4jsf.model.SequenceDataModel.walk(SequenceDataModel.java:65) [richfaces-core-api-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at org.richfaces.component.UIDataAdaptor.walk(UIDataAdaptor.java:796) [richfaces-components-ui-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at org.richfaces.component.UIDataAdaptor.visitDataChildren(UIDataAdaptor.java:1269) [richfaces-components-ui-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at org.richfaces.component.UIDataTableBase.visitDataChildren(UIDataTableBase.java:395) [richfaces-components-ui-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1347) [richfaces-components-ui-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIForm.visitTree(UIForm.java:371) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at org.richfaces.context.ExtendedPartialViewContextImpl.visitActivatorComponent(ExtendedPartialViewContextImpl.java:440) [richfaces-core-impl-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at org.richfaces.context.ExtendedPartialViewContextImpl.visitActivatorAtExecute(ExtendedPartialViewContextImpl.java:310) [richfaces-core-impl-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at org.richfaces.context.ExtendedPartialViewContextImpl.getExecuteIds(ExtendedPartialViewContextImpl.java:98) [richfaces-core-impl-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at org.richfaces.context.ExtendedPartialViewContextImpl.isExecuteAll(ExtendedPartialViewContextImpl.java:148) [richfaces-core-impl-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:929) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:78) [jsf-impl-2.1.7-jbossorg-2.jar:] > {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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12678) Rich:editor - unterminated string literal JS error when submitting editor value

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12678?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12678: ------------------------------- Fix Version/s: 4.3.0.CR1 > Rich:editor - unterminated string literal JS error when submitting editor value > -------------------------------------------------------------------------------- > > Key: RF-12678 > URL: https://issues.jboss.org/browse/RF-12678 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.0.M3 > Environment: RichFaces 4.3.0.20121214-M3 > Metamer 4.3.0.20121218-M3 > JBoss Application Server: Weld Integration 7.1.1.Final > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.7.0_05-b06 @ Linux > Firefox 17.0 @ Linux x86_64, Chrome > Reporter: Juraj Húska > Priority: Minor > Labels: regression > Fix For: 4.3.0.CR1 > > Attachments: editorJSerror1.png, editorJSerror2.png > > > When submitting value from {{rich:editor}} JS error are thrown. Please see the attachment. > I have not found any broken functionality though, just those JS errors. > Is it caused by update of CKEditor or JQuery libraries ? -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12654) PartialViewRender skips check for whether column is rendered before checking if children can be rendered

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12654?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12654: ------------------------------- Labels: lazy-loaded (was: waiting_on_user) > PartialViewRender skips check for whether column is rendered before checking if children can be rendered > -------------------------------------------------------------------------------------------------------- > > Key: RF-12654 > URL: https://issues.jboss.org/browse/RF-12654 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.M2 > Environment: JBoss 7.1.1.Final > Reporter: Ken H > Labels: lazy-loaded > > When using rendered on a component within a rich:column of a rich:dataTable, the EL on the component is executed even if the column is not rendered. > The expected behavior (per my loose understanding of the JSF spec) would suggest that the traversal should have short-circuited before checking the unrendered column's children. > This behavior exists at least as far back as 4.1.0.Final. > Given this minimal example: > {code} > <rich:dataTable value="#{bean.foos}" var="foo"> > <rich:column rendered="false"> > <h:outputText value="#{foo.bar}" rendered="#{foo.propertyDoesNotExist != null}" /> > </rich:column> > <rich:column> > <a4j:commandButton value="Test" action="#{bean.noop}" > execute="@this" render="@form" /> > </rich:column> > </rich:dataTable> > {code} > Clicking the Test button would result in a stack trace similar to the following: > {code} > /index.xhtml @33,96 rendered="#{foo.propertyDoesNotExist != null}": The class 'org.richfaces.tests.Foo' does not have the property 'propertyDoesNotExist'. > at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:111) [jsf-impl-2.1.7-jbossorg-2.jar:] > at javax.faces.component.ComponentStateHelper.eval(ComponentStateHelper.java:194) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:413) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponent.isVisitable(UIComponent.java:1669) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1602) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at org.richfaces.component.UIDataAdaptor$DataVisitorForVisitTree.process(UIDataAdaptor.java:199) [richfaces-components-ui-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at org.ajax4jsf.model.SequenceDataModel.walk(SequenceDataModel.java:65) [richfaces-core-api-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at org.richfaces.component.UIDataAdaptor.walk(UIDataAdaptor.java:796) [richfaces-components-ui-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at org.richfaces.component.UIDataAdaptor.visitDataChildren(UIDataAdaptor.java:1269) [richfaces-components-ui-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at org.richfaces.component.UIDataTableBase.visitDataChildren(UIDataTableBase.java:395) [richfaces-components-ui-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1347) [richfaces-components-ui-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIForm.visitTree(UIForm.java:371) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at org.richfaces.context.ExtendedPartialViewContextImpl.visitActivatorComponent(ExtendedPartialViewContextImpl.java:440) [richfaces-core-impl-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at org.richfaces.context.ExtendedPartialViewContextImpl.visitActivatorAtExecute(ExtendedPartialViewContextImpl.java:310) [richfaces-core-impl-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at org.richfaces.context.ExtendedPartialViewContextImpl.getExecuteIds(ExtendedPartialViewContextImpl.java:98) [richfaces-core-impl-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at org.richfaces.context.ExtendedPartialViewContextImpl.isExecuteAll(ExtendedPartialViewContextImpl.java:148) [richfaces-core-impl-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:929) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:78) [jsf-impl-2.1.7-jbossorg-2.jar:] > {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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12684) The last page shows rows from the page before if rich:collapsibleSubTable is included in rich:dataTable with rich:dataScroller.

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12684?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12684: ------------------------------- Fix Version/s: 4.3.0.CR1 Assignee: (was: Brian Leathem) > The last page shows rows from the page before if rich:collapsibleSubTable is included in rich:dataTable with rich:dataScroller. > ------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12684 > URL: https://issues.jboss.org/browse/RF-12684 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.3.Final > Reporter: Ilia Vassilev > Fix For: 4.3.0.CR1 > > Attachments: BackingBean.java, dataScroller_RF-12684.xhtml, page1.png, page3.png > > > The last page shows rows from the page before if rich:collapsibleSubTable is included in rich:dataTable with rich:dataScroller. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12669) Autocomplete: client side validation for custom validators doesn't work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12669?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-12669. -------------------------------- Resolution: Done Fixed the broken searchForComponentRootOrReturn method in richfaces.js > Autocomplete: client side validation for custom validators doesn't work > ----------------------------------------------------------------------- > > Key: RF-12669 > URL: https://issues.jboss.org/browse/RF-12669 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, regression > Affects Versions: 4.3.0.M3 > Environment: RichFaces 4.3.0.20121214-M3 > Metamer 4.3.0.20121214-M3 > Mojarra 2.1.7 > JBoss AS 7.1.2.Final-redhat-1 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 23.0.1271.97 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 4.3.0.CR1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/csv.xhtml > # click "set wrong values" button > result: > * 4 messages should be visible, one for each input > * fourth input has no message > * worked well with RF 4.3.0.M2 > * works fine with other inputs, e.g. inplaceInput -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12669) Autocomplete: client side validation for custom validators doesn't work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12669?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12669: ------------------------------------ This failure was caused by the commit: https://github.com/richfaces/components/commit/c31ff16157be2b250ec1809e22... specifically changing the blur event to originate with the input element id (_this.fieldId_) rather than the autocomplete id (_this.id_) in the file [_AutocompleteBase.js_|https://github.com/richfaces/components/blob/c31ff1...] > Autocomplete: client side validation for custom validators doesn't work > ----------------------------------------------------------------------- > > Key: RF-12669 > URL: https://issues.jboss.org/browse/RF-12669 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, regression > Affects Versions: 4.3.0.M3 > Environment: RichFaces 4.3.0.20121214-M3 > Metamer 4.3.0.20121214-M3 > Mojarra 2.1.7 > JBoss AS 7.1.2.Final-redhat-1 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 23.0.1271.97 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 4.3.0.CR1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/csv.xhtml > # click "set wrong values" button > result: > * 4 messages should be visible, one for each input > * fourth input has no message > * worked well with RF 4.3.0.M2 > * works fine with other inputs, e.g. inplaceInput -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12668) rich:focus - stops to work when containing form is re-rendered by another form

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12668?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved RF-12668. ----------------------------- Resolution: Done > rich:focus - stops to work when containing form is re-rendered by another form > ------------------------------------------------------------------------------ > > Key: RF-12668 > URL: https://issues.jboss.org/browse/RF-12668 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.3.0.M3 > Environment: JBoss AS 7, Tomcat 7 > Firefox 16, IE 10 > Reporter: Jan Papousek > Assignee: Lukáš Fryč > Fix For: 4.3.0.CR1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12668) rich:focus - stops to work when containing form is re-rendered by another form

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12668?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12668: ---------------------------- Summary: rich:focus - stops to work when containing form is re-rendered by another form (was: rich:focus - @preserve attribute doesn't work when no text is entered) > rich:focus - stops to work when containing form is re-rendered by another form > ------------------------------------------------------------------------------ > > Key: RF-12668 > URL: https://issues.jboss.org/browse/RF-12668 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.3.0.M3 > Environment: JBoss AS 7, Tomcat 7 > Firefox 16, IE 10 > Reporter: Jan Papousek > Assignee: Lukáš Fryč > Fix For: 4.3.0.CR1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12669) Autocomplete: client side validation for custom validators doesn't work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12669?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-12669: ---------------------------------- Assignee: Brian Leathem (was: Lukáš Fryč) > Autocomplete: client side validation for custom validators doesn't work > ----------------------------------------------------------------------- > > Key: RF-12669 > URL: https://issues.jboss.org/browse/RF-12669 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, regression > Affects Versions: 4.3.0.M3 > Environment: RichFaces 4.3.0.20121214-M3 > Metamer 4.3.0.20121214-M3 > Mojarra 2.1.7 > JBoss AS 7.1.2.Final-redhat-1 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 23.0.1271.97 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 4.3.0.CR1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/csv.xhtml > # click "set wrong values" button > result: > * 4 messages should be visible, one for each input > * fourth input has no message > * worked well with RF 4.3.0.M2 > * works fine with other inputs, e.g. inplaceInput -- 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, 11 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 December 2012