[JBoss JIRA] (RF-13449) rich:fileuload progress not displaying
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13449?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak reassigned RF-13449:
----------------------------------
Assignee: Brian Leathem (was: Pavol Pitonak)
I was able to reproduce the bug on Showcase with fake 300MB PNG image (see screenshot 3).
It is not possible to reproduce with small files because upload is very fast. However, when I changed max file size in Metamer to 900 MB and I uploaded 300 MB file, it worked fine (screenshot 1). As soon as I tried to upload 1.2GB file (more than allowed maximum), it behaved as in Showcase (screenshot 2).
> rich:fileuload progress not displaying
> --------------------------------------
>
> Key: RF-13449
> URL: https://issues.jboss.org/browse/RF-13449
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4
> Reporter: Javier Gonzales
> Assignee: Brian Leathem
>
> On my local environment with IE 9 the progress bar works fine. Once the application is deployed in higher environments the progress bar does not display the progress, the bar is empty. I've also noticed this same issue in the showcases with the same browser IE9 (I've tried other browsers and also experiencing the same problem, IE10/11, Chrome 31.0, etc). After some debugging I've noticed that when the application makes the following request, the response is always 0.
> http://showcase.richfaces.org/rfRes/fileUploadProgress.jsf?ln=org.richfac....
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (RF-13458) CommandLink Javassist Compatibility Failures (richfaces-5.0.0.Alpha2)
by Marek Novotny (JIRA)
[ https://issues.jboss.org/browse/RF-13458?page=com.atlassian.jira.plugin.s... ]
Marek Novotny commented on RF-13458:
------------------------------------
Seam uses javasist 3.15.0-GA as the latest version which can use/was tested. 3.18.0-GA changed signature in method
javassist.util.proxy.RuntimeSupport.find2Methods(Ljava/lang/Object;Ljava/lang/String;Ljava/lang/String;ILjava/lang/String;[Ljava/lang/reflect/Method;)V
So you should use corresponding Seam BOM as recommended/tested thirdparty dependencies ;-). And if you would like to use newer versions, you can expect some glitches. This is not an issue of Richfaces.
> 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.
>
> 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}
> <rich:commandLink id="listByUnit" render="f_home,f_selections,g_body_wrapper"
> 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
12 years
[JBoss JIRA] (RF-13449) rich:fileuload progress not displaying
by Javier Gonzales (JIRA)
[ https://issues.jboss.org/browse/RF-13449?page=com.atlassian.jira.plugin.s... ]
Javier Gonzales updated RF-13449:
---------------------------------
Description:
On my local environment with IE 9 the progress bar works fine. Once the application is deployed in higher environments the progress bar does not display the progress, the bar is empty. I've also noticed this same issue in the showcases with the same browser IE9 (I've tried other browsers and also experiencing the same problem, IE10/11, Chrome 31.0, etc). After some debugging I've noticed that when the application makes the following request, the response is always 0.
http://showcase.richfaces.org/rfRes/fileUploadProgress.jsf?ln=org.richfac....
was:
On my local environment with IE 9 the progress bar works fine. Once the application is deployed in higher environments then the progress bar does not display at all. I've also noticed this same issue in the showcases with the same browser IE9 (I've tried other browsers and also experiencing the same problem, IE10/11, Chrome 31.0, etc). After some debugging I've noticed that when the application makes the following request, the response is always 0.
http://showcase.richfaces.org/rfRes/fileUploadProgress.jsf?ln=org.richfac....
> rich:fileuload progress not displaying
> --------------------------------------
>
> Key: RF-13449
> URL: https://issues.jboss.org/browse/RF-13449
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4
> Reporter: Javier Gonzales
> Assignee: Pavol Pitonak
>
> On my local environment with IE 9 the progress bar works fine. Once the application is deployed in higher environments the progress bar does not display the progress, the bar is empty. I've also noticed this same issue in the showcases with the same browser IE9 (I've tried other browsers and also experiencing the same problem, IE10/11, Chrome 31.0, etc). After some debugging I've noticed that when the application makes the following request, the response is always 0.
> http://showcase.richfaces.org/rfRes/fileUploadProgress.jsf?ln=org.richfac....
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (RF-13452) UIDataAdaptor must not register as listener for PostAddToViewEvent in its constructor
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13452?page=com.atlassian.jira.plugin.s... ]
Brian Leathem edited comment on RF-13452 at 1/3/14 6:03 PM:
------------------------------------------------------------
This issue will take a fair amount of investigation to determine the effect of the system event listeners, and find alternatives.
https://github.com/richfaces/richfaces/blob/master/framework/src/main/jav...
was (Author: bleathem):
This issue will take a fair amount of investigation to determine the effect of the system event listeners, and find alternatives.
> UIDataAdaptor must not register as listener for PostAddToViewEvent in its constructor
> -------------------------------------------------------------------------------------
>
> Key: RF-13452
> URL: https://issues.jboss.org/browse/RF-13452
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: compatibility
> Affects Versions: 4.3.4
> Environment: Mojarra 2.1.?? - 2.1.26
> Reporter: Lutz Ulrich
> Labels: UIDataAdaptor, UIDataTable, dynamical-add
> Fix For: 5-Tracking
>
>
> Whenever a component which is based on {{org.richfaces.component.UIDataAdaptor}} is added dynamically, NPE occurs in the next RESTORE_VIEW Phase when using Mojarra 2.1.x.
> My first guess was, that this would be an error in Mojarra (issue 2152, see https://java.net/jira/browse/JAVASERVERFACES-2152?page=com.atlassian.jira... ),
> which occurs whenever a sub-class of {{UIComponent}} registers itself as {{javax.faces.event.SystemEventListener}} for
> {{javax.faces.event.PostAddToViewEvent}} in ist constructor, just like {{UIDataAdaptor}} does.
> Now, Manfred Riem of Mojarra argues (in the very issue named above), that registering for PostAddToView in the constructor is a design flaw in itself.
> Note that the error occurs with every UIComponent which is added dynamically and which registers itself as PostAddToView listener in its constructor. For the Mojarra issue, I provided a simple component which extends the standard JSF HtmlOutputText and registers itself in its constructor, too. Baam - same error. So maybe more components of RichFaces are affected - not just those based on {{UIDataAdaptor}}.
> For completion, here is a stack trace:
> {quote}
> Schwerwiegend: java.lang.NullPointerException
> at javax.faces.component.UIComponent$ComponentSystemEventListenerAdapter.processEvent(UIComponent.java:2526)
> at javax.faces.event.SystemEvent.processListener(SystemEvent.java:106)
> at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2163)
> at com.sun.faces.application.ApplicationImpl.invokeComponentListenersFor(ApplicationImpl.java:2111)
> at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:289)
> at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:247)
> at javax.faces.component.UIComponentBase.publishAfterViewEvents(UIComponentBase.java:2203)
> at javax.faces.component.UIComponentBase.doPostAddProcessing(UIComponentBase.java:1885)
> at javax.faces.component.UIComponentBase.setParent(UIComponentBase.java:405)
> at javax.faces.component.UIComponentBase$ChildrenList.add(UIComponentBase.java:2637)
> at javax.faces.component.UIComponentBase$ChildrenList.add(UIComponentBase.java:2609)
> at com.sun.faces.application.view.FaceletPartialStateManagementStrategy.restoreDynamicAdd(FaceletPartialStateManagementStrategy.java:421)
> at com.sun.faces.application.view.FaceletPartialStateManagementStrategy.restoreDynamicActions(FaceletPartialStateManagementStrategy.java:247)
> at com.sun.faces.application.view.FaceletPartialStateManagementStrategy.restoreView(FaceletPartialStateManagementStrategy.java:570)
> at com.sun.faces.application.StateManagerImpl.restoreView(StateManagerImpl.java:138)
> at com.sun.faces.application.view.ViewHandlingStrategy.restoreView(ViewHandlingStrategy.java:123)
> at com.sun.faces.application.view.FaceletViewHandlingStrategy.restoreView(FaceletViewHandlingStrategy.java:653)
> at com.sun.faces.application.view.MultiViewHandler.restoreView(MultiViewHandler.java:142)
> at javax.faces.application.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:301)
> at javax.faces.application.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:301)
> at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:192)
> at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:116)
> at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (RF-13450) page attribute on dataScroller doesn't work with a request scope
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13450?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13450:
-------------------------------
Fix Version/s: 5-Tracking
> page attribute on dataScroller doesn't work with a request scope
> ----------------------------------------------------------------
>
> Key: RF-13450
> URL: https://issues.jboss.org/browse/RF-13450
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-ScrollableDataTable
> Affects Versions: 4.3.4
> Environment: java 6 on jboss as 7.1
> Reporter: Luca Stancapiano
> Labels: datatable, scrollable
> Fix For: 5-Tracking
>
> Attachments: scrollablesample.zip, scrollablesample.zip
>
>
> Here the dataTable with a dataScroller:
> {code}
> <rich:dataScroller for="table" maxPages="5"
> page="#{currentPage.page}" />
> <rich:dataTable value="#{carsBean.allInventoryItems}" var="car"
> id="table" rows="10">
> <rich:column>
> <f:facet name="header">
> <h:outputText value="Vendor " />
> </f:facet>
> <h:outputText value="#{car.vendor}" />
> </rich:column>
> ...
> </rich:dataTable>
> {code}
> Here the definition of the currentPage bean:
> {code}
> <managed-bean>
> <managed-bean-name>currentPage</managed-bean-name>
> <managed-bean-class>prova.CurrentPage</managed-bean-class>
> <managed-bean-scope>request</managed-bean-scope>
> </managed-bean>
> {code}
> Here the currentPage bean:
> {code}
> package prova;
> public class CurrentPage {
>
> private int page = 1;
> public int getPage() {
> return page;
> }
> public void setPage(int page) {
> this.page = page;
> }
> }
> {code}
> the 'page' attribute in the dataScroller configuration doesn't work if set to 'request' scope. The buttons rewind and forward are blocked and it doesn't work. If I configure it with a 'session' scope that's 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
12 years