December 2013 - richfaces-issues - Jboss List Archives

[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: (was: 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 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > 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

10 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: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > 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 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > 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

10 years, 4 months

1
0
0 / 0

[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: ------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours > 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 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13220) Quickstart - Remove references to AS 7.1 in the RichFaces quickstarts

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13220?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13220: ------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > Quickstart - Remove references to AS 7.1 in the RichFaces quickstarts > --------------------------------------------------------------------- > > Key: RF-13220 > URL: https://issues.jboss.org/browse/RF-13220 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Reporter: Sande Gilda > Assignee: Vineet Reynolds > Fix For: 4.3.5 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The readme files provide instruction on how to run quickstarts on both AS 7.1 and EAP 6. Quickstarts now target EAP 6.1, so we need to remove references to AS 7.1. -- 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

10 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: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > 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 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13247) Upgrade the RichFaces guava dependency to version 15.0

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13247?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13247: ------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > Upgrade the RichFaces guava dependency to version 15.0 > ------------------------------------------------------ > > Key: RF-13247 > URL: https://issues.jboss.org/browse/RF-13247 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Reporter: Jeremy Landis > Priority: Minor > Fix For: 4.3.5 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Upgrading to guava 15 from 14.0.1 causes this richfaces error. I have not looked into this further but wanted to put it out there as an issue. > Caused by: java.lang.IllegalAccessError: tried to access method com.google.common.collect.MapMaker.makeComputingMap(Lcom/google/common/base/Function;)Ljava/util/concurrent/ConcurrentMap; from class org.richfaces.resource.ResourceLibraryFactoryImpl -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13364) Upgrade Mojarra to 2.1.26 in RichFaces 4

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13364?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13364: ------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > Upgrade Mojarra to 2.1.26 in RichFaces 4 > ---------------------------------------- > > Key: RF-13364 > URL: https://issues.jboss.org/browse/RF-13364 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 4.3.4 > Reporter: Pavol Pitonak > Fix For: 4.3.5 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > RichFaces 4 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26. > [1] https://github.com/richfaces4/build/blob/master/bom/pom.xml -- 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

10 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: ------------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours > 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 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > 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

10 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: ------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > 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 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > 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

10 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: ------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > 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 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > 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

10 years, 4 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 2013