Page title

Now when I tab horizontally, it tabs fine. Columns move too. Which is expected. Step 2. Since 1 works fine, I switched back to (which is what I need ! ) Now, I need to hide the table horizontal scroll so that wrapper DIV scroll takes effect. Been trying for past few hours, its not working ! But I'm able to hide the vertical scroll with this style .rf-edt-b { overflow-y:hidden;overflow-x:hidden; } Why isn't the horizontal scroll going away ? I looked into the generated code, and I see this in the footer of the table :

Scrollable dataTable. Header scrolled badly on TAB button. > ---------------------------------------------------------- > > Key: RF-1107 > URL: https://issues.jboss.org/browse/RF-1107 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-ScrollableDataTable > Affects Versions: 3.2.0 > Environment: FF 2.0.0.6 > Reporter: Ilya Shaikovsky > Fix For: 3.Future > > Attachments: case - 1.png, case - 2.png, controls-scrollable-data-table.js, file1.txt > > > Two use-cases failed: > "case - 1.png" > frozenColCount=0 > all the columns with inputs > last columns aren't in visible part > When I use TAB key - columns scrolled to be displayed (good) but headers jsut stays (Wrong!) > "case - 2.png" > frozenColCount=2 > all the columns with inputs > last columns aren't in visible part > I use TAB key. Focused inputs changed one by one only in "frozen zone" (seems good), but after I press TAB on the last input - the focus jumps to non frozen column input and frozen columns - scrolled and shifted down(Wrong!). But headers still aren't scrolled (good in this case). -- 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 From issues at jboss.org Thu Feb 6 16:42:29 2014 From: issues at jboss.org (Shantanu Upadhyaya (JIRA)) Date: Thu, 6 Feb 2014 16:42:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-1107) Scrollable dataTable. Header scrolled badly on TAB button. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942431#comment-12942431 ] Shantanu Upadhyaya commented on RF-1107: ---------------------------------------- So the question is - how to hide the horizontal scroll of , so that we can create a wrapper DIV with horizontal scroll ? > Scrollable dataTable. Header scrolled badly on TAB button. > ---------------------------------------------------------- > > Key: RF-1107 > URL: https://issues.jboss.org/browse/RF-1107 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-ScrollableDataTable > Affects Versions: 3.2.0 > Environment: FF 2.0.0.6 > Reporter: Ilya Shaikovsky > Fix For: 3.Future > > Attachments: case - 1.png, case - 2.png, controls-scrollable-data-table.js, file1.txt > > > Two use-cases failed: > "case - 1.png" > frozenColCount=0 > all the columns with inputs > last columns aren't in visible part > When I use TAB key - columns scrolled to be displayed (good) but headers jsut stays (Wrong!) > "case - 2.png" > frozenColCount=2 > all the columns with inputs > last columns aren't in visible part > I use TAB key. Focused inputs changed one by one only in "frozen zone" (seems good), but after I press TAB on the last input - the focus jumps to non frozen column input and frozen columns - scrolled and shifted down(Wrong!). But headers still aren't scrolled (good in this case). -- 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 From issues at jboss.org Thu Feb 6 18:42:29 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 6 Feb 2014 18:42:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13531) selects: cannot select option on IE11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13531. -------------------------------- Assignee: Brian Leathem Resolution: Done Replaced the mouseenter/leave event handlers with a top-level delegating event handler. QE please check all components that use list.js: * select * inplaceSelect * picklist * orderingList Note: This fix will have to be forward ported into RF 4.5 and RF 5. > selects: cannot select option on IE11 > ------------------------------------- > > Key: RF-13531 > URL: https://issues.jboss.org/browse/RF-13531 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.3.5, 4.5.0.Alpha2, 5.0.0.Alpha3 > Environment: IE 11 > Reporter: Ji?? ?tefek > Assignee: Brian Leathem > Labels: IE11 > Fix For: 4.3.6 > > > Components: autocomplete, select, inplaceSelect. > Works on IE 10. > ---- > Issues: > * User cannot visually select an option from the popup list == moving mouse over the items in the list will not change theirs class. > ** however clicking on the item will select the option correctly. {color:red}EXCEPT autocomplete (RF4), where it will not select anything{color}. > ** workaround: the item can be selected, when moving off the list and back to it on the correct item, but the cursor should not move through scroller. > * User cannot select option with keyboard. -- 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 From issues at jboss.org Thu Feb 6 18:42:30 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 6 Feb 2014 18:42:30 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13531) selects: cannot select option on IE11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13531: ------------------------------- Labels: IE11 needs-qe (was: IE11) > selects: cannot select option on IE11 > ------------------------------------- > > Key: RF-13531 > URL: https://issues.jboss.org/browse/RF-13531 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.3.5, 4.5.0.Alpha2, 5.0.0.Alpha3 > Environment: IE 11 > Reporter: Ji?? ?tefek > Assignee: Brian Leathem > Labels: IE11, needs-qe > Fix For: 4.3.6 > > > Components: autocomplete, select, inplaceSelect. > Works on IE 10. > ---- > Issues: > * User cannot visually select an option from the popup list == moving mouse over the items in the list will not change theirs class. > ** however clicking on the item will select the option correctly. {color:red}EXCEPT autocomplete (RF4), where it will not select anything{color}. > ** workaround: the item can be selected, when moving off the list and back to it on the correct item, but the cursor should not move through scroller. > * User cannot select option with keyboard. -- 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 From issues at jboss.org Thu Feb 6 22:48:28 2014 From: issues at jboss.org (alexey plotnikov (JIRA)) Date: Thu, 6 Feb 2014 22:48:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13537) Autocomplete: onbegin attribute igniored In-Reply-To: References: Message-ID: alexey plotnikov created RF-13537: ------------------------------------- Summary: Autocomplete: onbegin attribute igniored Key: RF-13537 URL: https://issues.jboss.org/browse/RF-13537 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.3.5 Reporter: alexey plotnikov "onbegin" attribute of rich:autocomplete is always ignored! I suggest next fix: In file Autocomplete.js: {code} var callAjax = function(event, callback) { ... this.isFirstAjax = false; //caution: JSF submits inputs with empty names causing "WARNING: Parameters: Invalid chunk ignored." in Tomcat log var params = {}; params[this.id + ".ajax"] = "1"; rf.ajax(this.id, event, {parameters: params, error: ajaxError, complete:ajaxSuccess}); } {code} for fixing, we must replace on {code} var callAjax = function(event, callback) { ... this.isFirstAjax = false; //caution: JSF submits inputs with empty names causing "WARNING: Parameters: Invalid chunk ignored." in Tomcat log var params = {}; params[this.id + ".ajax"] = "1"; var parameters_extended = {parameters: params, error: ajaxError, complete:ajaxSuccess}; if (this.options.onbegin != undefined) { parameters_extended.begin = this.options.onbegin; } rf.ajax(this.id, event, parameters_extended); } {code} I can create pull request if everything ok. -- 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 From issues at jboss.org Fri Feb 7 07:06:28 2014 From: issues at jboss.org (Frank Langelage (JIRA)) Date: Fri, 7 Feb 2014 07:06:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13168) 3rd party JSF component disappears on RichFaces ajax refresh In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frank Langelage reopened RF-13168: ---------------------------------- > 3rd party JSF component disappears on RichFaces ajax refresh > ------------------------------------------------------------ > > Key: RF-13168 > URL: https://issues.jboss.org/browse/RF-13168 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility, component-a4j-core > Reporter: Frank Langelage > Assignee: Luk?? Fry? > Labels: interop, jsf22 > Fix For: 5.0.0.Alpha3 > > Attachments: install-mojarra-2.1.19.cli, Jira-WFLY-UT.tar, xaa, xab, xac > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > On some of my pages I'm using richfaces a4j:poll to refresh components regularly. The components refreshed is an openfaces datatable. > This does not work with WildFly build from current sources. > Same code works with JBoss AS 7.20. So problem is not related to richfaces or openfaces for me. Probably related to replacement of jboss-web with undertow. > I'll attach a small project showing the problem. > The mojarra datatable works fine, is refreshed every 10 seconds. > The openfaces datatable below disappears on first refresh. -- 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 From issues at jboss.org Fri Feb 7 07:08:28 2014 From: issues at jboss.org (Frank Langelage (JIRA)) Date: Fri, 7 Feb 2014 07:08:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13168) 3rd party JSF component disappears on RichFaces ajax refresh In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frank Langelage updated RF-13168: --------------------------------- Attachment: Jira-WFLY-UT.tar xaa xab xac slightly updated test case. This can be used to reproduce the problem. As said, the only artifact that changed is the JSF version. > 3rd party JSF component disappears on RichFaces ajax refresh > ------------------------------------------------------------ > > Key: RF-13168 > URL: https://issues.jboss.org/browse/RF-13168 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility, component-a4j-core > Reporter: Frank Langelage > Assignee: Luk?? Fry? > Labels: interop, jsf22 > Fix For: 5.0.0.Alpha3 > > Attachments: install-mojarra-2.1.19.cli, Jira-WFLY-UT.tar, Jira-WFLY-UT.tar, xaa, xaa, xab, xab, xac, xac > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > On some of my pages I'm using richfaces a4j:poll to refresh components regularly. The components refreshed is an openfaces datatable. > This does not work with WildFly build from current sources. > Same code works with JBoss AS 7.20. So problem is not related to richfaces or openfaces for me. Probably related to replacement of jboss-web with undertow. > I'll attach a small project showing the problem. > The mojarra datatable works fine, is refreshed every 10 seconds. > The openfaces datatable below disappears on first refresh. -- 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 From issues at jboss.org Fri Feb 7 08:12:29 2014 From: issues at jboss.org (Daniele Benegiamo (JIRA)) Date: Fri, 7 Feb 2014 08:12:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13534) a4j:mediaOutput on GF4: "Unauthorized deserialisation attempt" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942596#comment-12942596 ] Daniele Benegiamo commented on RF-13534: ---------------------------------------- Hi [~ppitonak], also with that change it still raises the same error, with the same stack trace. > a4j:mediaOutput on GF4: "Unauthorized deserialisation attempt" > -------------------------------------------------------------- > > Key: RF-13534 > URL: https://issues.jboss.org/browse/RF-13534 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Environment: Glassfish 4.0, Mac OS X 10.9.1, Java(TM) SE Runtime Environment (build 1.7.0_21-b12), Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01, mixed mode) > Reporter: Daniele Benegiamo > Assignee: Pavol Pitonak > > On GF4.0 any attempt to use {{}} raises the same exception ("{{java.io.InvalidClassException: Unauthorized deserialisation attempt}}"). Everything works nicely with the old RichFaces 4.1.0. > Below you can find a stack trace, a sample page and a sample managed bean as minimum reproducible test case. > To keep the test case short, the sample doesn't uses the {{value}} attribute, but exceptions are raised also when using it (e.g. passing a simple {{java.lang.String}}). > From a first quick analysis seems that: > * basic types (as {{java.lang.String}}) are not properly detected as "de-serializable"; > * types implementing {{Serializable}} or {{SerializableResource}} interfaces are impossible to instantiate by {{LookAheadObjectInputStream}} (row 118 - {{Class.forName()}} call in {{isClassValid()}} method - raises a {{ClassNotFoundException}} exception). > {code:title=Exception} > SEVERE: Input error for deserialize data > java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.util.el.ForwardingMethodExpression > at org.richfaces.util.LookAheadObjectInputStream.resolveClass(LookAheadObjectInputStream.java:105) > at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1610) > at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515) > at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1620) > at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1769) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) > at com.sun.faces.facelets.el.TagMethodExpression.readExternal(TagMethodExpression.java:158) > at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1835) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1794) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) > at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1989) > at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1913) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1796) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) > at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1704) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1342) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) > at org.richfaces.util.Util.decodeObjectData(Util.java:237) > at org.richfaces.resource.DefaultCodecResourceRequestData.getData(DefaultCodecResourceRequestData.java:97) > at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:337) > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:156) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:643) > at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1682) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:318) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:160) > at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:734) > at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:673) > at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:99) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:174) > at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:357) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:260) > at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:188) > at org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:191) > at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:168) > at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:189) > at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:288) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:206) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:136) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:114) > at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77) > at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:838) > at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:113) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:115) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access$100(WorkerThreadIOStrategy.java:55) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:135) > at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:564) > at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:544) > at java.lang.Thread.run(Thread.java:722) > WARNING: StandardWrapperValve[Faces Servlet]: Servlet.service() for servlet Faces Servlet threw exception > java.lang.NullPointerException > at org.richfaces.resource.MediaOutputResource.encode(MediaOutputResource.java:62) > at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:188) > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:229) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:643) > at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1682) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:318) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:160) > at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:734) > at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:673) > at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:99) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:174) > at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:357) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:260) > at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:188) > at org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:191) > at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:168) > at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:189) > at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:288) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:206) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:136) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:114) > at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77) > at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:838) > at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:113) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:115) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access$100(WorkerThreadIOStrategy.java:55) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:135) > at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:564) > at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:544) > at java.lang.Thread.run(Thread.java:722) > {code} > {code:xml|title=index.xhtml} > > > xmlns:h="http://xmlns.jcp.org/jsf/html" > xmlns:a4j="http://richfaces.org/a4j"> > > Page title > > > > > > {code} > {code:java|title=MyBean.java} > package org.example; > import java.awt.Color; > import java.awt.Font; > import java.awt.Graphics2D; > import java.awt.image.BufferedImage; > import java.io.IOException; > import javax.enterprise.context.RequestScoped; > import javax.imageio.ImageIO; > import javax.inject.Named; > @Named > @RequestScoped > public class MyBean > { > public void myCreateContent (java.io.OutputStream output, java.lang.Object input) > throws IOException > { > BufferedImage img = new BufferedImage (400, 200, BufferedImage.TYPE_INT_RGB); > Graphics2D graphics2D = img.createGraphics (); > graphics2D.setBackground (Color.BLACK); > graphics2D.setColor (Color.WHITE); > graphics2D.clearRect (0, 0, img.getWidth (), img.getHeight ()); > graphics2D.setFont (new Font ("Arial", Font.PLAIN, 12)); > graphics2D.drawString ("String", 20, 35); > ImageIO.write (img, "png", output); > } > } > {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 From issues at jboss.org Fri Feb 7 08:26:29 2014 From: issues at jboss.org (Daniele Benegiamo (JIRA)) Date: Fri, 7 Feb 2014 08:26:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13534) a4j:mediaOutput on GF4: "Unauthorized deserialisation attempt" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniele Benegiamo updated RF-13534: ----------------------------------- Attachment: MediaOutput.zip The test case (with used JARs included). It's a NetBeans 7.4 project. > a4j:mediaOutput on GF4: "Unauthorized deserialisation attempt" > -------------------------------------------------------------- > > Key: RF-13534 > URL: https://issues.jboss.org/browse/RF-13534 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Environment: Glassfish 4.0, Mac OS X 10.9.1, Java(TM) SE Runtime Environment (build 1.7.0_21-b12), Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01, mixed mode) > Reporter: Daniele Benegiamo > Assignee: Pavol Pitonak > Attachments: MediaOutput.zip > > > On GF4.0 any attempt to use {{}} raises the same exception ("{{java.io.InvalidClassException: Unauthorized deserialisation attempt}}"). Everything works nicely with the old RichFaces 4.1.0. > Below you can find a stack trace, a sample page and a sample managed bean as minimum reproducible test case. > To keep the test case short, the sample doesn't uses the {{value}} attribute, but exceptions are raised also when using it (e.g. passing a simple {{java.lang.String}}). > From a first quick analysis seems that: > * basic types (as {{java.lang.String}}) are not properly detected as "de-serializable"; > * types implementing {{Serializable}} or {{SerializableResource}} interfaces are impossible to instantiate by {{LookAheadObjectInputStream}} (row 118 - {{Class.forName()}} call in {{isClassValid()}} method - raises a {{ClassNotFoundException}} exception). > {code:title=Exception} > SEVERE: Input error for deserialize data > java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.util.el.ForwardingMethodExpression > at org.richfaces.util.LookAheadObjectInputStream.resolveClass(LookAheadObjectInputStream.java:105) > at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1610) > at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515) > at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1620) > at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1769) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) > at com.sun.faces.facelets.el.TagMethodExpression.readExternal(TagMethodExpression.java:158) > at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1835) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1794) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) > at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1989) > at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1913) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1796) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) > at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1704) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1342) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) > at org.richfaces.util.Util.decodeObjectData(Util.java:237) > at org.richfaces.resource.DefaultCodecResourceRequestData.getData(DefaultCodecResourceRequestData.java:97) > at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:337) > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:156) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:643) > at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1682) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:318) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:160) > at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:734) > at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:673) > at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:99) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:174) > at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:357) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:260) > at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:188) > at org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:191) > at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:168) > at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:189) > at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:288) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:206) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:136) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:114) > at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77) > at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:838) > at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:113) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:115) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access$100(WorkerThreadIOStrategy.java:55) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:135) > at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:564) > at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:544) > at java.lang.Thread.run(Thread.java:722) > WARNING: StandardWrapperValve[Faces Servlet]: Servlet.service() for servlet Faces Servlet threw exception > java.lang.NullPointerException > at org.richfaces.resource.MediaOutputResource.encode(MediaOutputResource.java:62) > at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:188) > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:229) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:643) > at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1682) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:318) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:160) > at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:734) > at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:673) > at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:99) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:174) > at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:357) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:260) > at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:188) > at org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:191) > at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:168) > at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:189) > at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:288) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:206) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:136) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:114) > at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77) > at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:838) > at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:113) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:115) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access$100(WorkerThreadIOStrategy.java:55) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:135) > at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:564) > at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:544) > at java.lang.Thread.run(Thread.java:722) > {code} > {code:xml|title=index.xhtml} > > > xmlns:h="http://xmlns.jcp.org/jsf/html" > xmlns:a4j="http://richfaces.org/a4j"> > > Page title > > > > > > {code} > {code:java|title=MyBean.java} > package org.example; > import java.awt.Color; > import java.awt.Font; > import java.awt.Graphics2D; > import java.awt.image.BufferedImage; > import java.io.IOException; > import javax.enterprise.context.RequestScoped; > import javax.imageio.ImageIO; > import javax.inject.Named; > @Named > @RequestScoped > public class MyBean > { > public void myCreateContent (java.io.OutputStream output, java.lang.Object input) > throws IOException > { > BufferedImage img = new BufferedImage (400, 200, BufferedImage.TYPE_INT_RGB); > Graphics2D graphics2D = img.createGraphics (); > graphics2D.setBackground (Color.BLACK); > graphics2D.setColor (Color.WHITE); > graphics2D.clearRect (0, 0, img.getWidth (), img.getHeight ()); > graphics2D.setFont (new Font ("Arial", Font.PLAIN, 12)); > graphics2D.drawString ("String", 20, 35); > ImageIO.write (img, "png", output); > } > } > {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 From issues at jboss.org Fri Feb 7 12:00:30 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 7 Feb 2014 12:00:30 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13537) Autocomplete: onbegin attribute igniored In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942691#comment-12942691 ] Brian Leathem commented on RF-13537: ------------------------------------ That's great, thanks for investigating [~alixey]. At first glance you patch looks good. Please go ahead and issue a Pull Request. (Don't forget to sign the [CLA|https://cla.jboss.org/index.seam] if you haven't previously done so) > Autocomplete: onbegin attribute igniored > ---------------------------------------- > > Key: RF-13537 > URL: https://issues.jboss.org/browse/RF-13537 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Reporter: alexey plotnikov > > "onbegin" attribute of rich:autocomplete is always ignored! > I suggest next fix: > In file Autocomplete.js: > {code} > var callAjax = function(event, callback) { > ... > this.isFirstAjax = false; > //caution: JSF submits inputs with empty names causing "WARNING: Parameters: Invalid chunk ignored." in Tomcat log > var params = {}; > params[this.id + ".ajax"] = "1"; > rf.ajax(this.id, event, {parameters: params, error: ajaxError, complete:ajaxSuccess}); > } > {code} > for fixing, we must replace on > {code} > var callAjax = function(event, callback) { > ... > this.isFirstAjax = false; > //caution: JSF submits inputs with empty names causing "WARNING: Parameters: Invalid chunk ignored." in Tomcat log > var params = {}; > params[this.id + ".ajax"] = "1"; > var parameters_extended = {parameters: params, error: ajaxError, complete:ajaxSuccess}; > if (this.options.onbegin != undefined) { > parameters_extended.begin = this.options.onbegin; > } > rf.ajax(this.id, event, parameters_extended); > } > {code} > I can create pull request if everything ok. -- 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 From issues at jboss.org Fri Feb 7 12:00:30 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 7 Feb 2014 12:00:30 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13537) Autocomplete: onbegin attribute igniored In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13537: ------------------------------- Fix Version/s: 4.3.6 > Autocomplete: onbegin attribute igniored > ---------------------------------------- > > Key: RF-13537 > URL: https://issues.jboss.org/browse/RF-13537 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Reporter: alexey plotnikov > Fix For: 4.3.6 > > > "onbegin" attribute of rich:autocomplete is always ignored! > I suggest next fix: > In file Autocomplete.js: > {code} > var callAjax = function(event, callback) { > ... > this.isFirstAjax = false; > //caution: JSF submits inputs with empty names causing "WARNING: Parameters: Invalid chunk ignored." in Tomcat log > var params = {}; > params[this.id + ".ajax"] = "1"; > rf.ajax(this.id, event, {parameters: params, error: ajaxError, complete:ajaxSuccess}); > } > {code} > for fixing, we must replace on > {code} > var callAjax = function(event, callback) { > ... > this.isFirstAjax = false; > //caution: JSF submits inputs with empty names causing "WARNING: Parameters: Invalid chunk ignored." in Tomcat log > var params = {}; > params[this.id + ".ajax"] = "1"; > var parameters_extended = {parameters: params, error: ajaxError, complete:ajaxSuccess}; > if (this.options.onbegin != undefined) { > parameters_extended.begin = this.options.onbegin; > } > rf.ajax(this.id, event, parameters_extended); > } > {code} > I can create pull request if everything ok. -- 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 From issues at jboss.org Fri Feb 7 12:00:30 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 7 Feb 2014 12:00:30 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13168) 3rd party JSF component disappears on RichFaces ajax refresh In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13168: ------------------------------- Fix Version/s: (was: 5.0.0.Alpha3) > 3rd party JSF component disappears on RichFaces ajax refresh > ------------------------------------------------------------ > > Key: RF-13168 > URL: https://issues.jboss.org/browse/RF-13168 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility, component-a4j-core > Reporter: Frank Langelage > Assignee: Luk?? Fry? > Labels: interop, jsf22 > Attachments: install-mojarra-2.1.19.cli, Jira-WFLY-UT.tar, Jira-WFLY-UT.tar, xaa, xaa, xab, xab, xac, xac > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > On some of my pages I'm using richfaces a4j:poll to refresh components regularly. The components refreshed is an openfaces datatable. > This does not work with WildFly build from current sources. > Same code works with JBoss AS 7.20. So problem is not related to richfaces or openfaces for me. Probably related to replacement of jboss-web with undertow. > I'll attach a small project showing the problem. > The mojarra datatable works fine, is refreshed every 10 seconds. > The openfaces datatable below disappears on first refresh. -- 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 From issues at jboss.org Fri Feb 7 12:02:29 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 7 Feb 2014 12:02:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-1107) Scrollable dataTable. Header scrolled badly on TAB button. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942694#comment-12942694 ] Brian Leathem commented on RF-1107: ----------------------------------- We'll have to move the CSS rule from an inline style to an external CSS file, then we will be able to override it. Please file a new jira for this. (Note: you can try using the !important CSS marker as a temporary workaround) > Scrollable dataTable. Header scrolled badly on TAB button. > ---------------------------------------------------------- > > Key: RF-1107 > URL: https://issues.jboss.org/browse/RF-1107 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-ScrollableDataTable > Affects Versions: 3.2.0 > Environment: FF 2.0.0.6 > Reporter: Ilya Shaikovsky > Fix For: 3.Future > > Attachments: case - 1.png, case - 2.png, controls-scrollable-data-table.js, file1.txt > > > Two use-cases failed: > "case - 1.png" > frozenColCount=0 > all the columns with inputs > last columns aren't in visible part > When I use TAB key - columns scrolled to be displayed (good) but headers jsut stays (Wrong!) > "case - 2.png" > frozenColCount=2 > all the columns with inputs > last columns aren't in visible part > I use TAB key. Focused inputs changed one by one only in "frozen zone" (seems good), but after I press TAB on the last input - the focus jumps to non frozen column input and frozen columns - scrolled and shifted down(Wrong!). But headers still aren't scrolled (good in this case). -- 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 From issues at jboss.org Mon Feb 10 04:45:28 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 10 Feb 2014 04:45:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13531) selects: cannot select option on IE11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek reopened RF-13531: ------------------------------ The select and inplaceSelect are fixed. The picklist and orderingList are OK. Tried with IE 11 and FF 26. BUT the autocomplete is still not working. Reopening. > selects: cannot select option on IE11 > ------------------------------------- > > Key: RF-13531 > URL: https://issues.jboss.org/browse/RF-13531 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.3.5, 4.5.0.Alpha2, 5.0.0.Alpha3 > Environment: IE 11 > Reporter: Ji?? ?tefek > Assignee: Brian Leathem > Labels: IE11, needs-qe > Fix For: 4.3.6 > > > Components: autocomplete, select, inplaceSelect. > Works on IE 10. > ---- > Issues: > * User cannot visually select an option from the popup list == moving mouse over the items in the list will not change theirs class. > ** however clicking on the item will select the option correctly. {color:red}EXCEPT autocomplete (RF4), where it will not select anything{color}. > ** workaround: the item can be selected, when moving off the list and back to it on the correct item, but the cursor should not move through scroller. > * User cannot select option with keyboard. -- 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 From issues at jboss.org Mon Feb 10 05:11:29 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 10 Feb 2014 05:11:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11736) rich:popupPanel x domElementAttachment="parent" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated RF-11736: ----------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1063222 > rich:popupPanel x domElementAttachment="parent" > ----------------------------------------------- > > Key: RF-11736 > URL: https://issues.jboss.org/browse/RF-11736 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.Final > Environment: NetBeans 7.0.0 + GlassFish 3.1.1 + JSF2 + CDI + RF4 + Hibernate3 > Reporter: Edilmar Alves > Fix For: 5-Tracking > > > rich:popupPanel repositions after second click when we use domElementAttachment="parent" -- 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 From issues at jboss.org Mon Feb 10 10:31:29 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Mon, 10 Feb 2014 10:31:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13534) a4j:mediaOutput on GF4: "Unauthorized deserialisation attempt" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-13534: ---------------------------------- Assignee: Juraj H?ska (was: Pavol Pitonak) Juraj, please try to reproduce. > a4j:mediaOutput on GF4: "Unauthorized deserialisation attempt" > -------------------------------------------------------------- > > Key: RF-13534 > URL: https://issues.jboss.org/browse/RF-13534 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Environment: Glassfish 4.0, Mac OS X 10.9.1, Java(TM) SE Runtime Environment (build 1.7.0_21-b12), Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01, mixed mode) > Reporter: Daniele Benegiamo > Assignee: Juraj H?ska > Attachments: MediaOutput.zip > > > On GF4.0 any attempt to use {{}} raises the same exception ("{{java.io.InvalidClassException: Unauthorized deserialisation attempt}}"). Everything works nicely with the old RichFaces 4.1.0. > Below you can find a stack trace, a sample page and a sample managed bean as minimum reproducible test case. > To keep the test case short, the sample doesn't uses the {{value}} attribute, but exceptions are raised also when using it (e.g. passing a simple {{java.lang.String}}). > From a first quick analysis seems that: > * basic types (as {{java.lang.String}}) are not properly detected as "de-serializable"; > * types implementing {{Serializable}} or {{SerializableResource}} interfaces are impossible to instantiate by {{LookAheadObjectInputStream}} (row 118 - {{Class.forName()}} call in {{isClassValid()}} method - raises a {{ClassNotFoundException}} exception). > {code:title=Exception} > SEVERE: Input error for deserialize data > java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.util.el.ForwardingMethodExpression > at org.richfaces.util.LookAheadObjectInputStream.resolveClass(LookAheadObjectInputStream.java:105) > at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1610) > at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515) > at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1620) > at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1769) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) > at com.sun.faces.facelets.el.TagMethodExpression.readExternal(TagMethodExpression.java:158) > at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1835) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1794) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) > at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1989) > at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1913) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1796) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) > at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1704) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1342) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) > at org.richfaces.util.Util.decodeObjectData(Util.java:237) > at org.richfaces.resource.DefaultCodecResourceRequestData.getData(DefaultCodecResourceRequestData.java:97) > at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:337) > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:156) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:643) > at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1682) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:318) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:160) > at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:734) > at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:673) > at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:99) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:174) > at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:357) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:260) > at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:188) > at org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:191) > at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:168) > at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:189) > at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:288) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:206) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:136) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:114) > at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77) > at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:838) > at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:113) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:115) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access$100(WorkerThreadIOStrategy.java:55) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:135) > at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:564) > at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:544) > at java.lang.Thread.run(Thread.java:722) > WARNING: StandardWrapperValve[Faces Servlet]: Servlet.service() for servlet Faces Servlet threw exception > java.lang.NullPointerException > at org.richfaces.resource.MediaOutputResource.encode(MediaOutputResource.java:62) > at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:188) > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:229) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:643) > at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1682) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:318) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:160) > at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:734) > at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:673) > at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:99) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:174) > at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:357) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:260) > at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:188) > at org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:191) > at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:168) > at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:189) > at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:288) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:206) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:136) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:114) > at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77) > at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:838) > at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:113) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:115) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access$100(WorkerThreadIOStrategy.java:55) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:135) > at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:564) > at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:544) > at java.lang.Thread.run(Thread.java:722) > {code} > {code:xml|title=index.xhtml} > > > xmlns:h="http://xmlns.jcp.org/jsf/html" > xmlns:a4j="http://richfaces.org/a4j"> > > Page title > > > > > > {code} > {code:java|title=MyBean.java} > package org.example; > import java.awt.Color; > import java.awt.Font; > import java.awt.Graphics2D; > import java.awt.image.BufferedImage; > import java.io.IOException; > import javax.enterprise.context.RequestScoped; > import javax.imageio.ImageIO; > import javax.inject.Named; > @Named > @RequestScoped > public class MyBean > { > public void myCreateContent (java.io.OutputStream output, java.lang.Object input) > throws IOException > { > BufferedImage img = new BufferedImage (400, 200, BufferedImage.TYPE_INT_RGB); > Graphics2D graphics2D = img.createGraphics (); > graphics2D.setBackground (Color.BLACK); > graphics2D.setColor (Color.WHITE); > graphics2D.clearRect (0, 0, img.getWidth (), img.getHeight ()); > graphics2D.setFont (new Font ("Arial", Font.PLAIN, 12)); > graphics2D.drawString ("String", 20, 35); > ImageIO.write (img, "png", output); > } > } > {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 From issues at jboss.org Mon Feb 10 14:09:30 2014 From: issues at jboss.org (Silvana Deana (JIRA)) Date: Mon, 10 Feb 2014 14:09:30 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-4308) rich:pickList: keep sort order of source list after add/remove operations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943175#comment-12943175 ] Silvana Deana commented on RF-4308: ----------------------------------- Sorry about my ignorance. But, What do you mean when you day "include this orderedPickListFix.js in your app" If I add it as a common script it give me an error, and id I add it with JQuery, my menus stop working. So ... I'm lost Thanks in advance > rich:pickList: keep sort order of source list after add/remove operations > ------------------------------------------------------------------------- > > Key: RF-4308 > URL: https://issues.jboss.org/browse/RF-4308 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 3.2.2, 4.3.4, 5.0.0.Alpha1 > Reporter: Martin H?ller > Labels: low_hanging_fruit, order, picklist, sort > Fix For: 5-Tracking > > > When adding items from the source list to the target list and removing this items again, the original order of the source list is not preserved. This makes it hard to find items in a list that is longer than just a fest items. A good example is the second example on the livedemo at http://livedemo.exadel.com/richfaces-demo/richfaces/pickList.jsf. Add the first state (Alabama) and remove it. It can now be found at the very end of the otherwise alphabetical list of states. This can be rather unintuitive for a user. > My suggestion is either remember the original sort order of the source list, or add some attribute that enables automatic sorting. -- 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 From issues at jboss.org Mon Feb 10 14:11:30 2014 From: issues at jboss.org (Silvana Deana (JIRA)) Date: Mon, 10 Feb 2014 14:11:30 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-4308) rich:pickList: keep sort order of source list after add/remove operations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943175#comment-12943175 ] Silvana Deana edited comment on RF-4308 at 2/10/14 2:09 PM: ------------------------------------------------------------ Sorry about my ignorance. But, What do you mean when you day "include this orderedPickListFix.js in your app" If I add it as a common script it give me an error, and id I add it with JQuery, my menus stop working. So ... I'm lost We are using richFaces 3.3.3 with Facelets. Thanks in advance was (Author: silvana.deana): Sorry about my ignorance. But, What do you mean when you day "include this orderedPickListFix.js in your app" If I add it as a common script it give me an error, and id I add it with JQuery, my menus stop working. So ... I'm lost Thanks in advance > rich:pickList: keep sort order of source list after add/remove operations > ------------------------------------------------------------------------- > > Key: RF-4308 > URL: https://issues.jboss.org/browse/RF-4308 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 3.2.2, 4.3.4, 5.0.0.Alpha1 > Reporter: Martin H?ller > Labels: low_hanging_fruit, order, picklist, sort > Fix For: 5-Tracking > > > When adding items from the source list to the target list and removing this items again, the original order of the source list is not preserved. This makes it hard to find items in a list that is longer than just a fest items. A good example is the second example on the livedemo at http://livedemo.exadel.com/richfaces-demo/richfaces/pickList.jsf. Add the first state (Alabama) and remove it. It can now be found at the very end of the otherwise alphabetical list of states. This can be rather unintuitive for a user. > My suggestion is either remember the original sort order of the source list, or add some attribute that enables automatic sorting. -- 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 From issues at jboss.org Tue Feb 11 00:53:28 2014 From: issues at jboss.org (Steven W. (JIRA)) Date: Tue, 11 Feb 2014 00:53:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13458) CommandLink Javassist Compatibility Failures (richfaces-5.0.0.Alpha2) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943287#comment-12943287 ] Steven W. commented on RF-13458: -------------------------------- Hi I've created a minimized sample - this was easier to achieve than the reproducer. As-is all you need to do is startup tomcat with the Example web app and you'll see the exception. Simply replace the m2 richfaces with m1 and you'll see it runs. Example webapp: http://www.entracity.com/example/Example.war Source to produce: http://www.entracity.com/example/m2-javassist-exception-example-src.zip I hope this helps yield a ready solution :) Thanks, Steve > CommandLink Javassist Compatibility Failures (richfaces-5.0.0.Alpha2) > --------------------------------------------------------------------- > > Key: RF-13458 > URL: https://issues.jboss.org/browse/RF-13458 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Steven W. > Assignee: Pavol Pitonak > > There appear to be compatibility issues with the richfaces-5.0.0.Alpha2 release and the javassist package. Using older versions of the package lead to failures stating that new javassist methods are not available. > When using the newer libraries (3.14 -> javassist-3.18.0-GA) exceptions are generated on the use of previously functioning command links (the corresponding methods are still the same signatures i.e. return String and take no parameters) > {code} > value="#{messages['listByUnit']}" > title="#{messages['titleListByUnit']}" > action="#{appController.selectCurrSelectionUnit}"/> > {code} > with > {code} > public String selectCurrSelectionUnit() > {code} > yields: > {code} > 2014-01-03 13:57:57,597 ERROR [org.jboss.seam.exception.Exceptions] - handled and logged exception > javax.servlet.ServletException: /layout/controller-selections.xhtml: Property 'selectCurrSelectionUnit' not found on type com.integrits.bean.Controller_$$_javassist_seam_2 > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:606) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:374) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) > at java.lang.Thread.run(Thread.java:619) > Caused by: javax.el.ELException: /layout/controller-selections.xhtml: Property 'selectCurrSelectionUnit' not found on type com.integrits.bean.Controller_$$_javassist_seam_2 > at com.sun.faces.facelets.compiler.AttributeInstruction.write(AttributeInstruction.java:94) > at com.sun.faces.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:82) > at com.sun.faces.facelets.compiler.UILeaf.encodeAll(UILeaf.java:207) > at javax.faces.render.Renderer.encodeChildren(Renderer.java:168) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:304) > at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:105) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:304) > at com.sun.faces.renderkit.html_basic.GridRenderer.renderRow(GridRenderer.java:185) > at com.sun.faces.renderkit.html_basic.GridRenderer.encodeChildren(GridRenderer.java:129) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1819) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1822) > at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:447) > at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) > at org.jboss.seam.jsf.SeamViewHandler.renderView(SeamViewHandler.java:188) > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) > ... 33 more > {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 From issues at jboss.org Tue Feb 11 03:05:28 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 11 Feb 2014 03:05:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13458) CommandLink Javassist Compatibility Failures (richfaces-5.0.0.Alpha2) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-13458: ---------------------------------- Assignee: Juraj H?ska (was: Pavol Pitonak) Juraj, please try this reproducer. > CommandLink Javassist Compatibility Failures (richfaces-5.0.0.Alpha2) > --------------------------------------------------------------------- > > Key: RF-13458 > URL: https://issues.jboss.org/browse/RF-13458 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Steven W. > Assignee: Juraj H?ska > > There appear to be compatibility issues with the richfaces-5.0.0.Alpha2 release and the javassist package. Using older versions of the package lead to failures stating that new javassist methods are not available. > When using the newer libraries (3.14 -> javassist-3.18.0-GA) exceptions are generated on the use of previously functioning command links (the corresponding methods are still the same signatures i.e. return String and take no parameters) > {code} > value="#{messages['listByUnit']}" > title="#{messages['titleListByUnit']}" > action="#{appController.selectCurrSelectionUnit}"/> > {code} > with > {code} > public String selectCurrSelectionUnit() > {code} > yields: > {code} > 2014-01-03 13:57:57,597 ERROR [org.jboss.seam.exception.Exceptions] - handled and logged exception > javax.servlet.ServletException: /layout/controller-selections.xhtml: Property 'selectCurrSelectionUnit' not found on type com.integrits.bean.Controller_$$_javassist_seam_2 > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:606) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:374) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) > at java.lang.Thread.run(Thread.java:619) > Caused by: javax.el.ELException: /layout/controller-selections.xhtml: Property 'selectCurrSelectionUnit' not found on type com.integrits.bean.Controller_$$_javassist_seam_2 > at com.sun.faces.facelets.compiler.AttributeInstruction.write(AttributeInstruction.java:94) > at com.sun.faces.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:82) > at com.sun.faces.facelets.compiler.UILeaf.encodeAll(UILeaf.java:207) > at javax.faces.render.Renderer.encodeChildren(Renderer.java:168) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:304) > at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:105) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:304) > at com.sun.faces.renderkit.html_basic.GridRenderer.renderRow(GridRenderer.java:185) > at com.sun.faces.renderkit.html_basic.GridRenderer.encodeChildren(GridRenderer.java:129) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1819) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1822) > at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:447) > at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) > at org.jboss.seam.jsf.SeamViewHandler.renderView(SeamViewHandler.java:188) > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) > ... 33 more > {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 From issues at jboss.org Tue Feb 11 04:39:28 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 11 Feb 2014 04:39:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13534) a4j:mediaOutput on GF4: "Unauthorized deserialisation attempt" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943343#comment-12943343 ] Juraj H?ska commented on RF-13534: ---------------------------------- I *have reproduced* the issues with provided reproducer. It can be reproduced with RichFaces {{4.3.5.Final}}, {{4.3.6-SNAPSHOT}}, {{5.0.0.Alpha3}}. It can be reproduced on Glassfish 4 only. It works on AS 7.1.1.Final and WildFly latest SNAPSHOT. I have tried to put {{org.jboss.weld.util.el.ForwardingMethodExpression}} into serialization white-list, but it *did not* resolved the issue for me. Please tell me if I can do something more. > a4j:mediaOutput on GF4: "Unauthorized deserialisation attempt" > -------------------------------------------------------------- > > Key: RF-13534 > URL: https://issues.jboss.org/browse/RF-13534 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Environment: Glassfish 4.0, Mac OS X 10.9.1, Java(TM) SE Runtime Environment (build 1.7.0_21-b12), Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01, mixed mode) > Reporter: Daniele Benegiamo > Assignee: Juraj H?ska > Attachments: MediaOutput.zip > > > On GF4.0 any attempt to use {{}} raises the same exception ("{{java.io.InvalidClassException: Unauthorized deserialisation attempt}}"). Everything works nicely with the old RichFaces 4.1.0. > Below you can find a stack trace, a sample page and a sample managed bean as minimum reproducible test case. > To keep the test case short, the sample doesn't uses the {{value}} attribute, but exceptions are raised also when using it (e.g. passing a simple {{java.lang.String}}). > From a first quick analysis seems that: > * basic types (as {{java.lang.String}}) are not properly detected as "de-serializable"; > * types implementing {{Serializable}} or {{SerializableResource}} interfaces are impossible to instantiate by {{LookAheadObjectInputStream}} (row 118 - {{Class.forName()}} call in {{isClassValid()}} method - raises a {{ClassNotFoundException}} exception). > {code:title=Exception} > SEVERE: Input error for deserialize data > java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.util.el.ForwardingMethodExpression > at org.richfaces.util.LookAheadObjectInputStream.resolveClass(LookAheadObjectInputStream.java:105) > at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1610) > at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515) > at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1620) > at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1769) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) > at com.sun.faces.facelets.el.TagMethodExpression.readExternal(TagMethodExpression.java:158) > at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1835) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1794) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) > at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1989) > at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1913) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1796) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) > at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1704) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1342) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) > at org.richfaces.util.Util.decodeObjectData(Util.java:237) > at org.richfaces.resource.DefaultCodecResourceRequestData.getData(DefaultCodecResourceRequestData.java:97) > at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:337) > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:156) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:643) > at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1682) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:318) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:160) > at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:734) > at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:673) > at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:99) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:174) > at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:357) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:260) > at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:188) > at org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:191) > at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:168) > at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:189) > at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:288) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:206) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:136) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:114) > at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77) > at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:838) > at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:113) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:115) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access$100(WorkerThreadIOStrategy.java:55) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:135) > at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:564) > at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:544) > at java.lang.Thread.run(Thread.java:722) > WARNING: StandardWrapperValve[Faces Servlet]: Servlet.service() for servlet Faces Servlet threw exception > java.lang.NullPointerException > at org.richfaces.resource.MediaOutputResource.encode(MediaOutputResource.java:62) > at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:188) > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:229) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:643) > at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1682) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:318) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:160) > at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:734) > at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:673) > at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:99) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:174) > at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:357) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:260) > at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:188) > at org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:191) > at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:168) > at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:189) > at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:288) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:206) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:136) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:114) > at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77) > at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:838) > at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:113) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:115) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access$100(WorkerThreadIOStrategy.java:55) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:135) > at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:564) > at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:544) > at java.lang.Thread.run(Thread.java:722) > {code} > {code:xml|title=index.xhtml} > > > xmlns:h="http://xmlns.jcp.org/jsf/html" > xmlns:a4j="http://richfaces.org/a4j"> > > Page title > > > > > > {code} > {code:java|title=MyBean.java} > package org.example; > import java.awt.Color; > import java.awt.Font; > import java.awt.Graphics2D; > import java.awt.image.BufferedImage; > import java.io.IOException; > import javax.enterprise.context.RequestScoped; > import javax.imageio.ImageIO; > import javax.inject.Named; > @Named > @RequestScoped > public class MyBean > { > public void myCreateContent (java.io.OutputStream output, java.lang.Object input) > throws IOException > { > BufferedImage img = new BufferedImage (400, 200, BufferedImage.TYPE_INT_RGB); > Graphics2D graphics2D = img.createGraphics (); > graphics2D.setBackground (Color.BLACK); > graphics2D.setColor (Color.WHITE); > graphics2D.clearRect (0, 0, img.getWidth (), img.getHeight ()); > graphics2D.setFont (new Font ("Arial", Font.PLAIN, 12)); > graphics2D.drawString ("String", 20, 35); > ImageIO.write (img, "png", output); > } > } > {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 From issues at jboss.org Tue Feb 11 04:39:29 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 11 Feb 2014 04:39:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13534) a4j:mediaOutput on GF4: "Unauthorized deserialisation attempt" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13534: ----------------------------- Assignee: (was: Juraj H?ska) > a4j:mediaOutput on GF4: "Unauthorized deserialisation attempt" > -------------------------------------------------------------- > > Key: RF-13534 > URL: https://issues.jboss.org/browse/RF-13534 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Environment: Glassfish 4.0, Mac OS X 10.9.1, Java(TM) SE Runtime Environment (build 1.7.0_21-b12), Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01, mixed mode) > Reporter: Daniele Benegiamo > Attachments: MediaOutput.zip > > > On GF4.0 any attempt to use {{}} raises the same exception ("{{java.io.InvalidClassException: Unauthorized deserialisation attempt}}"). Everything works nicely with the old RichFaces 4.1.0. > Below you can find a stack trace, a sample page and a sample managed bean as minimum reproducible test case. > To keep the test case short, the sample doesn't uses the {{value}} attribute, but exceptions are raised also when using it (e.g. passing a simple {{java.lang.String}}). > From a first quick analysis seems that: > * basic types (as {{java.lang.String}}) are not properly detected as "de-serializable"; > * types implementing {{Serializable}} or {{SerializableResource}} interfaces are impossible to instantiate by {{LookAheadObjectInputStream}} (row 118 - {{Class.forName()}} call in {{isClassValid()}} method - raises a {{ClassNotFoundException}} exception). > {code:title=Exception} > SEVERE: Input error for deserialize data > java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.util.el.ForwardingMethodExpression > at org.richfaces.util.LookAheadObjectInputStream.resolveClass(LookAheadObjectInputStream.java:105) > at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1610) > at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515) > at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1620) > at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1769) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) > at com.sun.faces.facelets.el.TagMethodExpression.readExternal(TagMethodExpression.java:158) > at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1835) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1794) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) > at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1989) > at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1913) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1796) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) > at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1704) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1342) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) > at org.richfaces.util.Util.decodeObjectData(Util.java:237) > at org.richfaces.resource.DefaultCodecResourceRequestData.getData(DefaultCodecResourceRequestData.java:97) > at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:337) > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:156) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:643) > at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1682) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:318) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:160) > at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:734) > at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:673) > at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:99) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:174) > at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:357) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:260) > at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:188) > at org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:191) > at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:168) > at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:189) > at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:288) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:206) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:136) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:114) > at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77) > at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:838) > at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:113) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:115) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access$100(WorkerThreadIOStrategy.java:55) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:135) > at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:564) > at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:544) > at java.lang.Thread.run(Thread.java:722) > WARNING: StandardWrapperValve[Faces Servlet]: Servlet.service() for servlet Faces Servlet threw exception > java.lang.NullPointerException > at org.richfaces.resource.MediaOutputResource.encode(MediaOutputResource.java:62) > at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:188) > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:229) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:643) > at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1682) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:318) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:160) > at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:734) > at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:673) > at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:99) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:174) > at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:357) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:260) > at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:188) > at org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:191) > at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:168) > at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:189) > at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:288) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:206) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:136) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:114) > at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77) > at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:838) > at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:113) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:115) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access$100(WorkerThreadIOStrategy.java:55) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:135) > at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:564) > at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:544) > at java.lang.Thread.run(Thread.java:722) > {code} > {code:xml|title=index.xhtml} > > > xmlns:h="http://xmlns.jcp.org/jsf/html" > xmlns:a4j="http://richfaces.org/a4j"> > > Page title > > > > > > {code} > {code:java|title=MyBean.java} > package org.example; > import java.awt.Color; > import java.awt.Font; > import java.awt.Graphics2D; > import java.awt.image.BufferedImage; > import java.io.IOException; > import javax.enterprise.context.RequestScoped; > import javax.imageio.ImageIO; > import javax.inject.Named; > @Named > @RequestScoped > public class MyBean > { > public void myCreateContent (java.io.OutputStream output, java.lang.Object input) > throws IOException > { > BufferedImage img = new BufferedImage (400, 200, BufferedImage.TYPE_INT_RGB); > Graphics2D graphics2D = img.createGraphics (); > graphics2D.setBackground (Color.BLACK); > graphics2D.setColor (Color.WHITE); > graphics2D.clearRect (0, 0, img.getWidth (), img.getHeight ()); > graphics2D.setFont (new Font ("Arial", Font.PLAIN, 12)); > graphics2D.drawString ("String", 20, 35); > ImageIO.write (img, "png", output); > } > } > {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 From issues at jboss.org Tue Feb 11 05:09:28 2014 From: issues at jboss.org (Juergen Zimmermann (JIRA)) Date: Tue, 11 Feb 2014 05:09:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13538) Closeables.closeQuietly() removed in Guava 16.0, but still used in RF In-Reply-To: References: Message-ID: Juergen Zimmermann created RF-13538: --------------------------------------- Summary: Closeables.closeQuietly() removed in Guava 16.0, but still used in RF Key: RF-13538 URL: https://issues.jboss.org/browse/RF-13538 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 5.0.0.Alpha3 Reporter: Juergen Zimmermann For instance in org.richfaces.resource.Java2DUserResourceWrapperImpl at line 73 is an invocation of Closeables.closeQuietly(...). However, this method is removed in Guava 16.0 which is now used in RF 5.0.0.Alpha3. javadoc of Guava 14.0 already mentioned: "Deprecated. Where possible, use the try-with-resources statement if using JDK7 or Closer on JDK6 to close one or more Closeable objects. This method is deprecated because it is easy to misuse and may swallow IO exceptions that really should be thrown and handled. See Guava issue 1118 for a more detailed explanation of the reasons for deprecation and see Closing Resources for more information on the problems with closing Closeable objects and some of the preferred solutions for handling it correctly. This method is scheduled to be removed in Guava 16.0." Well, now the method is removed, but still invoked in RF 5.0.0.Alpha3. -- 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 From issues at jboss.org Tue Feb 11 05:11:28 2014 From: issues at jboss.org (Juergen Zimmermann (JIRA)) Date: Tue, 11 Feb 2014 05:11:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13539) r:fileUpload doesn't have the attribute fileUploadListener anymore In-Reply-To: References: Message-ID: Juergen Zimmermann created RF-13539: --------------------------------------- Summary: r:fileUpload doesn't have the attribute fileUploadListener anymore Key: RF-13539 URL: https://issues.jboss.org/browse/RF-13539 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 5.0.0.Alpha3 Reporter: Juergen Zimmermann In RF 4.x and 5.0.0.Alpha1 the tag r:fileUpload had an attribute fileUploadListener to provide a listener which received the uploaded byte array. This attribute is gone. How shall one receive the uploaded bytes? -- 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 From issues at jboss.org Tue Feb 11 06:17:28 2014 From: issues at jboss.org (Steve Oh (JIRA)) Date: Tue, 11 Feb 2014 06:17:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13378) extendedDataTable not shown inside Bootstrap tab panel In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12937429#comment-12937429 ] Steve Oh edited comment on RF-13378 at 2/11/14 6:16 AM: -------------------------------------------------------- REMOVED was (Author: cc2000): Hello, I put together a list of JS statements, that seams to fix the layout. But I don't think, this is a stable workaround. {code} var edt = RichFaces.$("#{rich:clientId('theTable')}"); var bodyy = document.getElementById("#{rich:clientId('theTable')}:b"); $(bodyy).height(300); $(edt).triggerHandler('rich:onajaxcomplete', {reinitializeHeader: true}); edt.updateLayout(); {code} > extendedDataTable not shown inside Bootstrap tab panel > ------------------------------------------------------ > > Key: RF-13378 > URL: https://issues.jboss.org/browse/RF-13378 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.4 > Environment: Tested on Ubuntu 12.04, Firefox 25, JDK 7u45, GlassFish 3.1.2.2 > Reporter: Salvo Isaja > Labels: extendedDataTable > Fix For: 5-Tracking > > Attachments: ExtendedDataTableTest.7z > > > As described in RF-12682, when an extendedDataTable is placed in a parent which is not displayed by default, showing the parent causes the table to be invisible. This was reported to be solved on 4.3.2 for tables inside rich:tabPanel, while this issue is on 4.3.4 for tables inside a tab panel from Bootstrap 3. > Attached a minimal project which demonstrates the issue. > Thanks. -- 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 From issues at jboss.org Tue Feb 11 06:17:28 2014 From: issues at jboss.org (Steve Oh (JIRA)) Date: Tue, 11 Feb 2014 06:17:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13378) extendedDataTable not shown inside Bootstrap tab panel In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12936875#comment-12936875 ] Steve Oh edited comment on RF-13378 at 2/11/14 6:16 AM: -------------------------------------------------------- REMOVED was (Author: cc2000): same problem with me (using rich:tabPanel), I am digging into suspected javascript - see this snippet from extendedDataTable.js: {code:javascript} initialize: function() { this.deActivateResizeListener(); if (! $(this.element).is(":visible")) { this.showOffscreen(this.element); } {code} > extendedDataTable not shown inside Bootstrap tab panel > ------------------------------------------------------ > > Key: RF-13378 > URL: https://issues.jboss.org/browse/RF-13378 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.4 > Environment: Tested on Ubuntu 12.04, Firefox 25, JDK 7u45, GlassFish 3.1.2.2 > Reporter: Salvo Isaja > Labels: extendedDataTable > Fix For: 5-Tracking > > Attachments: ExtendedDataTableTest.7z > > > As described in RF-12682, when an extendedDataTable is placed in a parent which is not displayed by default, showing the parent causes the table to be invisible. This was reported to be solved on 4.3.2 for tables inside rich:tabPanel, while this issue is on 4.3.4 for tables inside a tab panel from Bootstrap 3. > Attached a minimal project which demonstrates the issue. > Thanks. -- 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 From issues at jboss.org Tue Feb 11 06:55:29 2014 From: issues at jboss.org (Immo Benjes (JIRA)) Date: Tue, 11 Feb 2014 06:55:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13251) FocusManager to support complex components like rich:autocomplete In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943378#comment-12943378 ] Immo Benjes commented on RF-13251: ---------------------------------- Hi Luk??, sorry I am quite busy at the moment but it is really easy to reproduce. Just have a rich:autocomplete and an ajax button. The ajax button submits and rerenders the form. The action method on the a:commandButton tries to set the focus on the rich:autocomplete with the FocusManager - done. You probably have a 'test' autocomplete component flying around anyway. > FocusManager to support complex components like rich:autocomplete > ----------------------------------------------------------------- > > Key: RF-13251 > URL: https://issues.jboss.org/browse/RF-13251 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Assignee: Luk?? Fry? > Priority: Minor > Labels: waiting_on_user > > Currently the FocusManager in Richfaces only works on 'simple' UI components like h:inputText or h:selectOneMenu but not on more complex components like rich:autocomplete. > It would be good if FocusManager could support complex components or 'real' Ids as generated for that page. > The use case for the support on autocomplete is like this: > User has to enter multiple 'entities'. A rich:autocomplete is used to select the entity and add it to a list. After each ajax submit the focus gets lost and the user has to manually set the focus back to the autocomplete input field. -- 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 From issues at jboss.org Tue Feb 11 07:27:28 2014 From: issues at jboss.org (Sebastian Cramer (JIRA)) Date: Tue, 11 Feb 2014 07:27:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12801) Use of Resource Optimization prevents the WebBeansELResolver from registering in OWB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943394#comment-12943394 ] Sebastian Cramer commented on RF-12801: --------------------------------------- The workaround by [~mayerle] works (just triggers a different bug - refer to the forum thread for info). Since this issue seems to be a OWB bug I would suggest closing it (for now). > Use of Resource Optimization prevents the WebBeansELResolver from registering in OWB > ------------------------------------------------------------------------------------ > > Key: RF-12801 > URL: https://issues.jboss.org/browse/RF-12801 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.3.0.Final > Environment: Websphere 8.0.0.3 and Websphere 8.0.0.5, Windows 7, Richfaces 4.3.0.Final > Reporter: Erdem YILMAZ > Labels: ELResolver, optimization, owb, resource, websphere > Fix For: 5-Tracking > > > when we use context param org.richfaces.resourceOptimization.enabled in web.xml, the CDI listener is not registered in Websphere. > resourcesOptimization parameter disables org.apache.webbeans.el.WebBeansELResolver in Websphere. In richfaces 4.2.3.Final version, resourceOptimization parameter do not affect the CDI behaviour. > we have disabled the resource optimization in order to work with richfaces but for the production environment, we prefer to enable it. -- 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 From issues at jboss.org Tue Feb 11 07:59:29 2014 From: issues at jboss.org (Sebastian Cramer (JIRA)) Date: Tue, 11 Feb 2014 07:59:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13540) Websphere incarnation of MyFaces renderes optimized resources multiple times In-Reply-To: References: Message-ID: Sebastian Cramer created RF-13540: ------------------------------------- Summary: Websphere incarnation of MyFaces renderes optimized resources multiple times Key: RF-13540 URL: https://issues.jboss.org/browse/RF-13540 Project: RichFaces Issue Type: Patch Security Level: Public (Everyone can see) Components: compatibility Affects Versions: 5.0.0.Alpha3, 4.3.5 Environment: Myfaces/Websphere on all platforms Reporter: Sebastian Cramer When enabling resource optimization the packed.js (and packed.css) are rendered multiple times. The previous fix for stock myfaces is not effective against IBM's myfaces impl. -- 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 From issues at jboss.org Tue Feb 11 08:03:28 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 11 Feb 2014 08:03:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13531) selects: cannot select option on IE11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak updated RF-13531: ------------------------------- Labels: IE11 (was: IE11 needs-qe) > selects: cannot select option on IE11 > ------------------------------------- > > Key: RF-13531 > URL: https://issues.jboss.org/browse/RF-13531 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.3.5, 4.5.0.Alpha2, 5.0.0.Alpha3 > Environment: IE 11 > Reporter: Ji?? ?tefek > Assignee: Brian Leathem > Labels: IE11 > Fix For: 4.3.6 > > > Components: autocomplete, select, inplaceSelect. > Works on IE 10. > ---- > Issues: > * User cannot visually select an option from the popup list == moving mouse over the items in the list will not change theirs class. > ** however clicking on the item will select the option correctly. {color:red}EXCEPT autocomplete (RF4), where it will not select anything{color}. > ** workaround: the item can be selected, when moving off the list and back to it on the correct item, but the cursor should not move through scroller. > * User cannot select option with keyboard. -- 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 From issues at jboss.org Tue Feb 11 08:25:29 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 11 Feb 2014 08:25:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13251) FocusManager to support complex components like rich:autocomplete In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-13251: ---------------------------- Labels: (was: waiting_on_user) > FocusManager to support complex components like rich:autocomplete > ----------------------------------------------------------------- > > Key: RF-13251 > URL: https://issues.jboss.org/browse/RF-13251 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Assignee: Luk?? Fry? > Priority: Minor > > Currently the FocusManager in Richfaces only works on 'simple' UI components like h:inputText or h:selectOneMenu but not on more complex components like rich:autocomplete. > It would be good if FocusManager could support complex components or 'real' Ids as generated for that page. > The use case for the support on autocomplete is like this: > User has to enter multiple 'entities'. A rich:autocomplete is used to select the entity and add it to a list. After each ajax submit the focus gets lost and the user has to manually set the focus back to the autocomplete input field. -- 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 From issues at jboss.org Tue Feb 11 09:03:29 2014 From: issues at jboss.org (Erdem YILMAZ (JIRA)) Date: Tue, 11 Feb 2014 09:03:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12801) Use of Resource Optimization prevents the WebBeansELResolver from registering in OWB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erdem YILMAZ closed RF-12801. ----------------------------- Resolution: Partially Completed it seems an OWB bug > Use of Resource Optimization prevents the WebBeansELResolver from registering in OWB > ------------------------------------------------------------------------------------ > > Key: RF-12801 > URL: https://issues.jboss.org/browse/RF-12801 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.3.0.Final > Environment: Websphere 8.0.0.3 and Websphere 8.0.0.5, Windows 7, Richfaces 4.3.0.Final > Reporter: Erdem YILMAZ > Labels: ELResolver, optimization, owb, resource, websphere > Fix For: 5-Tracking > > > when we use context param org.richfaces.resourceOptimization.enabled in web.xml, the CDI listener is not registered in Websphere. > resourcesOptimization parameter disables org.apache.webbeans.el.WebBeansELResolver in Websphere. In richfaces 4.2.3.Final version, resourceOptimization parameter do not affect the CDI behaviour. > we have disabled the resource optimization in order to work with richfaces but for the production environment, we prefer to enable it. -- 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 From issues at jboss.org Tue Feb 11 11:15:29 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 11 Feb 2014 11:15:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13541) Photoalbum - JPA tests In-Reply-To: References: Message-ID: Michal Petrov created RF-13541: ---------------------------------- Summary: Photoalbum - JPA tests Key: RF-13541 URL: https://issues.jboss.org/browse/RF-13541 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.5.0.Alpha1 Reporter: Michal Petrov In the photoalbum POM there's a profile for running some Arquillian tests. (Basic CRUD) It's not currently runnable (outdated dependencies and/or settings). Most of the tests are missing some dependencies but {{UserManagementTest}} and {{UserBeanTest}} seem to require a large number of class dependencies to run. -- 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 From issues at jboss.org Tue Feb 11 11:19:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 11 Feb 2014 11:19:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13542) RichFaces 5 uses Bootstrap as it's base styling/theme approach. This epic will encompass issues relating to the skinning/theming of the framework. In-Reply-To: References: Message-ID: Brian Leathem created RF-13542: ---------------------------------- Summary: RichFaces 5 uses Bootstrap as it's base styling/theme approach. This epic will encompass issues relating to the skinning/theming of the framework. Key: RF-13542 URL: https://issues.jboss.org/browse/RF-13542 Project: RichFaces Issue Type: Epic Security Level: Public (Everyone can see) Reporter: Brian Leathem -- 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 From issues at jboss.org Tue Feb 11 11:21:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 11 Feb 2014 11:21:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13542) RichFaces 5 uses Bootstrap as it's base styling/theme approach. This epic will encompass issues relating to the skinning/theming of the framework. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13542: ------------------------------- Description: RichFaces 5 uses Bootstrap as it's base styling/theme approach. This epic will encompass issues relating to the skinning/theming of the framework. > RichFaces 5 uses Bootstrap as it's base styling/theme approach. This epic will encompass issues relating to the skinning/theming of the framework. > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-13542 > URL: https://issues.jboss.org/browse/RF-13542 > Project: RichFaces > Issue Type: Epic > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > > RichFaces 5 uses Bootstrap as it's base styling/theme approach. This epic will encompass issues relating to the skinning/theming of the framework. -- 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 From issues at jboss.org Tue Feb 11 11:21:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 11 Feb 2014 11:21:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13542) RichFaces 5 styling/theme capabilities In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13542: ------------------------------- Summary: RichFaces 5 styling/theme capabilities (was: RichFaces 5 uses Bootstrap as it's base styling/theme approach. This epic will encompass issues relating to the skinning/theming of the framework.) > RichFaces 5 styling/theme capabilities > -------------------------------------- > > Key: RF-13542 > URL: https://issues.jboss.org/browse/RF-13542 > Project: RichFaces > Issue Type: Epic > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > > RichFaces 5 uses Bootstrap as it's base styling/theme approach. This epic will encompass issues relating to the skinning/theming of the framework. -- 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 From issues at jboss.org Tue Feb 11 11:21:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 11 Feb 2014 11:21:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13542) RichFaces 5 styling/theme capabilities In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13542: ------------------------------- Fix Version/s: 5-Tracking > RichFaces 5 styling/theme capabilities > -------------------------------------- > > Key: RF-13542 > URL: https://issues.jboss.org/browse/RF-13542 > Project: RichFaces > Issue Type: Epic > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Fix For: 5-Tracking > > > RichFaces 5 uses Bootstrap as it's base styling/theme approach. This epic will encompass issues relating to the skinning/theming of the framework. -- 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 From issues at jboss.org Tue Feb 11 13:11:28 2014 From: issues at jboss.org (Cody Lerum (JIRA)) Date: Tue, 11 Feb 2014 13:11:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13538) Closeables.closeQuietly() removed in Guava 16.0, but still used in RF In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943567#comment-12943567 ] Cody Lerum commented on RF-13538: --------------------------------- This was always an @Beta feature (http://docs.guava-libraries.googlecode.com/git-history/v13.0.1/javadoc/index.html) and probably shouldn't have been depended on. > Closeables.closeQuietly() removed in Guava 16.0, but still used in RF > --------------------------------------------------------------------- > > Key: RF-13538 > URL: https://issues.jboss.org/browse/RF-13538 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha3 > Reporter: Juergen Zimmermann > > For instance in org.richfaces.resource.Java2DUserResourceWrapperImpl at line 73 is an invocation of Closeables.closeQuietly(...). However, this method is removed in Guava 16.0 which is now used in RF 5.0.0.Alpha3. > javadoc of Guava 14.0 already mentioned: > "Deprecated. Where possible, use the try-with-resources statement if using JDK7 or Closer on JDK6 to close one or more Closeable objects. This method is deprecated because it is easy to misuse and may swallow IO exceptions that really should be thrown and handled. See Guava issue 1118 for a more detailed explanation of the reasons for deprecation and see Closing Resources for more information on the problems with closing Closeable objects and some of the preferred solutions for handling it correctly. This method is scheduled to be removed in Guava 16.0." > Well, now the method is removed, but still invoked in RF 5.0.0.Alpha3. -- 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 From issues at jboss.org Tue Feb 11 13:55:29 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 11 Feb 2014 13:55:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13534) a4j:mediaOutput on GF4: "Unauthorized deserialisation attempt" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13534: ------------------------------- Fix Version/s: 5-Tracking > a4j:mediaOutput on GF4: "Unauthorized deserialisation attempt" > -------------------------------------------------------------- > > Key: RF-13534 > URL: https://issues.jboss.org/browse/RF-13534 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Environment: Glassfish 4.0, Mac OS X 10.9.1, Java(TM) SE Runtime Environment (build 1.7.0_21-b12), Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01, mixed mode) > Reporter: Daniele Benegiamo > Fix For: 5-Tracking > > Attachments: MediaOutput.zip > > > On GF4.0 any attempt to use {{}} raises the same exception ("{{java.io.InvalidClassException: Unauthorized deserialisation attempt}}"). Everything works nicely with the old RichFaces 4.1.0. > Below you can find a stack trace, a sample page and a sample managed bean as minimum reproducible test case. > To keep the test case short, the sample doesn't uses the {{value}} attribute, but exceptions are raised also when using it (e.g. passing a simple {{java.lang.String}}). > From a first quick analysis seems that: > * basic types (as {{java.lang.String}}) are not properly detected as "de-serializable"; > * types implementing {{Serializable}} or {{SerializableResource}} interfaces are impossible to instantiate by {{LookAheadObjectInputStream}} (row 118 - {{Class.forName()}} call in {{isClassValid()}} method - raises a {{ClassNotFoundException}} exception). > {code:title=Exception} > SEVERE: Input error for deserialize data > java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.util.el.ForwardingMethodExpression > at org.richfaces.util.LookAheadObjectInputStream.resolveClass(LookAheadObjectInputStream.java:105) > at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1610) > at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515) > at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1620) > at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1769) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) > at com.sun.faces.facelets.el.TagMethodExpression.readExternal(TagMethodExpression.java:158) > at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1835) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1794) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) > at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1989) > at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1913) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1796) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) > at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1704) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1342) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) > at org.richfaces.util.Util.decodeObjectData(Util.java:237) > at org.richfaces.resource.DefaultCodecResourceRequestData.getData(DefaultCodecResourceRequestData.java:97) > at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:337) > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:156) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:643) > at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1682) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:318) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:160) > at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:734) > at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:673) > at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:99) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:174) > at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:357) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:260) > at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:188) > at org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:191) > at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:168) > at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:189) > at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:288) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:206) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:136) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:114) > at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77) > at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:838) > at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:113) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:115) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access$100(WorkerThreadIOStrategy.java:55) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:135) > at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:564) > at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:544) > at java.lang.Thread.run(Thread.java:722) > WARNING: StandardWrapperValve[Faces Servlet]: Servlet.service() for servlet Faces Servlet threw exception > java.lang.NullPointerException > at org.richfaces.resource.MediaOutputResource.encode(MediaOutputResource.java:62) > at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:188) > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:229) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:643) > at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1682) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:318) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:160) > at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:734) > at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:673) > at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:99) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:174) > at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:357) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:260) > at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:188) > at org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:191) > at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:168) > at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:189) > at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:288) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:206) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:136) > at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:114) > at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77) > at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:838) > at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:113) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:115) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access$100(WorkerThreadIOStrategy.java:55) > at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:135) > at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:564) > at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:544) > at java.lang.Thread.run(Thread.java:722) > {code} > {code:xml|title=index.xhtml} > > > xmlns:h="http://xmlns.jcp.org/jsf/html" > xmlns:a4j="http://richfaces.org/a4j"> > > Page title > > > > > > {code} > {code:java|title=MyBean.java} > package org.example; > import java.awt.Color; > import java.awt.Font; > import java.awt.Graphics2D; > import java.awt.image.BufferedImage; > import java.io.IOException; > import javax.enterprise.context.RequestScoped; > import javax.imageio.ImageIO; > import javax.inject.Named; > @Named > @RequestScoped > public class MyBean > { > public void myCreateContent (java.io.OutputStream output, java.lang.Object input) > throws IOException > { > BufferedImage img = new BufferedImage (400, 200, BufferedImage.TYPE_INT_RGB); > Graphics2D graphics2D = img.createGraphics (); > graphics2D.setBackground (Color.BLACK); > graphics2D.setColor (Color.WHITE); > graphics2D.clearRect (0, 0, img.getWidth (), img.getHeight ()); > graphics2D.setFont (new Font ("Arial", Font.PLAIN, 12)); > graphics2D.drawString ("String", 20, 35); > ImageIO.write (img, "png", output); > } > } > {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 From issues at jboss.org Tue Feb 11 13:57:29 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 11 Feb 2014 13:57:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13247) Upgrade the RichFaces guava dependency to the latest version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13247: ------------------------------- Summary: Upgrade the RichFaces guava dependency to the latest version (was: Upgrade the RichFaces guava dependency to version 15.0) > Upgrade the RichFaces guava dependency to the latest version > ------------------------------------------------------------ > > 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 > Assignee: Brian Leathem > Priority: Minor > Fix For: 5.0.0.Alpha4 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > 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 From issues at jboss.org Tue Feb 11 13:57:29 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 11 Feb 2014 13:57:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13538) Closeables.closeQuietly() removed in Guava 16.0, but still used in RF In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13538: ------------------------------- Fix Version/s: 5.0.0.Alpha4 > Closeables.closeQuietly() removed in Guava 16.0, but still used in RF > --------------------------------------------------------------------- > > Key: RF-13538 > URL: https://issues.jboss.org/browse/RF-13538 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha3 > Reporter: Juergen Zimmermann > Fix For: 5.0.0.Alpha4 > > > For instance in org.richfaces.resource.Java2DUserResourceWrapperImpl at line 73 is an invocation of Closeables.closeQuietly(...). However, this method is removed in Guava 16.0 which is now used in RF 5.0.0.Alpha3. > javadoc of Guava 14.0 already mentioned: > "Deprecated. Where possible, use the try-with-resources statement if using JDK7 or Closer on JDK6 to close one or more Closeable objects. This method is deprecated because it is easy to misuse and may swallow IO exceptions that really should be thrown and handled. See Guava issue 1118 for a more detailed explanation of the reasons for deprecation and see Closing Resources for more information on the problems with closing Closeable objects and some of the preferred solutions for handling it correctly. This method is scheduled to be removed in Guava 16.0." > Well, now the method is removed, but still invoked in RF 5.0.0.Alpha3. -- 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 From issues at jboss.org Tue Feb 11 14:03:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 11 Feb 2014 14:03:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13539) r:fileUpload doesn't have the attribute fileUploadListener anymore In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943589#comment-12943589 ] Brian Leathem commented on RF-13539: ------------------------------------ I understand this feature was temporarily disabled with RF-13444 in 5.0.0.Alpha3 to enable JSF 2.2 compatibility. We are aiming to restorer the functionality with a re-work of the fileUpload component in 5.0.0.Alpha4 with RF-13514. [~lfryc] please correct me if am wrong. Should we consider this a duplicate issue? > r:fileUpload doesn't have the attribute fileUploadListener anymore > ------------------------------------------------------------------ > > Key: RF-13539 > URL: https://issues.jboss.org/browse/RF-13539 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha3 > Reporter: Juergen Zimmermann > > In RF 4.x and 5.0.0.Alpha1 the tag r:fileUpload had an attribute fileUploadListener to provide a listener which received the uploaded byte array. This attribute is gone. How shall one receive the uploaded bytes? -- 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 From issues at jboss.org Tue Feb 11 14:09:29 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 11 Feb 2014 14:09:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13539) r:fileUpload doesn't have the attribute fileUploadListener anymore In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943589#comment-12943589 ] Brian Leathem edited comment on RF-13539 at 2/11/14 2:09 PM: ------------------------------------------------------------- I understand this feature was temporarily disabled with RF-13444 in 5.0.0.Alpha3 to enable JSF 2.2 compatibility. We are aiming to restore the functionality with a re-work of the fileUpload component in 5.0.0.Alpha4 with RF-13514. [~lfryc] please correct me if am wrong. Should we consider this a duplicate issue? was (Author: bleathem): I understand this feature was temporarily disabled with RF-13444 in 5.0.0.Alpha3 to enable JSF 2.2 compatibility. We are aiming to restorer the functionality with a re-work of the fileUpload component in 5.0.0.Alpha4 with RF-13514. [~lfryc] please correct me if am wrong. Should we consider this a duplicate issue? > r:fileUpload doesn't have the attribute fileUploadListener anymore > ------------------------------------------------------------------ > > Key: RF-13539 > URL: https://issues.jboss.org/browse/RF-13539 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha3 > Reporter: Juergen Zimmermann > > In RF 4.x and 5.0.0.Alpha1 the tag r:fileUpload had an attribute fileUploadListener to provide a listener which received the uploaded byte array. This attribute is gone. How shall one receive the uploaded bytes? -- 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 From issues at jboss.org Tue Feb 11 16:13:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 11 Feb 2014 16:13:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13541) Photoalbum - JPA tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943642#comment-12943642 ] Brian Leathem commented on RF-13541: ------------------------------------ If it helps, take a look at the JPA test in the kitchensink-rf quickstart and see how the dependencies are managed there: https://github.com/richfaces/jdf-quickstarts/blob/master/kitchensink-rf/src/test/java/org/jboss/as/quickstarts/kitchensinkrf/test/MemberRegistrationTest.java > Photoalbum - JPA tests > ---------------------- > > Key: RF-13541 > URL: https://issues.jboss.org/browse/RF-13541 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha1 > Reporter: Michal Petrov > > In the photoalbum POM there's a profile for running some Arquillian tests. (Basic CRUD) > It's not currently runnable (outdated dependencies and/or settings). > Most of the tests are missing some dependencies but {{UserManagementTest}} and {{UserBeanTest}} seem to require a large number of class dependencies to run. -- 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 From issues at jboss.org Tue Feb 11 16:41:29 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 11 Feb 2014 16:41:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13540) Websphere incarnation of MyFaces renderes optimized resources multiple times In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943648#comment-12943648 ] Luk?? Fry? commented on RF-13540: --------------------------------- Hey [~sebcramer], could you please also sign a [Contibutor License Agreement|https://cla.jboss.org/index.seam]? > Websphere incarnation of MyFaces renderes optimized resources multiple times > ---------------------------------------------------------------------------- > > Key: RF-13540 > URL: https://issues.jboss.org/browse/RF-13540 > Project: RichFaces > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.3.5, 5.0.0.Alpha3 > Environment: Myfaces/Websphere on all platforms > Reporter: Sebastian Cramer > Labels: myfaces, websphere > Fix For: 4.3.6 > > > When enabling resource optimization the packed.js (and packed.css) are rendered multiple times. The previous fix for stock myfaces is not effective against IBM's myfaces impl. -- 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 From issues at jboss.org Tue Feb 11 17:47:28 2014 From: issues at jboss.org (Kaveh A. (JIRA)) Date: Tue, 11 Feb 2014 17:47:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12682) extendedDataTable render issue with rich:tabPanel In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943663#comment-12943663 ] Kaveh A. commented on RF-12682: ------------------------------- Yes this issue seems to be back, commenting out the following line in the extendedDataTable.js and packed.js seems to fix it. this.normalPartStyle.display = "none"; > extendedDataTable render issue with rich:tabPanel > ------------------------------------------------- > > Key: RF-12682 > URL: https://issues.jboss.org/browse/RF-12682 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.3.Final, 4.3.0.M3, 4.3.0.CR1, 4.3.0.Final > Reporter: Kaveh A. > Labels: extendedDataTable, render, richfaces, tabpanel, testcase_provided > Attachments: richfacesBug2.zip, RichFacesBugEclipseProject.zip > > > This issue is not just specific to tabPanel. Anytime the extendedDataTable is hidden (when the page loads) and then it is made visible later the table can not display the data (table is empty at the load time). > In this particular case if we load a page with two tabs. Furthermore if we have one extendedDataTable in each tab (the first tab shows and the second tab is not shown at first). In this case once the user clicks on the second tab and tries to populate the extendedDataTable (via any action). Then the table is not rendered properly. A sample project has been provided at the following link that further describe this issue. You can download the eclipse project attached at the end of the following message to reproduce this issue. > https://community.jboss.org/message/783787 -- 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 From issues at jboss.org Tue Feb 11 18:27:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 11 Feb 2014 18:27:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13531) selects: cannot select option on IE11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13531. -------------------------------- Labels: IE11 needs-qe (was: IE11) Resolution: Done Fixed autocomplete as well. > selects: cannot select option on IE11 > ------------------------------------- > > Key: RF-13531 > URL: https://issues.jboss.org/browse/RF-13531 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.3.5, 4.5.0.Alpha2, 5.0.0.Alpha3 > Environment: IE 11 > Reporter: Ji?? ?tefek > Assignee: Brian Leathem > Labels: IE11, needs-qe > Fix For: 4.3.6 > > > Components: autocomplete, select, inplaceSelect. > Works on IE 10. > ---- > Issues: > * User cannot visually select an option from the popup list == moving mouse over the items in the list will not change theirs class. > ** however clicking on the item will select the option correctly. {color:red}EXCEPT autocomplete (RF4), where it will not select anything{color}. > ** workaround: the item can be selected, when moving off the list and back to it on the correct item, but the cursor should not move through scroller. > * User cannot select option with keyboard. -- 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 From issues at jboss.org Tue Feb 11 18:59:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 11 Feb 2014 18:59:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13540) Websphere incarnation of MyFaces renderes optimized resources multiple times In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943731#comment-12943731 ] Brian Leathem commented on RF-13540: ------------------------------------ Note: I have approved [~sebcramer]'s CLA request. > Websphere incarnation of MyFaces renderes optimized resources multiple times > ---------------------------------------------------------------------------- > > Key: RF-13540 > URL: https://issues.jboss.org/browse/RF-13540 > Project: RichFaces > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.3.5, 5.0.0.Alpha3 > Environment: Myfaces/Websphere on all platforms > Reporter: Sebastian Cramer > Labels: myfaces, websphere > Fix For: 4.3.6 > > > When enabling resource optimization the packed.js (and packed.css) are rendered multiple times. The previous fix for stock myfaces is not effective against IBM's myfaces impl. -- 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 From issues at jboss.org Wed Feb 12 02:43:29 2014 From: issues at jboss.org (Sebastian Cramer (JIRA)) Date: Wed, 12 Feb 2014 02:43:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13540) Websphere incarnation of MyFaces renderes optimized resources multiple times In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943777#comment-12943777 ] Sebastian Cramer commented on RF-13540: --------------------------------------- Hey [~lfryc]. Should I port this fix to the RF5 tree? If so I would send you a pull request asap. > Websphere incarnation of MyFaces renderes optimized resources multiple times > ---------------------------------------------------------------------------- > > Key: RF-13540 > URL: https://issues.jboss.org/browse/RF-13540 > Project: RichFaces > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.3.5, 5.0.0.Alpha3 > Environment: Myfaces/Websphere on all platforms > Reporter: Sebastian Cramer > Labels: myfaces, websphere > Fix For: 4.3.6 > > > When enabling resource optimization the packed.js (and packed.css) are rendered multiple times. The previous fix for stock myfaces is not effective against IBM's myfaces impl. -- 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 From issues at jboss.org Wed Feb 12 04:21:28 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 12 Feb 2014 04:21:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13531) selects: cannot select option on IE11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13531: ----------------------------- Labels: IE11 (was: IE11 needs-qe) > selects: cannot select option on IE11 > ------------------------------------- > > Key: RF-13531 > URL: https://issues.jboss.org/browse/RF-13531 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.3.5, 4.5.0.Alpha2, 5.0.0.Alpha3 > Environment: IE 11 > Reporter: Ji?? ?tefek > Assignee: Brian Leathem > Labels: IE11 > Fix For: 4.3.6 > > > Components: autocomplete, select, inplaceSelect. > Works on IE 10. > ---- > Issues: > * User cannot visually select an option from the popup list == moving mouse over the items in the list will not change theirs class. > ** however clicking on the item will select the option correctly. {color:red}EXCEPT autocomplete (RF4), where it will not select anything{color}. > ** workaround: the item can be selected, when moving off the list and back to it on the correct item, but the cursor should not move through scroller. > * User cannot select option with keyboard. -- 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 From issues at jboss.org Wed Feb 12 04:47:28 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 12 Feb 2014 04:47:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13531) selects: cannot select option on IE11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943815#comment-12943815 ] Ji?? ?tefek commented on RF-13531: ---------------------------------- Verified. Selection of items by mouse in components: autocomplete, inplaceSelect, select, pickList and orderingList are OK now on IE 11. Also verified that these components are working with IE 9, IE 10, FF 26 and Chrome 32. [~bleathem] what about the selection by keyboard? > selects: cannot select option on IE11 > ------------------------------------- > > Key: RF-13531 > URL: https://issues.jboss.org/browse/RF-13531 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.3.5, 4.5.0.Alpha2, 5.0.0.Alpha3 > Environment: IE 11 > Reporter: Ji?? ?tefek > Assignee: Brian Leathem > Labels: IE11 > Fix For: 4.3.6 > > > Components: autocomplete, select, inplaceSelect. > Works on IE 10. > ---- > Issues: > * User cannot visually select an option from the popup list == moving mouse over the items in the list will not change theirs class. > ** however clicking on the item will select the option correctly. {color:red}EXCEPT autocomplete (RF4), where it will not select anything{color}. > ** workaround: the item can be selected, when moving off the list and back to it on the correct item, but the cursor should not move through scroller. > * User cannot select option with keyboard. -- 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 From issues at jboss.org Wed Feb 12 05:09:29 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 12 Feb 2014 05:09:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12682) extendedDataTable render issue with rich:tabPanel In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943819#comment-12943819 ] Pavol Pitonak commented on RF-12682: ------------------------------------ [~kaveh_a], could you please create a new issue and add link to this one? > extendedDataTable render issue with rich:tabPanel > ------------------------------------------------- > > Key: RF-12682 > URL: https://issues.jboss.org/browse/RF-12682 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.3.Final, 4.3.0.M3, 4.3.0.CR1, 4.3.0.Final > Reporter: Kaveh A. > Labels: extendedDataTable, render, richfaces, tabpanel, testcase_provided > Attachments: richfacesBug2.zip, RichFacesBugEclipseProject.zip > > > This issue is not just specific to tabPanel. Anytime the extendedDataTable is hidden (when the page loads) and then it is made visible later the table can not display the data (table is empty at the load time). > In this particular case if we load a page with two tabs. Furthermore if we have one extendedDataTable in each tab (the first tab shows and the second tab is not shown at first). In this case once the user clicks on the second tab and tries to populate the extendedDataTable (via any action). Then the table is not rendered properly. A sample project has been provided at the following link that further describe this issue. You can download the eclipse project attached at the end of the following message to reproduce this issue. > https://community.jboss.org/message/783787 -- 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 From issues at jboss.org Wed Feb 12 05:13:28 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 12 Feb 2014 05:13:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13458) CommandLink Javassist Compatibility Failures (richfaces-5.0.0.Alpha2) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943822#comment-12943822 ] Juraj H?ska commented on RF-13458: ---------------------------------- I believe this is not a bug and the behavior is caused by using of old {{rich:}} namespace, instead of {{r:}} introduced in {{5.Alpha2}}. When I refactored the reproducer {{.war}} so it contains only {{r:}} namespace, the issue is not occurring. Please find the refactored .war in the attachments. However, I needed to comment {{ CommandLink Javassist Compatibility Failures (richfaces-5.0.0.Alpha2) > --------------------------------------------------------------------- > > Key: RF-13458 > URL: https://issues.jboss.org/browse/RF-13458 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Steven W. > Assignee: Juraj H?ska > > There appear to be compatibility issues with the richfaces-5.0.0.Alpha2 release and the javassist package. Using older versions of the package lead to failures stating that new javassist methods are not available. > When using the newer libraries (3.14 -> javassist-3.18.0-GA) exceptions are generated on the use of previously functioning command links (the corresponding methods are still the same signatures i.e. return String and take no parameters) > {code} > value="#{messages['listByUnit']}" > title="#{messages['titleListByUnit']}" > action="#{appController.selectCurrSelectionUnit}"/> > {code} > with > {code} > public String selectCurrSelectionUnit() > {code} > yields: > {code} > 2014-01-03 13:57:57,597 ERROR [org.jboss.seam.exception.Exceptions] - handled and logged exception > javax.servlet.ServletException: /layout/controller-selections.xhtml: Property 'selectCurrSelectionUnit' not found on type com.integrits.bean.Controller_$$_javassist_seam_2 > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:606) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:374) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) > at java.lang.Thread.run(Thread.java:619) > Caused by: javax.el.ELException: /layout/controller-selections.xhtml: Property 'selectCurrSelectionUnit' not found on type com.integrits.bean.Controller_$$_javassist_seam_2 > at com.sun.faces.facelets.compiler.AttributeInstruction.write(AttributeInstruction.java:94) > at com.sun.faces.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:82) > at com.sun.faces.facelets.compiler.UILeaf.encodeAll(UILeaf.java:207) > at javax.faces.render.Renderer.encodeChildren(Renderer.java:168) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:304) > at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:105) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:304) > at com.sun.faces.renderkit.html_basic.GridRenderer.renderRow(GridRenderer.java:185) > at com.sun.faces.renderkit.html_basic.GridRenderer.encodeChildren(GridRenderer.java:129) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1819) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1822) > at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:447) > at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) > at org.jboss.seam.jsf.SeamViewHandler.renderView(SeamViewHandler.java:188) > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) > ... 33 more > {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 From issues at jboss.org Wed Feb 12 05:15:30 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 12 Feb 2014 05:15:30 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13458) CommandLink Javassist Compatibility Failures (richfaces-5.0.0.Alpha2) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13458: ----------------------------- Attachment: ExampleRefactoredRichNamespace.war > CommandLink Javassist Compatibility Failures (richfaces-5.0.0.Alpha2) > --------------------------------------------------------------------- > > Key: RF-13458 > URL: https://issues.jboss.org/browse/RF-13458 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Steven W. > Assignee: Juraj H?ska > Attachments: ExampleRefactoredRichNamespace.war > > > There appear to be compatibility issues with the richfaces-5.0.0.Alpha2 release and the javassist package. Using older versions of the package lead to failures stating that new javassist methods are not available. > When using the newer libraries (3.14 -> javassist-3.18.0-GA) exceptions are generated on the use of previously functioning command links (the corresponding methods are still the same signatures i.e. return String and take no parameters) > {code} > value="#{messages['listByUnit']}" > title="#{messages['titleListByUnit']}" > action="#{appController.selectCurrSelectionUnit}"/> > {code} > with > {code} > public String selectCurrSelectionUnit() > {code} > yields: > {code} > 2014-01-03 13:57:57,597 ERROR [org.jboss.seam.exception.Exceptions] - handled and logged exception > javax.servlet.ServletException: /layout/controller-selections.xhtml: Property 'selectCurrSelectionUnit' not found on type com.integrits.bean.Controller_$$_javassist_seam_2 > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:606) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:374) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) > at java.lang.Thread.run(Thread.java:619) > Caused by: javax.el.ELException: /layout/controller-selections.xhtml: Property 'selectCurrSelectionUnit' not found on type com.integrits.bean.Controller_$$_javassist_seam_2 > at com.sun.faces.facelets.compiler.AttributeInstruction.write(AttributeInstruction.java:94) > at com.sun.faces.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:82) > at com.sun.faces.facelets.compiler.UILeaf.encodeAll(UILeaf.java:207) > at javax.faces.render.Renderer.encodeChildren(Renderer.java:168) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:304) > at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:105) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:304) > at com.sun.faces.renderkit.html_basic.GridRenderer.renderRow(GridRenderer.java:185) > at com.sun.faces.renderkit.html_basic.GridRenderer.encodeChildren(GridRenderer.java:129) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1819) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1822) > at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:447) > at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) > at org.jboss.seam.jsf.SeamViewHandler.renderView(SeamViewHandler.java:188) > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) > ... 33 more > {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 From issues at jboss.org Wed Feb 12 05:15:30 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 12 Feb 2014 05:15:30 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13458) CommandLink Javassist Compatibility Failures (richfaces-5.0.0.Alpha2) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943822#comment-12943822 ] Juraj H?ska edited comment on RF-13458 at 2/12/14 5:15 AM: ----------------------------------------------------------- I believe this is not a bug and the behavior is caused by using of old {{rich:}} namespace, instead of {{r:}} introduced in {{5.Alpha2}}. When I refactored the reproducer {{.war}} so it contains only {{r:}} namespace, the issue is not occurring. Please find the refactored .war - it does not contains libraries, they can be copied from the original reproducer war. However, I needed to comment {{ CommandLink Javassist Compatibility Failures (richfaces-5.0.0.Alpha2) > --------------------------------------------------------------------- > > Key: RF-13458 > URL: https://issues.jboss.org/browse/RF-13458 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Steven W. > Assignee: Juraj H?ska > Attachments: ExampleRefactoredRichNamespace.war > > > There appear to be compatibility issues with the richfaces-5.0.0.Alpha2 release and the javassist package. Using older versions of the package lead to failures stating that new javassist methods are not available. > When using the newer libraries (3.14 -> javassist-3.18.0-GA) exceptions are generated on the use of previously functioning command links (the corresponding methods are still the same signatures i.e. return String and take no parameters) > {code} > value="#{messages['listByUnit']}" > title="#{messages['titleListByUnit']}" > action="#{appController.selectCurrSelectionUnit}"/> > {code} > with > {code} > public String selectCurrSelectionUnit() > {code} > yields: > {code} > 2014-01-03 13:57:57,597 ERROR [org.jboss.seam.exception.Exceptions] - handled and logged exception > javax.servlet.ServletException: /layout/controller-selections.xhtml: Property 'selectCurrSelectionUnit' not found on type com.integrits.bean.Controller_$$_javassist_seam_2 > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:606) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:374) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) > at java.lang.Thread.run(Thread.java:619) > Caused by: javax.el.ELException: /layout/controller-selections.xhtml: Property 'selectCurrSelectionUnit' not found on type com.integrits.bean.Controller_$$_javassist_seam_2 > at com.sun.faces.facelets.compiler.AttributeInstruction.write(AttributeInstruction.java:94) > at com.sun.faces.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:82) > at com.sun.faces.facelets.compiler.UILeaf.encodeAll(UILeaf.java:207) > at javax.faces.render.Renderer.encodeChildren(Renderer.java:168) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:304) > at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:105) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:304) > at com.sun.faces.renderkit.html_basic.GridRenderer.renderRow(GridRenderer.java:185) > at com.sun.faces.renderkit.html_basic.GridRenderer.encodeChildren(GridRenderer.java:129) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1819) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1822) > at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:447) > at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) > at org.jboss.seam.jsf.SeamViewHandler.renderView(SeamViewHandler.java:188) > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) > ... 33 more > {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 From issues at jboss.org Wed Feb 12 05:19:29 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 12 Feb 2014 05:19:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13458) CommandLink Javassist Compatibility Failures (richfaces-5.0.0.Alpha2) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943822#comment-12943822 ] Juraj H?ska edited comment on RF-13458 at 2/12/14 5:17 AM: ----------------------------------------------------------- I believe this is not a bug and the behavior is caused by using of old {{rich:}} namespace, instead of {{r:}} introduced in {{5.Alpha2}}. When I refactored the reproducer {{.war}} so it contains only {{r:}} namespace, the issue is not occurring. Please find the refactored .war - it does not contains libraries, they can be copied from the original reproducer war. However, I needed to comment {{ CommandLink Javassist Compatibility Failures (richfaces-5.0.0.Alpha2) > --------------------------------------------------------------------- > > Key: RF-13458 > URL: https://issues.jboss.org/browse/RF-13458 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Steven W. > Assignee: Juraj H?ska > Attachments: ExampleRefactoredRichNamespace.war > > > There appear to be compatibility issues with the richfaces-5.0.0.Alpha2 release and the javassist package. Using older versions of the package lead to failures stating that new javassist methods are not available. > When using the newer libraries (3.14 -> javassist-3.18.0-GA) exceptions are generated on the use of previously functioning command links (the corresponding methods are still the same signatures i.e. return String and take no parameters) > {code} > value="#{messages['listByUnit']}" > title="#{messages['titleListByUnit']}" > action="#{appController.selectCurrSelectionUnit}"/> > {code} > with > {code} > public String selectCurrSelectionUnit() > {code} > yields: > {code} > 2014-01-03 13:57:57,597 ERROR [org.jboss.seam.exception.Exceptions] - handled and logged exception > javax.servlet.ServletException: /layout/controller-selections.xhtml: Property 'selectCurrSelectionUnit' not found on type com.integrits.bean.Controller_$$_javassist_seam_2 > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:606) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:374) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) > at java.lang.Thread.run(Thread.java:619) > Caused by: javax.el.ELException: /layout/controller-selections.xhtml: Property 'selectCurrSelectionUnit' not found on type com.integrits.bean.Controller_$$_javassist_seam_2 > at com.sun.faces.facelets.compiler.AttributeInstruction.write(AttributeInstruction.java:94) > at com.sun.faces.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:82) > at com.sun.faces.facelets.compiler.UILeaf.encodeAll(UILeaf.java:207) > at javax.faces.render.Renderer.encodeChildren(Renderer.java:168) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:304) > at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:105) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:304) > at com.sun.faces.renderkit.html_basic.GridRenderer.renderRow(GridRenderer.java:185) > at com.sun.faces.renderkit.html_basic.GridRenderer.encodeChildren(GridRenderer.java:129) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1819) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1822) > at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:447) > at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) > at org.jboss.seam.jsf.SeamViewHandler.renderView(SeamViewHandler.java:188) > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) > ... 33 more > {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 From issues at jboss.org Wed Feb 12 06:17:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 12 Feb 2014 06:17:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13540) Websphere incarnation of MyFaces renderes optimized resources multiple times In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943840#comment-12943840 ] Luk?? Fry? commented on RF-13540: --------------------------------- We usually grab 4.3.x fixes and port them to 4.5.x/5.0.x on regular basis (before the release), but if you use or are going to use 5.0.0-SNAPSHOT, a PR will be welcomed. > Websphere incarnation of MyFaces renderes optimized resources multiple times > ---------------------------------------------------------------------------- > > Key: RF-13540 > URL: https://issues.jboss.org/browse/RF-13540 > Project: RichFaces > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.3.5, 5.0.0.Alpha3 > Environment: Myfaces/Websphere on all platforms > Reporter: Sebastian Cramer > Labels: myfaces, websphere > Fix For: 4.3.6 > > > When enabling resource optimization the packed.js (and packed.css) are rendered multiple times. The previous fix for stock myfaces is not effective against IBM's myfaces impl. -- 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 From issues at jboss.org Wed Feb 12 06:19:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 12 Feb 2014 06:19:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13540) Websphere incarnation of MyFaces renderes optimized resources multiple times In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-13540: ---------------------------- Assignee: Sebastian Cramer > Websphere incarnation of MyFaces renderes optimized resources multiple times > ---------------------------------------------------------------------------- > > Key: RF-13540 > URL: https://issues.jboss.org/browse/RF-13540 > Project: RichFaces > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.3.5, 5.0.0.Alpha3 > Environment: Myfaces/Websphere on all platforms > Reporter: Sebastian Cramer > Assignee: Sebastian Cramer > Labels: myfaces, websphere > Fix For: 4.3.6 > > > When enabling resource optimization the packed.js (and packed.css) are rendered multiple times. The previous fix for stock myfaces is not effective against IBM's myfaces impl. -- 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 From issues at jboss.org Wed Feb 12 06:53:28 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 12 Feb 2014 06:53:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13543) When r:ajax nested in r:select and event=keyup then error is thrown In-Reply-To: References: Message-ID: Juraj H?ska created RF-13543: -------------------------------- Summary: When r:ajax nested in r:select and event=keyup then error is thrown Key: RF-13543 URL: https://issues.jboss.org/browse/RF-13543 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 5.0.0.Alpha3, 5.0.0.Alpha2 Reporter: Juraj H?ska Nested {{r:ajax}} with event set to {{keyup}} in {{r:select}} component causes this error being thrown when rendering such a page: {code} javax.faces.view.facelets.TagException: /index.xhtml @21,62 keyupevent is not supported for the UISelect org.richfaces.ui.ajax.ajax.AjaxHandler.resolveEventName(AjaxHandler.java:209) org.richfaces.ui.ajax.ajax.AjaxHandler.applyNested(AjaxHandler.java:190) org.richfaces.ui.ajax.ajax.AjaxHandler.apply(AjaxHandler.java:133) javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137) org.richfaces.ui.behavior.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53) com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:190) javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120) javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137) org.richfaces.ui.behavior.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53) com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:190) javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120) javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) com.sun.faces.facelets.tag.ui.DefineHandler.applyDefinition(DefineHandler.java:106) com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:201) com.sun.faces.facelets.impl.DefaultFaceletContext$TemplateManager.apply(DefaultFaceletContext.java:395) com.sun.faces.facelets.impl.DefaultFaceletContext.includeDefinition(DefaultFaceletContext.java:366) com.sun.faces.facelets.tag.ui.InsertHandler.apply(InsertHandler.java:111) javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137) org.richfaces.ui.behavior.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53) com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:190) javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120) javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93) com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:87) com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:312) com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:371) com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:350) com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:199) com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:169) com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93) com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:87) com.sun.faces.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:161) com.sun.faces.application.view.FaceletViewHandlingStrategy.buildView(FaceletViewHandlingStrategy.java:980) com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:99) com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:219) javax.faces.webapp.FacesServlet.service(FacesServlet.java:647) {code} Issue is regression in 5.0.0.Alpha2, in other words it worked in older releases. -- 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 From issues at jboss.org Wed Feb 12 06:55:28 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 12 Feb 2014 06:55:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13543) When r:ajax nested in r:select and event=keyup then error is thrown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13543: ----------------------------- Steps to Reproduce: # build and deploy this project: https://github.com/jhuska/richfaces-sanbox/tree/RF-13543 # deploy it to e.g. Tomcat 7 # load in your browser: http://localhost:8080/richfaces-sanbox # see that the page is not rendered and mentioned error is thrown > When r:ajax nested in r:select and event=keyup then error is thrown > ------------------------------------------------------------------- > > Key: RF-13543 > URL: https://issues.jboss.org/browse/RF-13543 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 5.0.0.Alpha2, 5.0.0.Alpha3 > Reporter: Juraj H?ska > > Nested {{r:ajax}} with event set to {{keyup}} in {{r:select}} component causes this error being thrown when rendering such a page: > {code} > javax.faces.view.facelets.TagException: /index.xhtml @21,62 keyupevent is not supported for the UISelect > org.richfaces.ui.ajax.ajax.AjaxHandler.resolveEventName(AjaxHandler.java:209) > org.richfaces.ui.ajax.ajax.AjaxHandler.applyNested(AjaxHandler.java:190) > org.richfaces.ui.ajax.ajax.AjaxHandler.apply(AjaxHandler.java:133) > javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) > javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137) > org.richfaces.ui.behavior.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53) > com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:190) > javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120) > javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137) > org.richfaces.ui.behavior.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53) > com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:190) > javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120) > javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) > com.sun.faces.facelets.tag.ui.DefineHandler.applyDefinition(DefineHandler.java:106) > com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:201) > com.sun.faces.facelets.impl.DefaultFaceletContext$TemplateManager.apply(DefaultFaceletContext.java:395) > com.sun.faces.facelets.impl.DefaultFaceletContext.includeDefinition(DefaultFaceletContext.java:366) > com.sun.faces.facelets.tag.ui.InsertHandler.apply(InsertHandler.java:111) > javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137) > org.richfaces.ui.behavior.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53) > com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:190) > javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120) > javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) > com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93) > com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:87) > com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:312) > com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:371) > com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:350) > com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:199) > com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:169) > com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93) > com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:87) > com.sun.faces.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:161) > com.sun.faces.application.view.FaceletViewHandlingStrategy.buildView(FaceletViewHandlingStrategy.java:980) > com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:99) > com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) > com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:219) > javax.faces.webapp.FacesServlet.service(FacesServlet.java:647) > {code} > Issue is regression in 5.0.0.Alpha2, in other words it worked in older releases. -- 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 From issues at jboss.org Wed Feb 12 06:55:28 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 12 Feb 2014 06:55:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13543) When r:ajax nested in r:select and event=keyup then error is thrown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13543: ----------------------------- Labels: regression (was: ) > When r:ajax nested in r:select and event=keyup then error is thrown > ------------------------------------------------------------------- > > Key: RF-13543 > URL: https://issues.jboss.org/browse/RF-13543 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 5.0.0.Alpha2, 5.0.0.Alpha3 > Reporter: Juraj H?ska > Labels: regression > > Nested {{r:ajax}} with event set to {{keyup}} in {{r:select}} component causes this error being thrown when rendering such a page: > {code} > javax.faces.view.facelets.TagException: /index.xhtml @21,62 keyupevent is not supported for the UISelect > org.richfaces.ui.ajax.ajax.AjaxHandler.resolveEventName(AjaxHandler.java:209) > org.richfaces.ui.ajax.ajax.AjaxHandler.applyNested(AjaxHandler.java:190) > org.richfaces.ui.ajax.ajax.AjaxHandler.apply(AjaxHandler.java:133) > javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) > javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137) > org.richfaces.ui.behavior.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53) > com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:190) > javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120) > javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137) > org.richfaces.ui.behavior.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53) > com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:190) > javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120) > javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) > com.sun.faces.facelets.tag.ui.DefineHandler.applyDefinition(DefineHandler.java:106) > com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:201) > com.sun.faces.facelets.impl.DefaultFaceletContext$TemplateManager.apply(DefaultFaceletContext.java:395) > com.sun.faces.facelets.impl.DefaultFaceletContext.includeDefinition(DefaultFaceletContext.java:366) > com.sun.faces.facelets.tag.ui.InsertHandler.apply(InsertHandler.java:111) > javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137) > org.richfaces.ui.behavior.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53) > com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:190) > javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120) > javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) > com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93) > com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:87) > com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:312) > com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:371) > com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:350) > com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:199) > com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:169) > com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93) > com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:87) > com.sun.faces.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:161) > com.sun.faces.application.view.FaceletViewHandlingStrategy.buildView(FaceletViewHandlingStrategy.java:980) > com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:99) > com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) > com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:219) > javax.faces.webapp.FacesServlet.service(FacesServlet.java:647) > {code} > Issue is regression in 5.0.0.Alpha2, in other words it worked in older releases. -- 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 From issues at jboss.org Wed Feb 12 06:57:28 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 12 Feb 2014 06:57:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13458) CommandLink Javassist Compatibility Failures (richfaces-5.0.0.Alpha2) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943849#comment-12943849 ] Juraj H?ska commented on RF-13458: ---------------------------------- I have created issue for that mentioned bug: RF-13543. > CommandLink Javassist Compatibility Failures (richfaces-5.0.0.Alpha2) > --------------------------------------------------------------------- > > Key: RF-13458 > URL: https://issues.jboss.org/browse/RF-13458 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Steven W. > Assignee: Juraj H?ska > Attachments: ExampleRefactoredRichNamespace.war > > > There appear to be compatibility issues with the richfaces-5.0.0.Alpha2 release and the javassist package. Using older versions of the package lead to failures stating that new javassist methods are not available. > When using the newer libraries (3.14 -> javassist-3.18.0-GA) exceptions are generated on the use of previously functioning command links (the corresponding methods are still the same signatures i.e. return String and take no parameters) > {code} > value="#{messages['listByUnit']}" > title="#{messages['titleListByUnit']}" > action="#{appController.selectCurrSelectionUnit}"/> > {code} > with > {code} > public String selectCurrSelectionUnit() > {code} > yields: > {code} > 2014-01-03 13:57:57,597 ERROR [org.jboss.seam.exception.Exceptions] - handled and logged exception > javax.servlet.ServletException: /layout/controller-selections.xhtml: Property 'selectCurrSelectionUnit' not found on type com.integrits.bean.Controller_$$_javassist_seam_2 > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:606) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:374) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) > at java.lang.Thread.run(Thread.java:619) > Caused by: javax.el.ELException: /layout/controller-selections.xhtml: Property 'selectCurrSelectionUnit' not found on type com.integrits.bean.Controller_$$_javassist_seam_2 > at com.sun.faces.facelets.compiler.AttributeInstruction.write(AttributeInstruction.java:94) > at com.sun.faces.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:82) > at com.sun.faces.facelets.compiler.UILeaf.encodeAll(UILeaf.java:207) > at javax.faces.render.Renderer.encodeChildren(Renderer.java:168) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:304) > at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:105) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:304) > at com.sun.faces.renderkit.html_basic.GridRenderer.renderRow(GridRenderer.java:185) > at com.sun.faces.renderkit.html_basic.GridRenderer.encodeChildren(GridRenderer.java:129) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1819) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1822) > at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:447) > at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) > at org.jboss.seam.jsf.SeamViewHandler.renderView(SeamViewHandler.java:188) > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) > ... 33 more > {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 From issues at jboss.org Wed Feb 12 06:57:29 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 12 Feb 2014 06:57:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13458) CommandLink Javassist Compatibility Failures (richfaces-5.0.0.Alpha2) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13458: ----------------------------- Assignee: (was: Juraj H?ska) > CommandLink Javassist Compatibility Failures (richfaces-5.0.0.Alpha2) > --------------------------------------------------------------------- > > Key: RF-13458 > URL: https://issues.jboss.org/browse/RF-13458 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Steven W. > Attachments: ExampleRefactoredRichNamespace.war > > > There appear to be compatibility issues with the richfaces-5.0.0.Alpha2 release and the javassist package. Using older versions of the package lead to failures stating that new javassist methods are not available. > When using the newer libraries (3.14 -> javassist-3.18.0-GA) exceptions are generated on the use of previously functioning command links (the corresponding methods are still the same signatures i.e. return String and take no parameters) > {code} > value="#{messages['listByUnit']}" > title="#{messages['titleListByUnit']}" > action="#{appController.selectCurrSelectionUnit}"/> > {code} > with > {code} > public String selectCurrSelectionUnit() > {code} > yields: > {code} > 2014-01-03 13:57:57,597 ERROR [org.jboss.seam.exception.Exceptions] - handled and logged exception > javax.servlet.ServletException: /layout/controller-selections.xhtml: Property 'selectCurrSelectionUnit' not found on type com.integrits.bean.Controller_$$_javassist_seam_2 > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:606) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:374) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) > at java.lang.Thread.run(Thread.java:619) > Caused by: javax.el.ELException: /layout/controller-selections.xhtml: Property 'selectCurrSelectionUnit' not found on type com.integrits.bean.Controller_$$_javassist_seam_2 > at com.sun.faces.facelets.compiler.AttributeInstruction.write(AttributeInstruction.java:94) > at com.sun.faces.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:82) > at com.sun.faces.facelets.compiler.UILeaf.encodeAll(UILeaf.java:207) > at javax.faces.render.Renderer.encodeChildren(Renderer.java:168) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:304) > at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:105) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:304) > at com.sun.faces.renderkit.html_basic.GridRenderer.renderRow(GridRenderer.java:185) > at com.sun.faces.renderkit.html_basic.GridRenderer.encodeChildren(GridRenderer.java:129) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1819) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1822) > at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:447) > at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) > at org.jboss.seam.jsf.SeamViewHandler.renderView(SeamViewHandler.java:188) > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) > ... 33 more > {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 From issues at jboss.org Wed Feb 12 06:57:29 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 12 Feb 2014 06:57:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13539) r:fileUpload doesn't have the attribute fileUploadListener anymore In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943850#comment-12943850 ] Luk?? Fry? commented on RF-13539: --------------------------------- [~juergen.zimmermann] good catch, it seems the attribute was accidentally removed in Alpha2 and so it isn't part of Alpha3 as well. (checked on VDL for [Alpha1|http://docs.jboss.org/richfaces/5.0.X/5.0.0.Alpha1/vdldoc/r/fileUpload.html], [Alpha2|http://docs.jboss.org/richfaces/5.0.X/5.0.0.Alpha2/vdldoc/r/fileUpload.html]). [~bleathem] I assume it has something to do with the attribute refactoring we did in Alpha2 time-frame. Note: this has nothing to do with RF-13444. > r:fileUpload doesn't have the attribute fileUploadListener anymore > ------------------------------------------------------------------ > > Key: RF-13539 > URL: https://issues.jboss.org/browse/RF-13539 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha3 > Reporter: Juergen Zimmermann > > In RF 4.x and 5.0.0.Alpha1 the tag r:fileUpload had an attribute fileUploadListener to provide a listener which received the uploaded byte array. This attribute is gone. How shall one receive the uploaded bytes? -- 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 From issues at jboss.org Wed Feb 12 07:25:28 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 12 Feb 2014 07:25:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13541) Photoalbum - JPA tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943854#comment-12943854 ] Michal Petrov commented on RF-13541: ------------------------------------ I've fixed it, the user testing required adding about 20 classes to the deployment. Which I guess is a sign I should refactor the UserBean. After every addition a new ClassNotFoundException popped up and I was worried where it would stop. > Photoalbum - JPA tests > ---------------------- > > Key: RF-13541 > URL: https://issues.jboss.org/browse/RF-13541 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha1 > Reporter: Michal Petrov > Assignee: Michal Petrov > > In the photoalbum POM there's a profile for running some Arquillian tests. (Basic CRUD) > It's not currently runnable (outdated dependencies and/or settings). > Most of the tests are missing some dependencies but {{UserManagementTest}} and {{UserBeanTest}} seem to require a large number of class dependencies to run. -- 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 From issues at jboss.org Wed Feb 12 07:25:28 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 12 Feb 2014 07:25:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13541) Photoalbum - JPA tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov reassigned RF-13541: ---------------------------------- Assignee: Michal Petrov > Photoalbum - JPA tests > ---------------------- > > Key: RF-13541 > URL: https://issues.jboss.org/browse/RF-13541 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha1 > Reporter: Michal Petrov > Assignee: Michal Petrov > > In the photoalbum POM there's a profile for running some Arquillian tests. (Basic CRUD) > It's not currently runnable (outdated dependencies and/or settings). > Most of the tests are missing some dependencies but {{UserManagementTest}} and {{UserBeanTest}} seem to require a large number of class dependencies to run. -- 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 From issues at jboss.org Wed Feb 12 07:55:28 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 12 Feb 2014 07:55:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13541) Photoalbum - JPA tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RF-13541. -------------------------------- Fix Version/s: 4.3.6 Resolution: Done > Photoalbum - JPA tests > ---------------------- > > Key: RF-13541 > URL: https://issues.jboss.org/browse/RF-13541 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha1 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.3.6 > > > In the photoalbum POM there's a profile for running some Arquillian tests. (Basic CRUD) > It's not currently runnable (outdated dependencies and/or settings). > Most of the tests are missing some dependencies but {{UserManagementTest}} and {{UserBeanTest}} seem to require a large number of class dependencies to run. -- 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 From issues at jboss.org Wed Feb 12 09:13:28 2014 From: issues at jboss.org (=?UTF-8?Q?Marcel_=C5=A0ebek_=28JIRA=29?=) Date: Wed, 12 Feb 2014 09:13:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13250) Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943895#comment-12943895 ] Marcel ?ebek commented on RF-13250: ----------------------------------- Hello. I can see the same behavior with RF 4.3.5 after upgrading from 4.3.3. Some client still runs the old version of atmosphere and generates a lot of requests of the form /__richfaces_push?__richfacesPushAsync=1&pushSessionId=650b92c8-db1c-4e97-81e2-80cf684bbe68&X-Atmosphere-tracking-id=de550cf9-c1eb-4f26-9bd3-ae94187e4711&X-Atmosphere-Framework=1.0.10&X-Atmosphere-Transport=long-polling&X-Cache-Date=0&_=1392213448240 Each such request leads to "Committed error code 400" in server log. I also see a big number of AtomicBoolean classes in heap dump. Currently I cannot say that the number of the instances increase only when these old-version requests are comming, but it looks so. > Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final > -------------------------------------------------------------- > > Key: RF-13250 > URL: https://issues.jboss.org/browse/RF-13250 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Environment: Gentoo Linux, Tomcat 7.0.39, MyFaces 2.1.12, Tomahawk 1.1.14, RichFaces 4.3.4, APR 1.4.5 > Reporter: Milo van der Zee > Assignee: Pavol Pitonak > Labels: memoryleak > > Hello, > I did an upgrade from RF 4.3.3.Final to 4.3.4.Final and the application started to crash with 'Out Off Memory' errors. I changed the POM back to 4.3.3.Final and the problem is gone. > I also started seeing this message lot's of times: > {{WARN org.atmosphere.cpr.AtmosphereResponse - Committed error code 400}} > I don't know if that has anything to do with the error. I set {{org.atmosphere.cpr.sessionSupport}} to {{true}} and I did not see the message again. But still the application went out-of-memory. > In the crashed system heap dump I see a lot of: > - AtomicBoolean (751.000, 15.0MB) > - ConcurrentLinkedQueue > - AtmospereRequest$Builder (60.042, 13.8MB) > To me it looks like it has something to do with Atmosphere. Any ideas? > Thanks, > Milo van der Zee -- 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 From issues at jboss.org Wed Feb 12 10:25:29 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 12 Feb 2014 10:25:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13250) Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943932#comment-12943932 ] Pavol Pitonak commented on RF-13250: ------------------------------------ Hi, could you please provide more information? * Do you use any other frameworks in your application? * What server are you deploying on? * Which JSF impl do you use? * What is your definition of "extreme memory usage"? How many clients are there, how much memory is consumed? * Is memory usage high and/or is it growing over time? * What kind of messages do you push to the clients? I couldn't reproduce this issue with 4.3.4 so any additional information might be helpful. > Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final > -------------------------------------------------------------- > > Key: RF-13250 > URL: https://issues.jboss.org/browse/RF-13250 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Environment: Gentoo Linux, Tomcat 7.0.39, MyFaces 2.1.12, Tomahawk 1.1.14, RichFaces 4.3.4, APR 1.4.5 > Reporter: Milo van der Zee > Assignee: Pavol Pitonak > Labels: memoryleak > > Hello, > I did an upgrade from RF 4.3.3.Final to 4.3.4.Final and the application started to crash with 'Out Off Memory' errors. I changed the POM back to 4.3.3.Final and the problem is gone. > I also started seeing this message lot's of times: > {{WARN org.atmosphere.cpr.AtmosphereResponse - Committed error code 400}} > I don't know if that has anything to do with the error. I set {{org.atmosphere.cpr.sessionSupport}} to {{true}} and I did not see the message again. But still the application went out-of-memory. > In the crashed system heap dump I see a lot of: > - AtomicBoolean (751.000, 15.0MB) > - ConcurrentLinkedQueue > - AtmospereRequest$Builder (60.042, 13.8MB) > To me it looks like it has something to do with Atmosphere. Any ideas? > Thanks, > Milo van der Zee -- 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 From issues at jboss.org Wed Feb 12 11:11:29 2014 From: issues at jboss.org (Sebastian Cramer (JIRA)) Date: Wed, 12 Feb 2014 11:11:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13540) Websphere incarnation of MyFaces renderes optimized resources multiple times In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Cramer updated RF-13540: ---------------------------------- Git Pull Request: https://github.com/richfaces4/core/pull/20, https://github.com/richfaces/richfaces/pull/81 (was: https://github.com/richfaces4/core/pull/20) > Websphere incarnation of MyFaces renderes optimized resources multiple times > ---------------------------------------------------------------------------- > > Key: RF-13540 > URL: https://issues.jboss.org/browse/RF-13540 > Project: RichFaces > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.3.5, 5.0.0.Alpha3 > Environment: Myfaces/Websphere on all platforms > Reporter: Sebastian Cramer > Assignee: Sebastian Cramer > Labels: myfaces, websphere > Fix For: 4.3.6 > > > When enabling resource optimization the packed.js (and packed.css) are rendered multiple times. The previous fix for stock myfaces is not effective against IBM's myfaces impl. -- 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 From issues at jboss.org Wed Feb 12 11:11:29 2014 From: issues at jboss.org (Sebastian Cramer (JIRA)) Date: Wed, 12 Feb 2014 11:11:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13540) Websphere incarnation of MyFaces renderes optimized resources multiple times In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943957#comment-12943957 ] Sebastian Cramer commented on RF-13540: --------------------------------------- added a pull-request for rf5.0 > Websphere incarnation of MyFaces renderes optimized resources multiple times > ---------------------------------------------------------------------------- > > Key: RF-13540 > URL: https://issues.jboss.org/browse/RF-13540 > Project: RichFaces > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.3.5, 5.0.0.Alpha3 > Environment: Myfaces/Websphere on all platforms > Reporter: Sebastian Cramer > Assignee: Sebastian Cramer > Labels: myfaces, websphere > Fix For: 4.3.6 > > > When enabling resource optimization the packed.js (and packed.css) are rendered multiple times. The previous fix for stock myfaces is not effective against IBM's myfaces impl. -- 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 From issues at jboss.org Wed Feb 12 14:23:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 12 Feb 2014 14:23:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13544) Upgrade integration tests to WildFly 8.0.0.Final In-Reply-To: References: Message-ID: Luk?? Fry? created RF-13544: ------------------------------- Summary: Upgrade integration tests to WildFly 8.0.0.Final Key: RF-13544 URL: https://issues.jboss.org/browse/RF-13544 Project: RichFaces Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: tests - functional Affects Versions: 5.0.0.Alpha3 Reporter: Luk?? Fry? Assignee: Luk?? Fry? Fix For: 5.0.0.Alpha3 -- 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 From issues at jboss.org Wed Feb 12 14:57:29 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 12 Feb 2014 14:57:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13540) Websphere incarnation of MyFaces renderes optimized resources multiple times In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944036#comment-12944036 ] Luk?? Fry? commented on RF-13540: --------------------------------- Thanks Seb, it's merged now. > Websphere incarnation of MyFaces renderes optimized resources multiple times > ---------------------------------------------------------------------------- > > Key: RF-13540 > URL: https://issues.jboss.org/browse/RF-13540 > Project: RichFaces > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.3.5, 5.0.0.Alpha3 > Environment: Myfaces/Websphere on all platforms > Reporter: Sebastian Cramer > Assignee: Sebastian Cramer > Labels: myfaces, websphere > Fix For: 4.3.6 > > > When enabling resource optimization the packed.js (and packed.css) are rendered multiple times. The previous fix for stock myfaces is not effective against IBM's myfaces impl. -- 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 From issues at jboss.org Wed Feb 12 15:11:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 12 Feb 2014 15:11:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13436) Upgrade CKEditor to 4.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-13436: ---------------------------- Sprint: 5.0.0.Alpha4 - Sprint 1 > Upgrade CKEditor to 4.3 > ----------------------- > > Key: RF-13436 > URL: https://issues.jboss.org/browse/RF-13436 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Reporter: barbara b > Labels: rich_editor > Fix For: 5-Tracking > > > All current versions of Richfaces are working with CKEditor 3.6.6. Would it be possible to make an upgrade of CKEditor to a version 4.3? Some plugins for CKEditor are only working with the 4.X versions of the editor. -- 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 From issues at jboss.org Wed Feb 12 15:13:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 12 Feb 2014 15:13:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13436) Upgrade CKEditor to 4.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-13436: ------------------------------- Assignee: Luk?? Fry? > Upgrade CKEditor to 4.3 > ----------------------- > > Key: RF-13436 > URL: https://issues.jboss.org/browse/RF-13436 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Reporter: barbara b > Assignee: Luk?? Fry? > Labels: rich_editor > Fix For: 5-Tracking > > > All current versions of Richfaces are working with CKEditor 3.6.6. Would it be possible to make an upgrade of CKEditor to a version 4.3? Some plugins for CKEditor are only working with the 4.X versions of the editor. -- 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 From issues at jboss.org Wed Feb 12 15:13:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 12 Feb 2014 15:13:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13436) Upgrade CKEditor to 4.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-13436: ---------------------------- Fix Version/s: 5.0.0.Alpha4 (was: 5-Tracking) > Upgrade CKEditor to 4.3 > ----------------------- > > Key: RF-13436 > URL: https://issues.jboss.org/browse/RF-13436 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Reporter: barbara b > Assignee: Luk?? Fry? > Labels: rich_editor > Fix For: 5.0.0.Alpha4 > > > All current versions of Richfaces are working with CKEditor 3.6.6. Would it be possible to make an upgrade of CKEditor to a version 4.3? Some plugins for CKEditor are only working with the 4.X versions of the editor. -- 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 From issues at jboss.org Wed Feb 12 15:13:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 12 Feb 2014 15:13:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13436) Upgrade CKEditor to 4.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944040#comment-12944040 ] Luk?? Fry? commented on RF-13436: --------------------------------- We will switch to CKEditor 4.3, the dependency will be managed by RichWidgets subproject. > Upgrade CKEditor to 4.3 > ----------------------- > > Key: RF-13436 > URL: https://issues.jboss.org/browse/RF-13436 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Reporter: barbara b > Assignee: Luk?? Fry? > Labels: rich_editor > Fix For: 5.0.0.Alpha4 > > > All current versions of Richfaces are working with CKEditor 3.6.6. Would it be possible to make an upgrade of CKEditor to a version 4.3? Some plugins for CKEditor are only working with the 4.X versions of the editor. -- 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 From issues at jboss.org Wed Feb 12 16:09:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 12 Feb 2014 16:09:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12762) Duplicate id problem in ExtendedDatatable with dynamic columns In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12762: ------------------------------- Priority: Major (was: Critical) > Duplicate id problem in ExtendedDatatable with dynamic columns > -------------------------------------------------------------- > > Key: RF-12762 > URL: https://issues.jboss.org/browse/RF-12762 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.CR1 > Environment: Windows 7 , weblogic10.4.3, Myfaces 2.1.10, IE 9, FireFox 14.0.1 > Reporter: blam lam > Fix For: 5-Tracking > > > When the ExtendedDataTable contains dynamic columns (i.e. using for:each), "java.lang.IllegalStateException: component with duplicate id" will occur after the second submit from a commandButton. > The problem does not appear in 4.2.3 Final but found in 4.3 CR1 > Sample source code: > {code} > > > value="#{updateMarkBean.studentVoMarkAmends}" > var="studVo" > selectionMode="none" > height="100%"> > > > > Status > > > > > > > > > > value="#{studVo.getTaskMarkMap().get(tvo.task.taskId).amendedMark}" > size="1" maxlength="3"/> > > > > > action="#{updateMarkBean.doBeforeSave}" > styleClass="button blue"> > > > > > {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 From issues at jboss.org Wed Feb 12 16:09:29 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 12 Feb 2014 16:09:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12762) Duplicate id problem in ExtendedDatatable with dynamic columns In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12762: ------------------------------- Fix Version/s: (was: 5-Tracking) > Duplicate id problem in ExtendedDatatable with dynamic columns > -------------------------------------------------------------- > > Key: RF-12762 > URL: https://issues.jboss.org/browse/RF-12762 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.CR1 > Environment: Windows 7 , weblogic10.4.3, Myfaces 2.1.10, IE 9, FireFox 14.0.1 > Reporter: blam lam > > When the ExtendedDataTable contains dynamic columns (i.e. using for:each), "java.lang.IllegalStateException: component with duplicate id" will occur after the second submit from a commandButton. > The problem does not appear in 4.2.3 Final but found in 4.3 CR1 > Sample source code: > {code} > > > value="#{updateMarkBean.studentVoMarkAmends}" > var="studVo" > selectionMode="none" > height="100%"> > > > > Status > > > > > > > > > > value="#{studVo.getTaskMarkMap().get(tvo.task.taskId).amendedMark}" > size="1" maxlength="3"/> > > > > > action="#{updateMarkBean.doBeforeSave}" > styleClass="button blue"> > > > > > {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 From issues at jboss.org Wed Feb 12 16:11:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 12 Feb 2014 16:11:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12762) Duplicate id problem in ExtendedDatatable with dynamic columns In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-12762: ---------------------------------- Assignee: Pavol Pitonak QE, please verify on both mojarra and myfaces. > Duplicate id problem in ExtendedDatatable with dynamic columns > -------------------------------------------------------------- > > Key: RF-12762 > URL: https://issues.jboss.org/browse/RF-12762 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.CR1 > Environment: Windows 7 , weblogic10.4.3, Myfaces 2.1.10, IE 9, FireFox 14.0.1 > Reporter: blam lam > Assignee: Pavol Pitonak > > When the ExtendedDataTable contains dynamic columns (i.e. using for:each), "java.lang.IllegalStateException: component with duplicate id" will occur after the second submit from a commandButton. > The problem does not appear in 4.2.3 Final but found in 4.3 CR1 > Sample source code: > {code} > > > value="#{updateMarkBean.studentVoMarkAmends}" > var="studVo" > selectionMode="none" > height="100%"> > > > > Status > > > > > > > > > > value="#{studVo.getTaskMarkMap().get(tvo.task.taskId).amendedMark}" > size="1" maxlength="3"/> > > > > > action="#{updateMarkBean.doBeforeSave}" > styleClass="button blue"> > > > > > {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 From issues at jboss.org Wed Feb 12 16:27:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 12 Feb 2014 16:27:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11992) cache bug in portlet In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-11992. -------------------------------- Fix Version/s: (was: 5-Tracking) Resolution: Out of Date > cache bug in portlet > -------------------- > > Key: RF-11992 > URL: https://issues.jboss.org/browse/RF-11992 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 3.3.3.Final, 4.2.0.CR1 > Environment: jboss portal 2.7.2; Gatein portal > Reporter: Ivan Ravin > Assignee: Brian Leathem > Priority: Minor > > On Jboss and Gatein portal richfaces cant be cached when user is logged in. > Bug is found for richfaces 3.3.3 but i think can be reproduced for 4.x because org.richfaces.resource.AbstractCacheableResource has similar code. > The steps for reproduce bug are: > download portlet bridge 2.2 archive > deploy richFacesPortlet.war from portlet bridge archive (i used jboss portal 2.7.2 bundle and GateIn-3.1.0-FINAL-jbossas) > look at network activity (i did with firefox + firebug, the same result on any other browser). Just open page with richfaces portlet. > When user is not logged in, all richfaces resources are caching well, and this is headers returned by server: > |Cache-Control |max-age=86400| > |Content-Type |text/javascript| > |Date |Thu, 26 Jan 2012 17:57:39 GMT| > |Expires |27 Jan 2012 17:57:39 GMT| > |Last-Modified |26 Jan 2012 17:42:17 GMT| > |Server |Apache-Coyote/1.1| > |X-Powered-By |Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0| > But when user is logged in all richfaces stuff come from network every time (more than 1.3 mb). > This is headers returned by portal 2.7.2 when user logged in: > |Cache-Control |{color:red}no-cache,{color} max-age=86400| > |Content-Type |text/javascript| > |Date |Thu, 26 Jan 2012 18:26:49 GMT| > |Expires |{color:red}Thu, 01 Jan 1970 03:00:00 MSK,{color} 27 Jan 2012 18:26:49 GMT| > |Last-Modified |26 Jan 2012 18:05:56 GMT| > |{color:red}Pragma{color} |{color:red}No-cache{color}| > |Server |Apache-Coyote/1.1| > |Transfer-Encoding |chunked| > |X-Powered-By |Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0| > The same problem with GateIn-3.1.0-FINAL-jbossas bundle, but now only one wrong header: > |Cache-Control |max-age=86400| > |Content-Type |text/javascript;charset=UTF-8| > |Date |Sat, 28 Jan 2012 08:54:14 GMT| > |Expires |29 Jan 2012 08:54:14 GMT| > |Last-Modified |28 Jan 2012 08:51:11 GMT| > |{color:red}Pragma{color} |{color:red}No-cache{color}| > |Server |Apache-Coyote/1.1| > |Transfer-Encoding |chunked| > |X-Powered-By |Servlet 2.5; JBoss-5.0/JBossWeb-2.1| > This header (Pragma) appears only when user is logged in, and again, all richfaces resources come through network. > I did some debug and found that richfaces create good headers, but there is some code in portal which put wrong values into real response before richfaces. I cant find this code in portal sources, so maybe it is JBoss AS problem, or third party component. > In Gatein portal problem was partially resolved: it overwrites 2 wrong headers with values provided by richfaces, but "pragma" header is absent in richfaces response, and this way in secured portlets richfaces generate too much unnesessary traffic. > To solve problem for GateIn there is enough to provide empty Pragma header; To solve problem for JBoss Portal its required to fix resource headers processing in portal code, like it done in gatein. -- 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 From issues at jboss.org Wed Feb 12 17:11:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 12 Feb 2014 17:11:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12897) ExtendedPartialViewContextImpl swallows exceptions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944059#comment-12944059 ] Brian Leathem commented on RF-12897: ------------------------------------ [~lfryc] is this still an issue with your proposed EPVC rewrite? > ExtendedPartialViewContextImpl swallows exceptions > -------------------------------------------------- > > Key: RF-12897 > URL: https://issues.jboss.org/browse/RF-12897 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.2.Final > Environment: Windows 7, JDK 1.6 > Reporter: Cristian Cerb > Assignee: Luk?? Fry? > Labels: richfaces > Fix For: 5-Tracking > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Method public VisitResult visit(VisitContext context, UIComponent target) of class ExtendedPartialViewContextImpl swallows exceptions. I think exceptions should be wrapped inside a FaceException and propagated. This class http://java.net/projects/mojarra/sources/svn/content/trunk/jsf-ri/src/main/java/com/sun/faces/context/PartialViewContextImpl.java seems to have served as a model for the RF one, but the RF class inadvertently chose to swallow exceptions instead of propagating them up. This causes unpredictable behaviour, such as system being stuck in the browser. > I just found an older version of Sun's Mojarra where they had the same issue, but the newer versions seem to have fixed it. See this taken from jsf 2.1.4: > {code} > public VisitResult visit(VisitContext context, UIComponent comp) { > try { > if (curPhase == PhaseId.APPLY_REQUEST_VALUES) { > // RELEASE_PENDING handle immediate request(s) > // If the user requested an immediate request > // Make sure to set the immediate flag here. > comp.processDecodes(ctx); > } else if (curPhase == PhaseId.PROCESS_VALIDATIONS) { > comp.processValidators(ctx); > } else if (curPhase == PhaseId.UPDATE_MODEL_VALUES) { > comp.processUpdates(ctx); > } else if (curPhase == PhaseId.RENDER_RESPONSE) { > PartialResponseWriter writer = ctx.getPartialViewContext().getPartialResponseWriter(); > writer.startUpdate(comp.getClientId(ctx)); > try { > // do the default behavior... > comp.encodeAll(ctx); > } > catch (Exception ce) { > if (LOGGER.isLoggable(Level.SEVERE)) { > LOGGER.severe(ce.toString()); > } > if (LOGGER.isLoggable(Level.FINE)) { > LOGGER.log(Level.FINE, > ce.toString(), > ce); > } > } > writer.endUpdate(); > } > else { > throw new IllegalStateException("I18N: Unexpected " + > "PhaseId passed to " + > " PhaseAwareContextCallback: " + > curPhase.toString()); > } > } > catch (IOException ex) { > ex.printStackTrace(); > } > // Once we visit a component, there is no need to visit > // its children, since processDecodes/Validators/Updates and > // encodeAll() already traverse the subtree. We return > // VisitResult.REJECT to supress the subtree visit. > return VisitResult.REJECT; > } > } > {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 From issues at jboss.org Wed Feb 12 17:21:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 12 Feb 2014 17:21:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13539) r:fileUpload doesn't have the attribute fileUploadListener anymore In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13539: ------------------------------- Fix Version/s: 5.0.0.Alpha4 > r:fileUpload doesn't have the attribute fileUploadListener anymore > ------------------------------------------------------------------ > > Key: RF-13539 > URL: https://issues.jboss.org/browse/RF-13539 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha3 > Reporter: Juergen Zimmermann > Fix For: 5.0.0.Alpha4 > > > In RF 4.x and 5.0.0.Alpha1 the tag r:fileUpload had an attribute fileUploadListener to provide a listener which received the uploaded byte array. This attribute is gone. How shall one receive the uploaded bytes? -- 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 From issues at jboss.org Wed Feb 12 17:23:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 12 Feb 2014 17:23:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13458) CommandLink Javassist Compatibility Failures (richfaces-5.0.0.Alpha2) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13458. -------------------------------- Resolution: Rejected Great work [~jhuska]! > CommandLink Javassist Compatibility Failures (richfaces-5.0.0.Alpha2) > --------------------------------------------------------------------- > > Key: RF-13458 > URL: https://issues.jboss.org/browse/RF-13458 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Steven W. > Attachments: ExampleRefactoredRichNamespace.war > > > There appear to be compatibility issues with the richfaces-5.0.0.Alpha2 release and the javassist package. Using older versions of the package lead to failures stating that new javassist methods are not available. > When using the newer libraries (3.14 -> javassist-3.18.0-GA) exceptions are generated on the use of previously functioning command links (the corresponding methods are still the same signatures i.e. return String and take no parameters) > {code} > value="#{messages['listByUnit']}" > title="#{messages['titleListByUnit']}" > action="#{appController.selectCurrSelectionUnit}"/> > {code} > with > {code} > public String selectCurrSelectionUnit() > {code} > yields: > {code} > 2014-01-03 13:57:57,597 ERROR [org.jboss.seam.exception.Exceptions] - handled and logged exception > javax.servlet.ServletException: /layout/controller-selections.xhtml: Property 'selectCurrSelectionUnit' not found on type com.integrits.bean.Controller_$$_javassist_seam_2 > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:606) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:374) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) > at java.lang.Thread.run(Thread.java:619) > Caused by: javax.el.ELException: /layout/controller-selections.xhtml: Property 'selectCurrSelectionUnit' not found on type com.integrits.bean.Controller_$$_javassist_seam_2 > at com.sun.faces.facelets.compiler.AttributeInstruction.write(AttributeInstruction.java:94) > at com.sun.faces.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:82) > at com.sun.faces.facelets.compiler.UILeaf.encodeAll(UILeaf.java:207) > at javax.faces.render.Renderer.encodeChildren(Renderer.java:168) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:304) > at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:105) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:304) > at com.sun.faces.renderkit.html_basic.GridRenderer.renderRow(GridRenderer.java:185) > at com.sun.faces.renderkit.html_basic.GridRenderer.encodeChildren(GridRenderer.java:129) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:847) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1819) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1822) > at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:447) > at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) > at org.jboss.seam.jsf.SeamViewHandler.renderView(SeamViewHandler.java:188) > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) > ... 33 more > {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 From issues at jboss.org Wed Feb 12 17:27:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 12 Feb 2014 17:27:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13543) When r:ajax nested in r:select and event=keyup then error is thrown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13543: ------------------------------- Fix Version/s: 5.0.0.Alpha4 > When r:ajax nested in r:select and event=keyup then error is thrown > ------------------------------------------------------------------- > > Key: RF-13543 > URL: https://issues.jboss.org/browse/RF-13543 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 5.0.0.Alpha2, 5.0.0.Alpha3 > Reporter: Juraj H?ska > Labels: regression > Fix For: 5.0.0.Alpha4 > > > Nested {{r:ajax}} with event set to {{keyup}} in {{r:select}} component causes this error being thrown when rendering such a page: > {code} > javax.faces.view.facelets.TagException: /index.xhtml @21,62 keyupevent is not supported for the UISelect > org.richfaces.ui.ajax.ajax.AjaxHandler.resolveEventName(AjaxHandler.java:209) > org.richfaces.ui.ajax.ajax.AjaxHandler.applyNested(AjaxHandler.java:190) > org.richfaces.ui.ajax.ajax.AjaxHandler.apply(AjaxHandler.java:133) > javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) > javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137) > org.richfaces.ui.behavior.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53) > com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:190) > javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120) > javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137) > org.richfaces.ui.behavior.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53) > com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:190) > javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120) > javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) > com.sun.faces.facelets.tag.ui.DefineHandler.applyDefinition(DefineHandler.java:106) > com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:201) > com.sun.faces.facelets.impl.DefaultFaceletContext$TemplateManager.apply(DefaultFaceletContext.java:395) > com.sun.faces.facelets.impl.DefaultFaceletContext.includeDefinition(DefaultFaceletContext.java:366) > com.sun.faces.facelets.tag.ui.InsertHandler.apply(InsertHandler.java:111) > javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137) > org.richfaces.ui.behavior.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53) > com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:190) > javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120) > javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) > com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93) > com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:87) > com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:312) > com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:371) > com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:350) > com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:199) > com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:169) > com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93) > com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:87) > com.sun.faces.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:161) > com.sun.faces.application.view.FaceletViewHandlingStrategy.buildView(FaceletViewHandlingStrategy.java:980) > com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:99) > com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) > com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:219) > javax.faces.webapp.FacesServlet.service(FacesServlet.java:647) > {code} > Issue is regression in 5.0.0.Alpha2, in other words it worked in older releases. -- 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 From issues at jboss.org Thu Feb 13 00:29:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 13 Feb 2014 00:29:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13531) selects: cannot select option on IE11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944093#comment-12944093 ] Brian Leathem commented on RF-13531: ------------------------------------ Sorry, I missed that the keyboard was broken to when reading the description. I've removed use of the keypress event for listening for "special" keys. I tested in recent Chrome, Firefox and IE and it works. There is a chance this breaks in old Firefox, but I don't have access to it. @QE please take this into consideration when testing the fix. > selects: cannot select option on IE11 > ------------------------------------- > > Key: RF-13531 > URL: https://issues.jboss.org/browse/RF-13531 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.3.5, 4.5.0.Alpha2, 5.0.0.Alpha3 > Environment: IE 11 > Reporter: Ji?? ?tefek > Assignee: Brian Leathem > Labels: IE11 > Fix For: 4.3.6 > > > Components: autocomplete, select, inplaceSelect. > Works on IE 10. > ---- > Issues: > * User cannot visually select an option from the popup list == moving mouse over the items in the list will not change theirs class. > ** however clicking on the item will select the option correctly. {color:red}EXCEPT autocomplete (RF4), where it will not select anything{color}. > ** workaround: the item can be selected, when moving off the list and back to it on the correct item, but the cursor should not move through scroller. > * User cannot select option with keyboard. -- 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 From issues at jboss.org Thu Feb 13 00:29:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 13 Feb 2014 00:29:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13531) selects: cannot select option on IE11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13531: ------------------------------- Labels: IE11 needs-qe (was: IE11) > selects: cannot select option on IE11 > ------------------------------------- > > Key: RF-13531 > URL: https://issues.jboss.org/browse/RF-13531 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.3.5, 4.5.0.Alpha2, 5.0.0.Alpha3 > Environment: IE 11 > Reporter: Ji?? ?tefek > Assignee: Brian Leathem > Labels: IE11, needs-qe > Fix For: 4.3.6 > > > Components: autocomplete, select, inplaceSelect. > Works on IE 10. > ---- > Issues: > * User cannot visually select an option from the popup list == moving mouse over the items in the list will not change theirs class. > ** however clicking on the item will select the option correctly. {color:red}EXCEPT autocomplete (RF4), where it will not select anything{color}. > ** workaround: the item can be selected, when moving off the list and back to it on the correct item, but the cursor should not move through scroller. > * User cannot select option with keyboard. -- 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 From issues at jboss.org Thu Feb 13 00:45:29 2014 From: issues at jboss.org (Kaveh A. (JIRA)) Date: Thu, 13 Feb 2014 00:45:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12682) extendedDataTable render issue with rich:tabPanel In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944096#comment-12944096 ] Kaveh A. commented on RF-12682: ------------------------------- Hi Pavol There is really no need to create another issue. This issue was never fixed. With every new release of RichFaces we have to open the jars and make the above modifications to get it to work for us. This issue is more of a display issue for extended data table where some columns (usually non-forzen columns) will disappear. This only happens when the table is hidden during the load and then it is made visible. Feel free to use the attached program to reproduce. In this particular case the extended data table is hidden in one of the tabs of tabPanel but any parent component that hides the extended data table during the load and then un-hides it will have this issue. It is critical to note that extended data table should be empty to reproduce this error. > extendedDataTable render issue with rich:tabPanel > ------------------------------------------------- > > Key: RF-12682 > URL: https://issues.jboss.org/browse/RF-12682 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.3.Final, 4.3.0.M3, 4.3.0.CR1, 4.3.0.Final > Reporter: Kaveh A. > Labels: extendedDataTable, render, richfaces, tabpanel, testcase_provided > Attachments: richfacesBug2.zip, RichFacesBugEclipseProject.zip > > > This issue is not just specific to tabPanel. Anytime the extendedDataTable is hidden (when the page loads) and then it is made visible later the table can not display the data (table is empty at the load time). > In this particular case if we load a page with two tabs. Furthermore if we have one extendedDataTable in each tab (the first tab shows and the second tab is not shown at first). In this case once the user clicks on the second tab and tries to populate the extendedDataTable (via any action). Then the table is not rendered properly. A sample project has been provided at the following link that further describe this issue. You can download the eclipse project attached at the end of the following message to reproduce this issue. > https://community.jboss.org/message/783787 -- 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 From issues at jboss.org Thu Feb 13 02:13:28 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Thu, 13 Feb 2014 02:13:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12762) Duplicate id problem in ExtendedDatatable with dynamic columns In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-12762: ---------------------------------- Assignee: Matej Novotny (was: Pavol Pitonak) > Duplicate id problem in ExtendedDatatable with dynamic columns > -------------------------------------------------------------- > > Key: RF-12762 > URL: https://issues.jboss.org/browse/RF-12762 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.CR1 > Environment: Windows 7 , weblogic10.4.3, Myfaces 2.1.10, IE 9, FireFox 14.0.1 > Reporter: blam lam > Assignee: Matej Novotny > > When the ExtendedDataTable contains dynamic columns (i.e. using for:each), "java.lang.IllegalStateException: component with duplicate id" will occur after the second submit from a commandButton. > The problem does not appear in 4.2.3 Final but found in 4.3 CR1 > Sample source code: > {code} > > > value="#{updateMarkBean.studentVoMarkAmends}" > var="studVo" > selectionMode="none" > height="100%"> > > > > Status > > > > > > > > > > value="#{studVo.getTaskMarkMap().get(tvo.task.taskId).amendedMark}" > size="1" maxlength="3"/> > > > > > action="#{updateMarkBean.doBeforeSave}" > styleClass="button blue"> > > > > > {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 From issues at jboss.org Thu Feb 13 03:21:28 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 13 Feb 2014 03:21:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13545) Simpleapp: Support for servlets/Java EE containers at generation time In-Reply-To: References: Message-ID: Juraj H?ska created RF-13545: -------------------------------- Summary: Simpleapp: Support for servlets/Java EE containers at generation time Key: RF-13545 URL: https://issues.jboss.org/browse/RF-13545 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: archetype Affects Versions: 5.0.0.Alpha3 Environment: simpleapp archetype Reporter: Juraj H?ska In [this|https://community.jboss.org/message/857393#857393] discussion [~bleathem] wrote: {quote} I'd like to see us support both servlet and EE containers with our archetypes at generation time. We'd build in the archetype conditional asking the user if the generated project should target EE or servlet containers. This should also be done in our Forge plugin. {quote} {quote} Taking a profile approach leaves a lot of unnecessary clutter in their pom.xml. whereas asking at archetype evaluation time we can trim the unnecessary pieces out of the pom.xml. {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 From issues at jboss.org Thu Feb 13 03:29:28 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 13 Feb 2014 03:29:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13546) Forge plugin: support for Servlet or JavaEE containers In-Reply-To: References: Message-ID: Juraj H?ska created RF-13546: -------------------------------- Summary: Forge plugin: support for Servlet or JavaEE containers Key: RF-13546 URL: https://issues.jboss.org/browse/RF-13546 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 5.0.0.Alpha3 Reporter: Juraj H?ska Priority: Minor There should be taken similar approach as in RF-13545 for RichFaces Forge plugin. That is to ask whether an user wants Servlet or Java EE container, and then create a profile for it. -- 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 From issues at jboss.org Thu Feb 13 03:29:28 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 13 Feb 2014 03:29:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13545) Simpleapp: Support for servlets/Java EE containers at generation time In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13545: ----------------------------- Priority: Minor (was: Major) > Simpleapp: Support for servlets/Java EE containers at generation time > --------------------------------------------------------------------- > > Key: RF-13545 > URL: https://issues.jboss.org/browse/RF-13545 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 5.0.0.Alpha3 > Environment: simpleapp archetype > Reporter: Juraj H?ska > Priority: Minor > > In [this|https://community.jboss.org/message/857393#857393] discussion [~bleathem] wrote: > {quote} > I'd like to see us support both servlet and EE containers with our archetypes at generation time. We'd build in the archetype conditional asking the user if the generated project should target EE or servlet containers. This should also be done in our Forge plugin. > {quote} > {quote} > Taking a profile approach leaves a lot of unnecessary clutter in their pom.xml. whereas asking at archetype evaluation time we can trim the unnecessary pieces out of the pom.xml. > {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 From issues at jboss.org Thu Feb 13 03:39:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Macko_=28JIRA=29?=) Date: Thu, 13 Feb 2014 03:39:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13547) @ResourceDependency with missing resource doesn't throw an exception In-Reply-To: References: Message-ID: Luk?? Macko created RF-13547: -------------------------------- Summary: @ResourceDependency with missing resource doesn't throw an exception Key: RF-13547 URL: https://issues.jboss.org/browse/RF-13547 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: cdk Reporter: Luk?? Macko If there is an annotation {{@ResourceDependency}} with not existing resource such as {{@ResourceDependency(library = "org.richfaces", name = "base-component.reslib")}} It doesn't throw an exception. However, exception CacheLoader returned null for key org.richfaces:base-component. -- 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 From issues at jboss.org Thu Feb 13 03:49:28 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 13 Feb 2014 03:49:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13548) Clean using of guava dependency across framework In-Reply-To: References: Message-ID: Juraj H?ska created RF-13548: -------------------------------- Summary: Clean using of guava dependency across framework Key: RF-13548 URL: https://issues.jboss.org/browse/RF-13548 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: compatibility, core, third-party Affects Versions: 5.0.0.Alpha3 Environment: Guava dependency and Tomcat 8 Reporter: Juraj H?ska As per [this|https://community.jboss.org/message/857397?et=watches.email.thread#857397] discussion we should do something with _Guava_ dependency. * We should investigate whether _maven shade_ plugin will for any good * Investigate on refactoring the code so it does not contain dependencies from Guava marked as {{@Beta}} It seems that this blocks using of Tomcat 8 properly. -- 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 From issues at jboss.org Thu Feb 13 03:51:29 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 13 Feb 2014 03:51:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13545) Simpleapp: Support for servlets/Java EE containers at generation time In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13545: ----------------------------- Forum Reference: https://community.jboss.org/thread/236741 > Simpleapp: Support for servlets/Java EE containers at generation time > --------------------------------------------------------------------- > > Key: RF-13545 > URL: https://issues.jboss.org/browse/RF-13545 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 5.0.0.Alpha3 > Environment: simpleapp archetype > Reporter: Juraj H?ska > Priority: Minor > > In [this|https://community.jboss.org/message/857393#857393] discussion [~bleathem] wrote: > {quote} > I'd like to see us support both servlet and EE containers with our archetypes at generation time. We'd build in the archetype conditional asking the user if the generated project should target EE or servlet containers. This should also be done in our Forge plugin. > {quote} > {quote} > Taking a profile approach leaves a lot of unnecessary clutter in their pom.xml. whereas asking at archetype evaluation time we can trim the unnecessary pieces out of the pom.xml. > {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 From issues at jboss.org Thu Feb 13 03:51:29 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 13 Feb 2014 03:51:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13547) @ResourceDependency with missing resource doesn't throw an exception In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-13547: ---------------------------- Priority: Minor (was: Major) > @ResourceDependency with missing resource doesn't throw an exception > -------------------------------------------------------------------- > > Key: RF-13547 > URL: https://issues.jboss.org/browse/RF-13547 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: cdk > Reporter: Luk?? Macko > Priority: Minor > > If there is an annotation {{@ResourceDependency}} with not existing resource > such as {{@ResourceDependency(library = "org.richfaces", name = "base-component.reslib")}} > It doesn't throw an exception. However, exception CacheLoader returned null for key org.richfaces:base-component. -- 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 From issues at jboss.org Thu Feb 13 03:51:29 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 13 Feb 2014 03:51:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13548) Clean using of guava dependency across framework In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13548: ----------------------------- Description: As per [this|https://community.jboss.org/message/857397?et=watches.email.thread#857397] discussion we should do something with _Guava_ dependency. * We should investigate whether _maven shade_ plugin will be for any good * Investigate on refactoring the code so it does not contain dependencies from Guava marked as {{@Beta}} It seems that this blocks using of Tomcat 8 properly. was: As per [this|https://community.jboss.org/message/857397?et=watches.email.thread#857397] discussion we should do something with _Guava_ dependency. * We should investigate whether _maven shade_ plugin will for any good * Investigate on refactoring the code so it does not contain dependencies from Guava marked as {{@Beta}} It seems that this blocks using of Tomcat 8 properly. > Clean using of guava dependency across framework > ------------------------------------------------ > > Key: RF-13548 > URL: https://issues.jboss.org/browse/RF-13548 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: compatibility, core, third-party > Affects Versions: 5.0.0.Alpha3 > Environment: Guava dependency and Tomcat 8 > Reporter: Juraj H?ska > > As per [this|https://community.jboss.org/message/857397?et=watches.email.thread#857397] discussion we should do something with _Guava_ dependency. > * We should investigate whether _maven shade_ plugin will be for any good > * Investigate on refactoring the code so it does not contain dependencies from Guava marked as {{@Beta}} > It seems that this blocks using of Tomcat 8 properly. -- 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 From issues at jboss.org Thu Feb 13 03:55:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Macko_=28JIRA=29?=) Date: Thu, 13 Feb 2014 03:55:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13547) @ResourceDependency with missing resource should throw meaningful exception In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Macko updated RF-13547: ----------------------------- Summary: @ResourceDependency with missing resource should throw meaningful exception (was: @ResourceDependency with missing resource doesn't throw an exception) > @ResourceDependency with missing resource should throw meaningful exception > --------------------------------------------------------------------------- > > Key: RF-13547 > URL: https://issues.jboss.org/browse/RF-13547 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: cdk > Reporter: Luk?? Macko > Priority: Minor > > If there is an annotation {{@ResourceDependency}} with not existing resource > such as {{@ResourceDependency(library = "org.richfaces", name = "base-component.reslib")}} > It doesn't throw an exception. However, exception CacheLoader returned null for key org.richfaces:base-component. -- 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 From issues at jboss.org Thu Feb 13 03:57:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Macko_=28JIRA=29?=) Date: Thu, 13 Feb 2014 03:57:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13547) @ResourceDependency with missing resource should throw meaningful exception In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944125#comment-12944125 ] Luk?? Macko commented on RF-13547: ---------------------------------- com.google.common.cache.CacheLoader$InvalidCacheLoadException: CacheLoader returned null for key org.richfaces:base-component. at com.google.common.cache.LocalCache$Segment.getAndRecordStats(LocalCache.java:2407) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2375) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2337) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2252) at com.google.common.cache.LocalCache.get(LocalCache.java:3990) at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3994) at com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4878) at org.richfaces.resource.ResourceLibraryFactoryImpl.getResourceLibrary(ResourceLibraryFactoryImpl.java:85) at org.richfaces.ui.core.ResourceLibraryRenderer.encodeEnd(ResourceLibraryRenderer.java:67) at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:875) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786) at com.sun.faces.renderkit.html_basic.HeadRenderer.encodeHeadResources(HeadRenderer.java:105) at com.sun.faces.renderkit.html_basic.HeadRenderer.encodeEnd(HeadRenderer.java:92) at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:875) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782) at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:402) at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) at java.lang.Thread.run(Thread.java:724) > @ResourceDependency with missing resource should throw meaningful exception > --------------------------------------------------------------------------- > > Key: RF-13547 > URL: https://issues.jboss.org/browse/RF-13547 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: cdk > Reporter: Luk?? Macko > Priority: Minor > > If there is an annotation {{@ResourceDependency}} with not existing resource > such as {{@ResourceDependency(library = "org.richfaces", name = "base-component.reslib")}} > It doesn't throw an exception. However, exception CacheLoader returned null for key org.richfaces:base-component. -- 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 From issues at jboss.org Thu Feb 13 04:07:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 13 Feb 2014 04:07:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13547) @ResourceDependency with missing resource should throw meaningful exception In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944125#comment-12944125 ] Luk?? Fry? edited comment on RF-13547 at 2/13/14 4:06 AM: ---------------------------------------------------------- {code} com.google.common.cache.CacheLoader$InvalidCacheLoadException: CacheLoader returned null for key org.richfaces:base-component. at com.google.common.cache.LocalCache$Segment.getAndRecordStats(LocalCache.java:2407) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2375) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2337) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2252) at com.google.common.cache.LocalCache.get(LocalCache.java:3990) at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3994) at com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4878) at org.richfaces.resource.ResourceLibraryFactoryImpl.getResourceLibrary(ResourceLibraryFactoryImpl.java:85) at org.richfaces.ui.core.ResourceLibraryRenderer.encodeEnd(ResourceLibraryRenderer.java:67) at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:875) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786) at com.sun.faces.renderkit.html_basic.HeadRenderer.encodeHeadResources(HeadRenderer.java:105) at com.sun.faces.renderkit.html_basic.HeadRenderer.encodeEnd(HeadRenderer.java:92) at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:875) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782) at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:402) at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) at java.lang.Thread.run(Thread.java:724) {code} was (Author: lukindo): com.google.common.cache.CacheLoader$InvalidCacheLoadException: CacheLoader returned null for key org.richfaces:base-component. at com.google.common.cache.LocalCache$Segment.getAndRecordStats(LocalCache.java:2407) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2375) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2337) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2252) at com.google.common.cache.LocalCache.get(LocalCache.java:3990) at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3994) at com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4878) at org.richfaces.resource.ResourceLibraryFactoryImpl.getResourceLibrary(ResourceLibraryFactoryImpl.java:85) at org.richfaces.ui.core.ResourceLibraryRenderer.encodeEnd(ResourceLibraryRenderer.java:67) at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:875) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786) at com.sun.faces.renderkit.html_basic.HeadRenderer.encodeHeadResources(HeadRenderer.java:105) at com.sun.faces.renderkit.html_basic.HeadRenderer.encodeEnd(HeadRenderer.java:92) at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:875) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782) at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:402) at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) at java.lang.Thread.run(Thread.java:724) > @ResourceDependency with missing resource should throw meaningful exception > --------------------------------------------------------------------------- > > Key: RF-13547 > URL: https://issues.jboss.org/browse/RF-13547 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: cdk > Reporter: Luk?? Macko > Priority: Minor > > If there is an annotation {{@ResourceDependency}} with not existing resource > such as {{@ResourceDependency(library = "org.richfaces", name = "base-component.reslib")}} > It doesn't throw an exception. However, exception CacheLoader returned null for key org.richfaces:base-component. -- 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 From issues at jboss.org Thu Feb 13 06:09:28 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 13 Feb 2014 06:09:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13549) Photoalbum: cannot upload image In-Reply-To: References: Message-ID: Ji?? ?tefek created RF-13549: -------------------------------- Summary: Photoalbum: cannot upload image Key: RF-13549 URL: https://issues.jboss.org/browse/RF-13549 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: examples Reporter: Ji?? ?tefek Assignee: Michal Petrov Fix For: 4.3.6 The uploaded image is not saved to db. After this [commit|https://github.com/richfaces4/dev-examples/commit/0c787a307f6cdba9329b76eba020df80d6a0f02d#diff-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 From issues at jboss.org Thu Feb 13 06:11:28 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 13 Feb 2014 06:11:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13549) Photoalbum: cannot upload image In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944197#comment-12944197 ] Ji?? ?tefek commented on RF-13549: ---------------------------------- Same as [RF-13257|https://issues.jboss.org/browse/RF-13257] > Photoalbum: cannot upload image > ------------------------------- > > Key: RF-13549 > URL: https://issues.jboss.org/browse/RF-13549 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Reporter: Ji?? ?tefek > Assignee: Michal Petrov > Labels: photoalbum > Fix For: 4.3.6 > > > The uploaded image is not saved to db. > After this [commit|https://github.com/richfaces4/dev-examples/commit/0c787a307f6cdba9329b76eba020df80d6a0f02d#diff-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 From issues at jboss.org Thu Feb 13 06:21:28 2014 From: issues at jboss.org (Pavel Slegr (JIRA)) Date: Thu, 13 Feb 2014 06:21:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13247) Upgrade the RichFaces guava dependency to the latest version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944199#comment-12944199 ] Pavel Slegr commented on RF-13247: ---------------------------------- Do we need to use guava lib at all ? I mean, RF 5.x is intended to be used with WildFly 8, which requires Java SE7 at minimum... while RF states as requirements JDK6 (http://docs.jboss.org/richfaces/latest_5_X/Developer_Guide/en-US/html_single/#sect-Developer_Guide-Getting_started_with_RichFaces-Technical_Requirements) which is EOLed anyway... 1. Aren't the majority of guava features covered with JDK7 already ? Is there a desperate need to use it ? 2. Shouldn't RF5 jump to minimum Java SE7 ? just asking... > Upgrade the RichFaces guava dependency to the latest version > ------------------------------------------------------------ > > 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 > Assignee: Brian Leathem > Priority: Minor > Fix For: 5.0.0.Alpha4 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > 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 From issues at jboss.org Thu Feb 13 06:41:28 2014 From: issues at jboss.org (Thorsten Richter (JIRA)) Date: Thu, 13 Feb 2014 06:41:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13247) Upgrade the RichFaces guava dependency to the latest version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944205#comment-12944205 ] Thorsten Richter commented on RF-13247: --------------------------------------- [~lfryc] I think I used the "jboss-as-kitchensink-rf" project as a template for setting up the project. > Upgrade the RichFaces guava dependency to the latest version > ------------------------------------------------------------ > > 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 > Assignee: Brian Leathem > Priority: Minor > Fix For: 5.0.0.Alpha4 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > 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 From issues at jboss.org Thu Feb 13 07:23:28 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 13 Feb 2014 07:23:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13531) selects: cannot select option on IE11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13531: ----------------------------- Labels: IE11 (was: IE11 needs-qe) > selects: cannot select option on IE11 > ------------------------------------- > > Key: RF-13531 > URL: https://issues.jboss.org/browse/RF-13531 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.3.5, 4.5.0.Alpha2, 5.0.0.Alpha3 > Environment: IE 11 > Reporter: Ji?? ?tefek > Assignee: Brian Leathem > Labels: IE11 > Fix For: 4.3.6 > > > Components: autocomplete, select, inplaceSelect. > Works on IE 10. > ---- > Issues: > * User cannot visually select an option from the popup list == moving mouse over the items in the list will not change theirs class. > ** however clicking on the item will select the option correctly. {color:red}EXCEPT autocomplete (RF4), where it will not select anything{color}. > ** workaround: the item can be selected, when moving off the list and back to it on the correct item, but the cursor should not move through scroller. > * User cannot select option with keyboard. -- 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 From issues at jboss.org Thu Feb 13 07:25:28 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 13 Feb 2014 07:25:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13531) selects: cannot select option on IE11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944222#comment-12944222 ] Ji?? ?tefek commented on RF-13531: ---------------------------------- Verified, leaving opened for verification in RF 4.5 and 5 > selects: cannot select option on IE11 > ------------------------------------- > > Key: RF-13531 > URL: https://issues.jboss.org/browse/RF-13531 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.3.5, 4.5.0.Alpha2, 5.0.0.Alpha3 > Environment: IE 11 > Reporter: Ji?? ?tefek > Assignee: Brian Leathem > Labels: IE11 > Fix For: 4.3.6 > > > Components: autocomplete, select, inplaceSelect. > Works on IE 10. > ---- > Issues: > * User cannot visually select an option from the popup list == moving mouse over the items in the list will not change theirs class. > ** however clicking on the item will select the option correctly. {color:red}EXCEPT autocomplete (RF4), where it will not select anything{color}. > ** workaround: the item can be selected, when moving off the list and back to it on the correct item, but the cursor should not move through scroller. > * User cannot select option with keyboard. -- 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 From issues at jboss.org Thu Feb 13 07:33:28 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Thu, 13 Feb 2014 07:33:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13549) Photoalbum: cannot upload image In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RF-13549. -------------------------------- Resolution: Done > Photoalbum: cannot upload image > ------------------------------- > > Key: RF-13549 > URL: https://issues.jboss.org/browse/RF-13549 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Reporter: Ji?? ?tefek > Assignee: Michal Petrov > Labels: photoalbum > Fix For: 4.3.6 > > > The uploaded image is not saved to db. > After this [commit|https://github.com/richfaces4/dev-examples/commit/0c787a307f6cdba9329b76eba020df80d6a0f02d#diff-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 From issues at jboss.org Thu Feb 13 08:21:28 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 13 Feb 2014 08:21:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13492) Photoalbum: cancel selection in other r:trees when browsing an album navigation panel In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13492. ---------------------------- verified, closing > Photoalbum: cancel selection in other r:trees when browsing an album navigation panel > ------------------------------------------------------------------------------------- > > Key: RF-13492 > URL: https://issues.jboss.org/browse/RF-13492 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.3.5 > Reporter: Luk?? Fry? > Assignee: Michal Petrov > Labels: photoalbum > Fix For: 4.3.6 > > Attachments: screenshot02.png > > > When we have several album categories opened, we can select a current album from each of them. > Only one is an opened one (visible in the main page content area), but the r:tree components show current selection for each album shelf separately. > Look at the attached screenshot. -- 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 From issues at jboss.org Thu Feb 13 08:23:29 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 13 Feb 2014 08:23:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13549) Photoalbum: cannot upload image In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13549. ---------------------------- verified, closing > Photoalbum: cannot upload image > ------------------------------- > > Key: RF-13549 > URL: https://issues.jboss.org/browse/RF-13549 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Reporter: Ji?? ?tefek > Assignee: Michal Petrov > Labels: photoalbum > Fix For: 4.3.6 > > > The uploaded image is not saved to db. > After this [commit|https://github.com/richfaces4/dev-examples/commit/0c787a307f6cdba9329b76eba020df80d6a0f02d#diff-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 From issues at jboss.org Thu Feb 13 09:15:32 2014 From: issues at jboss.org (Steve Oh (JIRA)) Date: Thu, 13 Feb 2014 09:15:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13317) ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944271#comment-12944271 ] Steve Oh commented on RF-13317: ------------------------------- backporting to 4.3 would be great ;) see my SO question: http://stackoverflow.com/questions/21726718/can-i-use-fixviewstate-js-from-omnifaces-with-richfaces-a4jajax-rf4jsf2-2-mo regards > 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: Luk?? Fry? > Priority: Critical > Labels: backport, jsf22 > Fix For: 5.0.0.Alpha3 > > > I'm using several {{}} fields in a {{}}, 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|https://javaserverfaces.java.net/nonav/docs/2.2/javadocs/javax/faces/render/ResponseStateManager.html#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 From issues at jboss.org Thu Feb 13 11:39:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 13 Feb 2014 11:39:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12897) ExtendedPartialViewContextImpl swallows exceptions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-12897: ---------------------------- Fix Version/s: (was: 5-Tracking) I will check - un-assigning for assessment and scheduling. > ExtendedPartialViewContextImpl swallows exceptions > -------------------------------------------------- > > Key: RF-12897 > URL: https://issues.jboss.org/browse/RF-12897 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.2.Final > Environment: Windows 7, JDK 1.6 > Reporter: Cristian Cerb > Assignee: Luk?? Fry? > Labels: richfaces > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Method public VisitResult visit(VisitContext context, UIComponent target) of class ExtendedPartialViewContextImpl swallows exceptions. I think exceptions should be wrapped inside a FaceException and propagated. This class http://java.net/projects/mojarra/sources/svn/content/trunk/jsf-ri/src/main/java/com/sun/faces/context/PartialViewContextImpl.java seems to have served as a model for the RF one, but the RF class inadvertently chose to swallow exceptions instead of propagating them up. This causes unpredictable behaviour, such as system being stuck in the browser. > I just found an older version of Sun's Mojarra where they had the same issue, but the newer versions seem to have fixed it. See this taken from jsf 2.1.4: > {code} > public VisitResult visit(VisitContext context, UIComponent comp) { > try { > if (curPhase == PhaseId.APPLY_REQUEST_VALUES) { > // RELEASE_PENDING handle immediate request(s) > // If the user requested an immediate request > // Make sure to set the immediate flag here. > comp.processDecodes(ctx); > } else if (curPhase == PhaseId.PROCESS_VALIDATIONS) { > comp.processValidators(ctx); > } else if (curPhase == PhaseId.UPDATE_MODEL_VALUES) { > comp.processUpdates(ctx); > } else if (curPhase == PhaseId.RENDER_RESPONSE) { > PartialResponseWriter writer = ctx.getPartialViewContext().getPartialResponseWriter(); > writer.startUpdate(comp.getClientId(ctx)); > try { > // do the default behavior... > comp.encodeAll(ctx); > } > catch (Exception ce) { > if (LOGGER.isLoggable(Level.SEVERE)) { > LOGGER.severe(ce.toString()); > } > if (LOGGER.isLoggable(Level.FINE)) { > LOGGER.log(Level.FINE, > ce.toString(), > ce); > } > } > writer.endUpdate(); > } > else { > throw new IllegalStateException("I18N: Unexpected " + > "PhaseId passed to " + > " PhaseAwareContextCallback: " + > curPhase.toString()); > } > } > catch (IOException ex) { > ex.printStackTrace(); > } > // Once we visit a component, there is no need to visit > // its children, since processDecodes/Validators/Updates and > // encodeAll() already traverse the subtree. We return > // VisitResult.REJECT to supress the subtree visit. > return VisitResult.REJECT; > } > } > {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 From issues at jboss.org Thu Feb 13 12:09:28 2014 From: issues at jboss.org (=?UTF-8?Q?Marcel_=C5=A0ebek_=28JIRA=29?=) Date: Thu, 13 Feb 2014 12:09:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13250) Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944368#comment-12944368 ] Marcel ?ebek commented on RF-13250: ----------------------------------- I'll try to answer your questions and describe the environment in which I see the leaking behavior. I also present some ideas what could be the cause. The first thing is that 'old-version' atmosphere requests seem to be one way how to rapidly create a huge number (in our case 700 000) of AtomicBoolean instances. However, even without such requests, heap gets exhausted. I suspect a relation to RFPL-2345 - problem with dead sessions. With RF 4.3.3, heap gets filled with MessageData classes, even with org.atmosphere.cpr.CometSupport.maxInactiveActivity = 60000 and org.richfaces.push.session.maxInactiveInterval = 60000 parameters. However, with RF 4.3.5, heap gets filled with AtomicBoolean and char[] instances (and possibly other classes). The heap growth in both cases is similar and very non-linear. In the beginning, the number is 0 (for MessageData) or low (AtomicBoolean), but after some time, it starts to grow and the speed of grow increases. The application runs in non-critical production environment, so I cannot tell exactly what the clients are doing, but it seems that new dead session appears from time to time, and with each new dead session, the speed of memory exhaustion grows. I'm not sure if I'd be able to isolate a small testcase. However, I have a heap dump which I can provide you. I don't want to provide it publicly (it may contant some sensitive information), but if you are interested, I can provide it to you privately. It is about 70M gzipped. Finally, here are the answers for your questions. Except a few libraries, I don't use any framework that should affect the result. The application is deployed on jboss 7.1 (latest build from git) with default jsf (mojarra 2.1.16) and native ssl on 64-bit linux. Extreme memory usage was not my invention, this name was chosen by original bug reporter. However, in my case, the application exhausts 0.75 GB heap with quite low but continuous load in scope of days (like 1-3 days). Low load means something like at most 5 clients simultaneously, but often just one client. The application is pushing just "null" messages (requests for re-rendering) with no useful data. Any additional questions or suggestions what to try are welcome. > Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final > -------------------------------------------------------------- > > Key: RF-13250 > URL: https://issues.jboss.org/browse/RF-13250 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Environment: Gentoo Linux, Tomcat 7.0.39, MyFaces 2.1.12, Tomahawk 1.1.14, RichFaces 4.3.4, APR 1.4.5 > Reporter: Milo van der Zee > Assignee: Pavol Pitonak > Labels: memoryleak > > Hello, > I did an upgrade from RF 4.3.3.Final to 4.3.4.Final and the application started to crash with 'Out Off Memory' errors. I changed the POM back to 4.3.3.Final and the problem is gone. > I also started seeing this message lot's of times: > {{WARN org.atmosphere.cpr.AtmosphereResponse - Committed error code 400}} > I don't know if that has anything to do with the error. I set {{org.atmosphere.cpr.sessionSupport}} to {{true}} and I did not see the message again. But still the application went out-of-memory. > In the crashed system heap dump I see a lot of: > - AtomicBoolean (751.000, 15.0MB) > - ConcurrentLinkedQueue > - AtmospereRequest$Builder (60.042, 13.8MB) > To me it looks like it has something to do with Atmosphere. Any ideas? > Thanks, > Milo van der Zee -- 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 From issues at jboss.org Thu Feb 13 13:17:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 13 Feb 2014 13:17:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12897) ExtendedPartialViewContextImpl swallows exceptions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944362#comment-12944362 ] Luk?? Fry? edited comment on RF-12897 at 2/13/14 1:16 PM: ---------------------------------------------------------- I will check - un-scheduling for assessment and re-scheduling. was (Author: lfryc): I will check - un-assigning for assessment and scheduling. > ExtendedPartialViewContextImpl swallows exceptions > -------------------------------------------------- > > Key: RF-12897 > URL: https://issues.jboss.org/browse/RF-12897 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.2.Final > Environment: Windows 7, JDK 1.6 > Reporter: Cristian Cerb > Assignee: Luk?? Fry? > Labels: richfaces > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Method public VisitResult visit(VisitContext context, UIComponent target) of class ExtendedPartialViewContextImpl swallows exceptions. I think exceptions should be wrapped inside a FaceException and propagated. This class http://java.net/projects/mojarra/sources/svn/content/trunk/jsf-ri/src/main/java/com/sun/faces/context/PartialViewContextImpl.java seems to have served as a model for the RF one, but the RF class inadvertently chose to swallow exceptions instead of propagating them up. This causes unpredictable behaviour, such as system being stuck in the browser. > I just found an older version of Sun's Mojarra where they had the same issue, but the newer versions seem to have fixed it. See this taken from jsf 2.1.4: > {code} > public VisitResult visit(VisitContext context, UIComponent comp) { > try { > if (curPhase == PhaseId.APPLY_REQUEST_VALUES) { > // RELEASE_PENDING handle immediate request(s) > // If the user requested an immediate request > // Make sure to set the immediate flag here. > comp.processDecodes(ctx); > } else if (curPhase == PhaseId.PROCESS_VALIDATIONS) { > comp.processValidators(ctx); > } else if (curPhase == PhaseId.UPDATE_MODEL_VALUES) { > comp.processUpdates(ctx); > } else if (curPhase == PhaseId.RENDER_RESPONSE) { > PartialResponseWriter writer = ctx.getPartialViewContext().getPartialResponseWriter(); > writer.startUpdate(comp.getClientId(ctx)); > try { > // do the default behavior... > comp.encodeAll(ctx); > } > catch (Exception ce) { > if (LOGGER.isLoggable(Level.SEVERE)) { > LOGGER.severe(ce.toString()); > } > if (LOGGER.isLoggable(Level.FINE)) { > LOGGER.log(Level.FINE, > ce.toString(), > ce); > } > } > writer.endUpdate(); > } > else { > throw new IllegalStateException("I18N: Unexpected " + > "PhaseId passed to " + > " PhaseAwareContextCallback: " + > curPhase.toString()); > } > } > catch (IOException ex) { > ex.printStackTrace(); > } > // Once we visit a component, there is no need to visit > // its children, since processDecodes/Validators/Updates and > // encodeAll() already traverse the subtree. We return > // VisitResult.REJECT to supress the subtree visit. > return VisitResult.REJECT; > } > } > {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 From issues at jboss.org Thu Feb 13 13:25:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 13 Feb 2014 13:25:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13317) ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944410#comment-12944410 ] Luk?? Fry? commented on RF-13317: --------------------------------- Backport issue opened here: https://issues.jboss.org/browse/RF-13507 > 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: Luk?? Fry? > Priority: Critical > Labels: backport, jsf22 > Fix For: 5.0.0.Alpha3 > > > I'm using several {{}} fields in a {{}}, 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|https://javaserverfaces.java.net/nonav/docs/2.2/javadocs/javax/faces/render/ResponseStateManager.html#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 From issues at jboss.org Thu Feb 13 13:47:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 13 Feb 2014 13:47:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13247) Upgrade the RichFaces guava dependency to the latest version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944419#comment-12944419 ] Luk?? Fry? commented on RF-13247: --------------------------------- [~pslegr], more on dropping Guava: https://community.jboss.org/message/857565#857565 > Upgrade the RichFaces guava dependency to the latest version > ------------------------------------------------------------ > > 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 > Assignee: Brian Leathem > Priority: Minor > Fix For: 5.0.0.Alpha4 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > 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 From issues at jboss.org Thu Feb 13 14:11:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 13 Feb 2014 14:11:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13544) Upgrade integration tests to WildFly 8.0.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-13544. ----------------------------- Resolution: Done > Upgrade integration tests to WildFly 8.0.0.Final > ------------------------------------------------ > > Key: RF-13544 > URL: https://issues.jboss.org/browse/RF-13544 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha3 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha3 > > -- 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 From issues at jboss.org Thu Feb 13 14:21:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 13 Feb 2014 14:21:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13101) rich:select Method getSelectInputLabel is not working when using objects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944430#comment-12944430 ] Luk?? Fry? commented on RF-13101: --------------------------------- [~jigg4], any chance you could provide a reproducer here? Or at least clarify how we could reproduce it? Matej [tried|https://github.com/richfaces4/components/pull/83#issuecomment-34970700] to reproduce it here, but with no luck. > rich:select Method getSelectInputLabel is not working when using objects > ------------------------------------------------------------------------ > > Key: RF-13101 > URL: https://issues.jboss.org/browse/RF-13101 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, component-selects > Affects Versions: 4.3.2, 5.0.0.Alpha1 > Reporter: J W > Labels: rich:select, select > Fix For: 4.5-Tracking > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The condition of the if-statement in org.richfaces.renderkit.SelectHelper.getSelectInputLabel(FacesContext facesContext, UIComponent component) is not working with the string-representations of the items. If using cloned objects the equals method will return false, even if the items are the same, because the IDs are different. > The method should use only the strings of the objects, similiar to how MyFaces has solved this (check workarround). -- 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 From issues at jboss.org Fri Feb 14 02:31:29 2014 From: issues at jboss.org (Pavel Slegr (JIRA)) Date: Fri, 14 Feb 2014 02:31:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13247) Upgrade the RichFaces guava dependency to the latest version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944506#comment-12944506 ] Pavel Slegr commented on RF-13247: ---------------------------------- Thanks Lukas, it shows like huge codebase to be reworked, which does not have suitable replacement in JDK7 anyway...Let's make sure to use proper version of guava then, not being in troubles at the end.... so 16.0.1 ... same as WF8 Final !? > Upgrade the RichFaces guava dependency to the latest version > ------------------------------------------------------------ > > 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 > Assignee: Brian Leathem > Priority: Minor > Fix For: 5.0.0.Alpha4 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > 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 From issues at jboss.org Fri Feb 14 03:07:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 14 Feb 2014 03:07:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13538) Closeables.closeQuietly() removed in Guava 16.0, but still used in RF In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-13538: ---------------------------- Forum Reference: https://community.jboss.org/thread/237087 > Closeables.closeQuietly() removed in Guava 16.0, but still used in RF > --------------------------------------------------------------------- > > Key: RF-13538 > URL: https://issues.jboss.org/browse/RF-13538 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha3 > Reporter: Juergen Zimmermann > Fix For: 5.0.0.Alpha4 > > > For instance in org.richfaces.resource.Java2DUserResourceWrapperImpl at line 73 is an invocation of Closeables.closeQuietly(...). However, this method is removed in Guava 16.0 which is now used in RF 5.0.0.Alpha3. > javadoc of Guava 14.0 already mentioned: > "Deprecated. Where possible, use the try-with-resources statement if using JDK7 or Closer on JDK6 to close one or more Closeable objects. This method is deprecated because it is easy to misuse and may swallow IO exceptions that really should be thrown and handled. See Guava issue 1118 for a more detailed explanation of the reasons for deprecation and see Closing Resources for more information on the problems with closing Closeable objects and some of the preferred solutions for handling it correctly. This method is scheduled to be removed in Guava 16.0." > Well, now the method is removed, but still invoked in RF 5.0.0.Alpha3. -- 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 From issues at jboss.org Fri Feb 14 03:07:29 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 14 Feb 2014 03:07:29 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13247) Upgrade the RichFaces guava dependency to the latest version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-13247: ---------------------------- Forum Reference: https://community.jboss.org/thread/237087 > Upgrade the RichFaces guava dependency to the latest version > ------------------------------------------------------------ > > 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 > Assignee: Brian Leathem > Priority: Minor > Fix For: 5.0.0.Alpha4 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > 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 From issues at jboss.org Fri Feb 14 13:01:28 2014 From: issues at jboss.org (=?UTF-8?Q?Marcel_=C5=A0ebek_=28JIRA=29?=) Date: Fri, 14 Feb 2014 13:01:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13250) Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944817#comment-12944817 ] Marcel ?ebek commented on RF-13250: ----------------------------------- Well, I've done some more investigations on this issue. At least one way how to leak resources is to send a malformed atmosphere request to an application. For example, send GET to /__richfaces_push?X-Atmosphere-Transport=long-polling Then, with each such request, you should observe "Committed error code 400" and one leaked org.atmosphere.cpr.Meteor instance (it is leaked, because it is referenced from Meteor.cache). The error is probably produced by PushHandlerFilter - check for session == null. I think it is time to reopen the bug now. If you cannot reproduce it, now I think I should be able to find the missing piece of information. > Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final > -------------------------------------------------------------- > > Key: RF-13250 > URL: https://issues.jboss.org/browse/RF-13250 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Environment: Gentoo Linux, Tomcat 7.0.39, MyFaces 2.1.12, Tomahawk 1.1.14, RichFaces 4.3.4, APR 1.4.5 > Reporter: Milo van der Zee > Assignee: Pavol Pitonak > Labels: memoryleak > > Hello, > I did an upgrade from RF 4.3.3.Final to 4.3.4.Final and the application started to crash with 'Out Off Memory' errors. I changed the POM back to 4.3.3.Final and the problem is gone. > I also started seeing this message lot's of times: > {{WARN org.atmosphere.cpr.AtmosphereResponse - Committed error code 400}} > I don't know if that has anything to do with the error. I set {{org.atmosphere.cpr.sessionSupport}} to {{true}} and I did not see the message again. But still the application went out-of-memory. > In the crashed system heap dump I see a lot of: > - AtomicBoolean (751.000, 15.0MB) > - ConcurrentLinkedQueue > - AtmospereRequest$Builder (60.042, 13.8MB) > To me it looks like it has something to do with Atmosphere. Any ideas? > Thanks, > Milo van der Zee -- 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 From issues at jboss.org Fri Feb 14 14:28:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 14 Feb 2014 14:28:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13550) Refactor bridge-base so that it will allow bridges to extend widgets In-Reply-To: References: Message-ID: Luk?? Fry? created RF-13550: ------------------------------- Summary: Refactor bridge-base so that it will allow bridges to extend widgets Key: RF-13550 URL: https://issues.jboss.org/browse/RF-13550 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component Affects Versions: 5.0.0.Alpha3 Reporter: Luk?? Fry? This will allow bridges to extend widget API and make it more natural for JSF users, e.g.: Editor is now: {code} $.widget('rf.editorBridge', $.rf.bridgeBase, {code} but we want: {code} $.widget('rf.editorBridge', $.rich.editor, {code} On multiple inheritance in jQuery Widget Factory: https://forum.jquery.com/topic/how-to-extend-a-widget-factory-widget-with-multiple-base-widgets The way of extending API should be designed in that way that user calls e.g.: {code} #{r:component('editor')}.setValue(); {code} but editor has (or rather should have) only a method which is named in jQuery Widget Factory style: {code} data('editor').value() / data('editor').value(newValue) editor('value') / editor('value', newValue) {code} So, we want bridge to add the setValue/getValue API: {code} $.extend(widget), { setValue: ..., getValue: ...}; {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 From issues at jboss.org Fri Feb 14 14:30:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 14 Feb 2014 14:30:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13550) Refactor bridge-base so that it will allow bridges to extend widgets In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944840#comment-12944840 ] Luk?? Fry? commented on RF-13550: --------------------------------- One of the caveats: bridge is usually called on component root, but widget can be instantiated on inner element: {code}

{code} {code} $('#editor').editorBridge(); ---> internally calls $("#editor" + 'Input').editor(); {code} > Refactor bridge-base so that it will allow bridges to extend widgets > -------------------------------------------------------------------- > > Key: RF-13550 > URL: https://issues.jboss.org/browse/RF-13550 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 5.0.0.Alpha3 > Reporter: Luk?? Fry? > > This will allow bridges to extend widget API and make it more natural for JSF users, e.g.: > Editor is now: > {code} > $.widget('rf.editorBridge', $.rf.bridgeBase, > {code} > but we want: > {code} > $.widget('rf.editorBridge', $.rich.editor, > {code} > On multiple inheritance in jQuery Widget Factory: > https://forum.jquery.com/topic/how-to-extend-a-widget-factory-widget-with-multiple-base-widgets > The way of extending API should be designed in that way that user calls e.g.: > {code} > #{r:component('editor')}.setValue(); > {code} > but editor has (or rather should have) only a method which is named in jQuery Widget Factory style: > {code} > data('editor').value() / data('editor').value(newValue) > editor('value') / editor('value', newValue) > {code} > So, we want bridge to add the setValue/getValue API: > {code} > $.extend(widget), { setValue: ..., getValue: ...}; > {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 From issues at jboss.org Fri Feb 14 15:06:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 14 Feb 2014 15:06:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13436) Upgrade CKEditor to 4.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-13436. ----------------------------- Labels: needs-qe (was: rich_editor) Resolution: Done The CKEditor was switched to use CKEditor 4 distributed in RichWidgets project. [~ppitonak] could you please start QE process for the component upgrade? Note that the whole component underwent general re-implementation using jQuery Widget Factory, etc. but the API stays same. We need to cover and expand test suite: * re-test with Metamer * [expand RichWidgets tests suite|https://github.com/richwidgets/richwidgets/issues/179] (just few basic tests there) * add few basic framework tests (should use Page Fragment) Pavol, could you please open appropriate RFPL/QE JIRAs? > Upgrade CKEditor to 4.3 > ----------------------- > > Key: RF-13436 > URL: https://issues.jboss.org/browse/RF-13436 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Reporter: barbara b > Assignee: Luk?? Fry? > Labels: needs-qe > Fix For: 5.0.0.Alpha4 > > > All current versions of Richfaces are working with CKEditor 3.6.6. Would it be possible to make an upgrade of CKEditor to a version 4.3? Some plugins for CKEditor are only working with the 4.X versions of the editor. -- 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 From issues at jboss.org Fri Feb 14 15:06:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 14 Feb 2014 15:06:28 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13436) Upgrade CKEditor to 4.3 (and switch code to jQuery Widget Factory) In-Reply-To: References: