December 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13252) a4j:ajax includes jsf.js script twice

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13252?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13252: ------------------------------- Sprint: RichFaces 4.3.5 Sprint 1 > a4j:ajax includes jsf.js script twice > ------------------------------------- > > Key: RF-13252 > URL: https://issues.jboss.org/browse/RF-13252 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.4 > Reporter: Jonáš Trantina > Fix For: 4.3.5 > > Attachments: reproducer.zip > > > When a4j:script is used in the page like so: > {noformat} > <h:commandLink value="Click me "> > <a4j:ajax event="click" render="@form"/> > </h:commandLink> > {noformat} > Then two script tags pointing to jsf.js are added to the page, once in the head by the inclusion of @ResourceDependency [1], and once again by Overriding the ClientBehaviorRenderer#getScript method [2,3]. > Note, that according to Brian, resolving this without introducing any functional regressions may require the resolution of RF-12270 [4]. > [1] https://github.com/richfaces/richfaces/blob/master/framework/src/main/jav... > [2] https://github.com/richfaces/richfaces/blob/master/framework/src/main/jav... > [3] https://github.com/jboss/mojarra/blob/2.1.21-jbossorg-1/jsf-api/src/main/... > [4] https://issues.jboss.org/browse/RF-12270 -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13306) Autocomplete: initialize value from DOM (was: ignored API call .setValue(''))

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13306?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13306: ------------------------------------ [~alixey] any luck with that pull request? We are ramping up our development efforts for a 4.3.5 release. It would be great to see this fix included if you can take the time to create the PR. > Autocomplete: initialize value from DOM (was: ignored API call .setValue('')) > ----------------------------------------------------------------------------- > > Key: RF-13306 > URL: https://issues.jboss.org/browse/RF-13306 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: alexey plotnikov > Fix For: 4.3.5 > > > All described here https://community.jboss.org/thread/233973 > I have this autocomplete component: > {code} > <table> > <tr> > <td> > <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteProviders}" > minChars="0" var="s" fetchValue="#{s.realName}" id="provider-suggestion" > autofill="false" > onselectitem="autocompleteChangeProvider(event.target)" style="display: inline;" > layout="table" value="#{autocomplete.providerName}" > > <a4j:queue requestDelay="500" ignoreDupResponses="true" /> > <h:column> > <h:outputText style="display:none;" value="#{s.id}"/> > <h:outputText style="display:none;" value="#{s.realName}"/> > </h:column> > <h:column> > <h:outputText value="#{s.name}" escape="false"/> > </h:column> > </rich:autocomplete> > </td> > <td> > <h:graphicImage value="/img/arrow.png" onclick="#{rich:component('provider-suggestion')}.setValue('');#{rich:component('provider-suggestion')}.showPopup();stopEvent(event);" > alt=""/> > <h:graphicImage value="/img/cancel.png" > onclick="#{rich:component('provider-suggestion')}.hidePopup();#{rich:component('provider-suggestion')}.setValue('');autocompleteChangeProvider(null);" > alt="#{messages['pages.clear']}" title="#{messages['pages.clear']}"/> > <h:inputHidden id="filter-provider-id" value="#{autocomplete.providerId}"/> > </td> > </tr> > </table> > {code} > as you can see, i don't use showButton="true", because i need another functionality, i need erase input text before show popup window. > I use JavaScript function "autocompleteChangeProvider" for extract selected id. > I use separate button(/img/cancel.png) for erase input text, as you can see this function just use Richfaces API. > > And a problem: > if autocomplete.providerName not null and not empty(in rich:autocomplete) and user clicks on show button(/img/arrow.png) than input text not erasing, but i called #{rich:component('provider-suggestion')}.setValue('') !!! > > I think i found a solution > AutocompleteBase.js has this code: > {code} > rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) { > // call constructor of parent class > $super.constructor.call(this, componentId); > this.selectId = selectId; > this.fieldId = fieldId; > this.options = $.extend({}, defaultOptions, options); > this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId); > this.currentValue = ""; > this.tempValue = this.getValue(); > this.isChanged = this.tempValue.length != 0; > bindEventHandlers.call(this); > }; > {code} > as you can see this.currentValue = "" so JS thinks that this.currentValue="" so currentValue equal new value("" - empty string), so nothing happens. > i replace this code by this: > {code} > rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) { > // call constructor of parent class > $super.constructor.call(this, componentId); > this.selectId = selectId; > this.fieldId = fieldId; > this.options = $.extend({}, defaultOptions, options); > this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId); > this.currentValue = $(rf.getDomElement(fieldId)).val(); > this.tempValue = this.getValue(); > this.isChanged = this.tempValue.length != 0; > bindEventHandlers.call(this); > }; > {code} > and it works! -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13298) Richfaces BOM manages a non Maven Central dependency

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13298?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13298: ------------------------------- Sprint: RichFaces 4.3.5 Sprint 1 > Richfaces BOM manages a non Maven Central dependency > ---------------------------------------------------- > > Key: RF-13298 > URL: https://issues.jboss.org/browse/RF-13298 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.3.2, 4.3.3, 4.3.4 > Reporter: Rafael Benevides > Fix For: 4.3.5 > > > Richfaces BOMs http://repo1.maven.org/maven2/org/richfaces/richfaces-bom/4.3.4.Final/ric... manages the following GAV: > org.richfaces.ui.common:richfaces-ui-common-api:${version.richfaces} which is not present on Maven Central ( http://search.maven.org/#search%7Cga%7C1%7Crichfaces-ui-common-api ) > BOM should have this scope changed or declare a https://repository.jboss.org/nexus repository -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13278) rich:tab : label, placed in header-facet, can not be refreshed per ajax

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13278: ------------------------------- Sprint: RichFaces 4.3.5 Sprint 1 > rich:tab : label, placed in header-facet, can not be refreshed per ajax > ----------------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Labels: regression > Fix For: 4.3.5 > > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <!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:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html" > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > <h:head> > </h:head> > <h:body> > > <a4j:log hotkey="M" mode="popup" /> > <h:form id="form" prependId="false"> > <rich:tabPanel id="tabPanel"> > <rich:tab header="tab 1"> > <a4j:commandLink value="click me" action="#{testBean.put('clicks',testBean.clicks + 1)}" render="label" execute="@this" /> > </rich:tab> > <rich:tab> > <f:facet name="header"> > <h:outputText id="label" value="#{testBean.clicks} clicks" /> > </f:facet> > </rich:tab> > </rich:tabPanel> > </h:form> > </h:body> > </html> > {code} > testBean is a simple session-scoped HashMap. -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13266) mediaOutput not working anymore on Glassfish3 and EAP6.1

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13266?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13266: ------------------------------- Sprint: RichFaces 4.3.5 Sprint 1 > mediaOutput not working anymore on Glassfish3 and EAP6.1 > -------------------------------------------------------- > > Key: RF-13266 > URL: https://issues.jboss.org/browse/RF-13266 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.4 > Environment: Glassfish 3.1.2.2 patched with Weld 1.1.14 (the problem appears also on earlier Weld builds) and JSF 2.1.26 and JDK 1.7.0_45 > Reporter: Fab Mars > Assignee: Matej Novotny > Labels: regression > Fix For: 4.3.5 > > > This is a followup to https://issues.jboss.org/browse/RF-13098 focusing on Glassfish3. > I have 2 mediaOutput in my code, none works. > The first one passes a Long as the value to the createContent method and the expected output is a PDF. I get > SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.util.el.ForwardingMethodExpression > The second one passes an array of 3 bytes (a color code) and the expected result is an image. I get > SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; [B > I'm preparing a reproducer on github and will share the url in the next comment. -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13317) ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate()

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13317: ------------------------------- Sprint: RichFaces 4.3.5 Sprint 1 > ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() > ----------------------------------------------------------------------------------------------- > > Key: RF-13317 > URL: https://issues.jboss.org/browse/RF-13317 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1 > Reporter: Matti Bickel > Assignee: Pavel Slegr > Priority: Critical > Labels: jsf22 > Fix For: 4.3.5 > > > I'm using several {{<rich:autocomplete>}} fields in a {{<h:form>}}, but have noticed the issue with several other AJAX requests: > When the response comes back, the data is fine but I get a JSF error saying > bq. During update: javax.faces.ViewState not found > Following that, no componentData is available to the Autocomplete component and no suggestions get displayed. > For reference the javadoc for ResponseStateManager.VIEW_STATE_PARAM says: > {quote} > Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view. > {quote} -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13358) rich:panelMenuGroup allowing actions executions even if originally disabled

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13358?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13358: ------------------------------- Sprint: RichFaces 4.3.5 Sprint 1 > rich:panelMenuGroup allowing actions executions even if originally disabled > --------------------------------------------------------------------------- > > Key: RF-13358 > URL: https://issues.jboss.org/browse/RF-13358 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.3.4 > Environment: Linux, AS 7.1.1 Brontes, FF 25 with FireBug addOn > Reporter: Pavel Slegr > Assignee: Pavel Slegr > Priority: Critical > Fix For: 4.3.5 > > > related to https://issues.jboss.org/browse/RF-12813 > This can be possibly a security hole, as the second component piece is discovered to allow tampering actions through JS. > I suggest to try out on other components as well !!! > with following example > {code} > { > <rich:panelMenuGroup id="group4" label="Group 4" expanded="false"> > <rich:panelMenuItem id="item41" label="Item 4.1" /> > <rich:panelMenuItem id="item42" label="Item 4.2" disabled="true" /> > <rich:panelMenuGroup id="group43" label="Group 4.1" disabled="true"> > <rich:panelMenuItem id="item431" label="Item 4.1.1" /> > </rich:panelMenuGroup> > </rich:panelMenuGroup> > } > {code} > the group43 element is intended to be disabled and thus not allowing any actions execution on it > Once tampered with > {code} > { > new RichFaces.ui.PanelMenuGroup("f:group43",{"collapseEvent":"click","unselectable":false,"selectable":false,"name":"group43","ajax":{"incId":"1"} ,"stylePrefix":"rf\u002Dpm\u002Dgr","expanded":false,"expandEvent":"click","disabled":false,"mode":"client"} ) > } > {code} > It is possible to expand the group and execute further actions on its children elements -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13397) a4j:push not working with Internet Explorer >= 10

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13397?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13397: ------------------------------- Sprint: RichFaces 4.3.5 Sprint 1 > a4j:push not working with Internet Explorer >= 10 > ------------------------------------------------- > > Key: RF-13397 > URL: https://issues.jboss.org/browse/RF-13397 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.3.4 > Environment: Any where Internet Explorer 10 or above is available > Reporter: Tobias Seppenhauser > Labels: richfaces > Fix For: 4.3.5 > > > The <a4j:push> mechanism seems to be broken when using the Internet Explorer 10 or above. This can easily be verified by visiting the corresponding showcase component [1]. The UUID never gets updated. > Unfortunately I can't see any error in the Javascript console. > [1] http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=push&sk... -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13310) Upgrade Graphene and Warp in 4.3 branch

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13310?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13310: ------------------------------- Sprint: RichFaces 4.3.5 Sprint 1 > Upgrade Graphene and Warp in 4.3 branch > --------------------------------------- > > Key: RF-13310 > URL: https://issues.jboss.org/browse/RF-13310 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 4.3.5 > Reporter: Lukáš Fryč > Fix For: 4.3.5 > > > The state of 4.3 branch framework tests is not as stable as 5.0, thus I track this as a separate issue. > Why we want to upgrade: > * Graphene = Final version API changes changes > * Warp = ease of debugging > I don't think this is absolutely necessary, I doesn;'t work with 4.3.x tests regularly and QE doesn't run them afaik. -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13369) autocomplete problem in glassfish 4 with jsf 2.2

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13369?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13369: ------------------------------- Fix Version/s: 4.5.0.Alpha2 (was: 5.0.0.Alpha3) > autocomplete problem in glassfish 4 with jsf 2.2 > ------------------------------------------------ > > Key: RF-13369 > URL: https://issues.jboss.org/browse/RF-13369 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4 > Environment: glassfish4 with JSF2.2, ubunto 12.04 > Reporter: Joao Granado > Labels: jsf22 > Fix For: 4.5.0.Alpha2 > > > autocomplete: the pop-up list always appears empty -- 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

12 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues December 2013