September 2011 - richfaces-issues

[JBoss JIRA] Created: (RF-11214) Sample for rich:fileUpload in showcase java.lang.IndexOutOfBoundsException is thrown when uploading and no picture is uploaded

by Juraj Huska (JIRA)

Sample for rich:fileUpload in showcase java.lang.IndexOutOfBoundsException is thrown when uploading and no picture is uploaded ------------------------------------------------------------------------------------------------------------------------------ Key: RF-11214 URL: https://issues.jboss.org/browse/RF-11214 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.1.0.Milestone1 Environment: richfaces-showcase-4.1.0.20110805-M1-jbas7.war, container JBoss AS 7, browser Firefox 5 Reporter: Juraj Huska Attachments: uploadWrong.png In sample for rich:fileUpload after adding correct .png file and clicking on upload no file is uploaded java.lang.IndexOutOfBoundsException is thrown, however the status is saying that picture was uploaded correctly. 10:43:56,165 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[Faces Servlet]] (http-localhost.localdomain-127.0.0.1-8080-1) Servlet.service() for servlet Faces Servlet threw exception: javax.el.ELException: /richfaces/fileUpload/samples/imgUpload-sample.xhtml @32,105 createContent="#{fileUploadBean.paint}": java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:111) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4] at org.richfaces.resource.MediaOutputResource.encode(MediaOutputResource.java:62) [richfaces-components-ui-4.1.0.20110805-M1.jar:] at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:188) [richfaces-core-impl-4.1.0.20110805-M1.jar:] at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:222) [richfaces-core-impl-4.1.0.20110805-M1.jar:] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:310) [jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.0.CR4.jar:7.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.0.CR4.jar:7.0.0.Final] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [weld-core-1.1.2.AS7.jar:2011-07-06 12:26] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.0.CR4.jar:7.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.0.CR4.jar:7.0.0.Final] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.0.CR4.jar:7.0.0.Final] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.0.CR4.jar:7.0.0.Final] at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.0.Final.jar:7.0.0.Final] at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.0.0.Final.jar:7.0.0.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.0.CR4.jar:7.0.0.Final] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.0.CR4.jar:7.0.0.Final] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.0.CR4.jar:7.0.0.Final] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.0.CR4.jar:7.0.0.Final] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.0.CR4.jar:7.0.0.Final] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.0.CR4.jar:7.0.0.Final] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [jbossweb-7.0.0.CR4.jar:7.0.0.Final] at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.RangeCheck(ArrayList.java:547) [:1.6.0_22] at java.util.ArrayList.get(ArrayList.java:322) [:1.6.0_22] at org.richfaces.demo.fileupload.FileUploadBean.paint(FileUploadBean.java:23) [classes:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_22] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_22] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_22] at org.apache.el.parser.AstValue.invoke(AstValue.java:196) [jbossweb-7.0.0.CR4.jar:7.0.0.Final] at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.0.CR4.jar:7.0.0.Final] at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.AS7.jar:2011-07-06 12:26] at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.AS7.jar:2011-07-06 12:26] at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4] ... 21 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
7
0 / 0

[JBoss JIRA] Created: (RF-11233) Can not invoke more than 1 message consumer in sample for CDI Push in showcase on IE 9

by Juraj Huska (JIRA)

Can not invoke more than 1 message consumer in sample for CDI Push in showcase on IE 9 -------------------------------------------------------------------------------------- Key: RF-11233 URL: https://issues.jboss.org/browse/RF-11233 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.1.0.Milestone1 Environment: richfaces-showcase-4.1.0.20110805-M1-jee6.war container - JBoss AS 6.0.0.Final browser - IE 9 Reporter: Juraj Huska Can not invoke more than 1 message consumer in sample for CDI Push in showcase on IE 9. When I attempt to open more than one consumers, the first one which was opened is replaced. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

5
7
0 / 0

[JBoss JIRA] Created: (RF-11196) Showcase - add rich:editor sample

by Lukáš Fryč (JIRA)

Showcase - add rich:editor sample --------------------------------- Key: RF-11196 URL: https://issues.jboss.org/browse/RF-11196 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.1.0.Milestone1 Reporter: Lukáš Fryč Assignee: Brian Leathem Fix For: 4.1.0.Milestone2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

5
5
0 / 0

[JBoss JIRA] Created: (RF-11344) rich:fileUpload causes a browser security warning in IE when using HTTPS

by Lee Theobald (JIRA)

rich:fileUpload causes a browser security warning in IE when using HTTPS ------------------------------------------------------------------------ Key: RF-11344 URL: https://issues.jboss.org/browse/RF-11344 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.2.2 Environment: IE6/Windows XP, HTTPS Reporter: Lee Theobald Assignee: Mikhail Vitenkov Fix For: 3.3.0 The Richfaces ComboBox is rendered using an empty iFrame when using Internet Explorer. This causes IE 6 to display a security warning that you are about to view a secure page with unsecure elements because the iFrame has an empty page inside which apparently IE considers an unsecure element.. This problem can be easily resolved by putting a relative reference to an empty page into the iFrame. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

6
9
0 / 0

[JBoss JIRA] Created: (RF-11110) Ajax push of CDI events directly, with no JMS requirement

by Brian Leathem (JIRA)

Ajax push of CDI events directly, with no JMS requirement --------------------------------------------------------- Key: RF-11110 URL: https://issues.jboss.org/browse/RF-11110 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-push/poll Reporter: Brian Leathem I would really like to see ajax push work with CDI events directly, without any requirement for JMS. Ideally we would leverage the work done in the Errai project. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

6
22
0 / 0

[JBoss JIRA] Created: (RF-10829) Slider: attribute onblur ignored

by Pavol Pitonak (JIRA)

Slider: attribute onblur ignored -------------------------------- Key: RF-10829 URL: https://issues.jboss.org/browse/RF-10829 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.0.0.Final Environment: RichFaces 4.1.0-SNAPSHOT r.22320 Metamer 4.1.0-SNAPSHOT r.22337 Mojarra 2.1.0-FCS GlassFish Server Open Source Edition 3.1-SNAPSHOT OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux Chrome 10.0.648.204 @ Linux x86_64 Reporter: Pavol Pitonak # deploy Metamer and open http://localhost:8080/metamer/faces/components/richInputNumberSlider/simp... # set onblur=alert('onblur') # focus on input and click outside of slider result: alert is not displayed -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
5
0 / 0

[JBoss JIRA] Created: (RF-10844) Panel menu item: onselect doesn't work in server mode

by Pavol Pitonak (JIRA)

Panel menu item: onselect doesn't work in server mode ----------------------------------------------------- Key: RF-10844 URL: https://issues.jboss.org/browse/RF-10844 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu Affects Versions: 4.0.0.Final Environment: RichFaces 4.1.0-SNAPSHOT r.22357 Metamer 4.1.0-SNAPSHOT r.22346 Mojarra 2.1.0-FCS GlassFish Server Open Source Edition 3.1-SNAPSHOT OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux Chrome 10.0.648.204 @ Linux x86_64 Reporter: Pavol Pitonak # deploy Metamer and open http://localhost:8080/metamer/faces/components/richPanelMenuItem/simple.x... # set mode=server # set onselect=alert('onselect') # select Item 1.2 result: no alert is displayed, works fine in ajax and client mode -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (RF-10853) dataScroller: do not works with a4j:status properly

by Ilya Shaikovsky (JIRA)

dataScroller: do not works with a4j:status properly --------------------------------------------------- Key: RF-10853 URL: https://issues.jboss.org/browse/RF-10853 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.0.0.Final Reporter: Ilya Shaikovsky 1) do not works properly with form scoped default status. onstart called but onstop - not. Problem seems in dataScroller because the same case with the button works see [1] 2) do not works at all using status="status". Seems just not implemented. [1] <rich:popupPanel id="splash" autosized="true" width="200" height="80" moveable="false" resizeable="false"> <f:facet name="header"><h:outputText value="WAIT" /></f:facet> <h:outputText value="WAIT!" /> </rich:popupPanel> <h:form id="form"> <a4j:status onstart="#{rich:component('splash')}.show()" onstop="#{rich:component('splash')}.hide()" /> <h:panelGrid columnClasses="acent"> <rich:dataScroller for="table" maxPages="5" /> <rich:dataTable value="#{carsBean.allInventoryItems}" var="car" id="table" rows="#{userBean.age}"> ................ </rich:dataTable> <rich:dataScroller for="table" maxPages="5" status="status"/> </h:panelGrid> <a4j:commandButton ></a4j:commandButton> </h:form> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
6
0 / 0

[JBoss JIRA] Created: (RF-11111) <a4j:status> for <rich:tree> works on selecting a node; not on toggling (via Ajax) in RF4.0.0

by Bastian Ulke (JIRA)

<a4j:status> for <rich:tree> works on selecting a node; not on toggling (via Ajax) in RF4.0.0 --------------------------------------------------------------------------------------------- Key: RF-11111 URL: https://issues.jboss.org/browse/RF-11111 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 4.0.0.Final Environment: WinXP; 6.0.0.Final; RichFaces 4.0.0 Reporter: Bastian Ulke I have got the following tree: <rich:tree var="item" id="someTree" selectionType="ajax" toggleType="ajax" treeSelectionChangeListener="#{someBean.selectionChanged}" selectionChangeListener="#{someBean.selectionChanged}"> <rich:treeModelRecursiveAdaptor roots="#{someBean.entities}" nodes="#{someBean.getSomeSubItems(item.id)}"> <rich:treeNode> <a4j:outputPanel> <h:outputText value="#{item.fullName}" /> </a4j:outputPanel> </rich:treeNode> </rich:treeModelRecursiveAdaptor> </rich:tree> And a status indicator: <a4j:status layout="block" startStyleClass="startAjax" > <f:facet name="start"> <img src="ajax-loader.gif" /> </f:facet </a4j:status> The combination works well for selecting (!) a node: When the AJAX-request is sent, it displays the gif, when it is received, it is removed. Unfortunatly, when performing a toggle on a node, the gif is displayed but never removed, although the data is correctly received and the view is updated. I added some alert('..') messages for the on{success|error|stop}-Properties of the <a4j:status> - same again: well fired for the selection of a particular node; but none ever executed for toggling. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
5
0 / 0

[JBoss JIRA] Created: (RF-11134) ComponentIdResolver does not resolve clientId correctly

by Val Blant (JIRA)

ComponentIdResolver does not resolve clientId correctly ------------------------------------------------------- Key: RF-11134 URL: https://issues.jboss.org/browse/RF-11134 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.0.Final Reporter: Val Blant Please consider the following test code: {code} <rich:dataTable id="testTable" value="#{dataTableTestBackingBean.rowsModel}" var="rowVar"> <f:facet name="header"> <rich:column> <h:outputText value="Column 1" /> </rich:column> </f:facet> <rich:column> <h:inputText id="valTest" value="#{rowVar.col1}" > <a4j:ajax event="blur" render="testColumn, footerTest" limitRender="true" execute="@this" /> </h:inputText> </rich:column> <rich:column> <h:outputText id="testColumn" value="#{dataTableTestBackingBean.footerValue}" /> </rich:column> <f:facet name="footer"> <rich:column> <h:outputText id="footerTest" value="#{dataTableTestBackingBean.footerValue}" /> </rich:column> </f:facet> </rich:dataTable> {code} This example will fail with the following Javascript error in the browser: {color:red} {quote} Error: During update: formId:testTable:0:footerTest not found {quote} {color} This is expected, b/c the correct id for the footer is _formId:testTable:footerTest_. The bug is in _org.richfaces.context.ComponentIdResolver_. Here is what happens: # The _RenderComponentCallback_ is executed on the input component (_'valTest'_ in the example) and it reads the list of short ids to render from the attached Ajax Behavior. Note that we got here by walking the parent data table model, so the current rowKey is 0 # _RenderComponentCallback_ asks _ComponentIdResolver_ to resolve short ids into client IDs # _ComponentIdResolver_ starts ascending up the tree from _'valTest'_ and looking at facets and children until it finds _'footerTest'_. # At this point it asks for the clientId of _'footerTest'_ w/o regard for the fact that the data model has a rowKey that is set 0 So, we get the wrong id b/c we call UiData.getClientId() outside of the normal walking order of that model. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
8
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues September 2011