May 2014 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13615) ExtendedDataTable: double ajax request on scrolling

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RF-13615?page=com.atlassian.jira.plugin.s... ] Michal Petrov resolved RF-13615. -------------------------------- Resolution: Done > ExtendedDataTable: double ajax request on scrolling > --------------------------------------------------- > > Key: RF-13615 > URL: https://issues.jboss.org/browse/RF-13615 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.3.6 > Environment: Problem can be tested in richfaces showcase. > http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=extende... > Reporter: Holger Walter > Assignee: Michal Petrov > Fix For: 4.3.8 > > Attachments: edt.png > > > 1. Go to the extendedDataTable showcase > 2. Turn on ajax loading. > 3. Open the debugger of your browser and watch the network communication > 4. Scroll down in the table untli new data has to be fetched. > => one POST request is sent. This is fine. > 5. Change the width of a column in the table. > => one POST request is sent. This is fine. > 6. Scroll again in the table untli new data has to be fetched. > -> 2 POST requests are sent. WHY? > From now on, on each scroll, the table always sends 2 requests. This behavior stops only when your relaod the table. > Due to this behavior I get some perfromance issues, as I have to execute some own javascript after each request. > Is there a possibility to prevent the 2nd POST request. I would be happy even with a dirty hack, or just a hint showing me from where the 2nd request is triggered. > Best regards > wlh -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13584) Backport the RF 5 component fixes

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13584?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13584: ------------------------------- Labels: needs-qe (was: ) > Backport the RF 5 component fixes > --------------------------------- > > Key: RF-13584 > URL: https://issues.jboss.org/browse/RF-13584 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Assignee: Michal Petrov > Labels: needs-qe > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Some fixes were applied to the RichFaces 5 components that should be backported to RF 4.5. These include (but are not limited to) the fixes labelled "45x": > https://issues.jboss.org/browse/RF-13520?jql=project%3DRF%20and%20labels%... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13624) archetype kitchensink: error on the server side when a value in view of member detail is changed

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13624?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13624: ------------------------------- Fix Version/s: 4.3.8 > archetype kitchensink: error on the server side when a value in view of member detail is changed > ------------------------------------------------------------------------------------------------ > > Key: RF-13624 > URL: https://issues.jboss.org/browse/RF-13624 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.3.5, 4.3.6, 4.3.7 > Environment: EAP 6.2 > Reporter: Jiří Štefek > Priority: Minor > Fix For: 4.3.8 > > > # create project from archetype > {code} mvn archetype:generate -DarchetypeGroupId=org.richfaces.archetypes -DarchetypeArtifactId=richfaces-archetype-kitchensink -DarchetypeVersion=4.3.7.Final -DgroupId=org.richfaces.test -DartifactId=kitchensink-test -Denterprise=false > {code} > # build and deploy > # open http://localhost:8080/kitchensink-test/ > # view the first (already created) member > # click in the email/phone input and type a single letter there and you get this on the server side: > {code} > SEVERE [org.richfaces.log.Context] (http-/0.0.0.0:8080-2) /resources/components/memberForm.xhtml @47,78 value="#{cc.attrs.member.phoneNumber}": JBWEB006017: Target Unreachable, ''member'' returned null: javax.el.PropertyNotFoundException: /resources/components/memberForm.xhtml @47,78 value="#{cc.attrs.member.phoneNumber}": JBWEB006017: Target Unreachable, ''member'' returned null > at com.sun.faces.facelets.el.TagValueExpression.getType(TagValueExpression.java:100) [jsf-impl-2.1.19-redhat-2.jar:2.1.19-redhat-2] > at com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.getConvertedValue(HtmlBasicInputRenderer.java:95) [jsf-impl-2.1.19-redhat-2.jar:2.1.19-redhat-2] > at javax.faces.component.UIInput.getConvertedValue(UIInput.java:1030) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.component.UIInput.validate(UIInput.java:960) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.component.UIInput.executeValidate(UIInput.java:1233) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.component.UIInput.processValidators(UIInput.java:698) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at org.richfaces.context.PartialViewExecuteVisitCallback.visit(PartialViewExecuteVisitCallback.java:55) [richfaces-core-impl-4.3.7.Final.jar:4.3.7.Final] > at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:321) [richfaces-core-impl-4.3.7.Final.jar:4.3.7.Final] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1612) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.component.UINamingContainer.visitTree(UINamingContainer.java:163) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.component.UIForm.visitTree(UIForm.java:371) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at org.richfaces.context.ExtendedPartialViewContextImpl.executeComponents(ExtendedPartialViewContextImpl.java:278) [richfaces-core-impl-4.3.7.Final.jar:4.3.7.Final] > at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialExecutePhase(ExtendedPartialViewContextImpl.java:258) [richfaces-core-impl-4.3.7.Final.jar:4.3.7.Final] > at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:215) [richfaces-core-impl-4.3.7.Final.jar:4.3.7.Final] > at javax.faces.component.UIViewRoot.processValidators(UIViewRoot.java:1162) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at com.sun.faces.lifecycle.ProcessValidationsPhase.execute(ProcessValidationsPhase.java:76) [jsf-impl-2.1.19-redhat-2.jar:2.1.19-redhat-2] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.19-redhat-2.jar:2.1.19-redhat-2] > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.19-redhat-2.jar:2.1.19-redhat-2] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] > {code} > Everything seems to work fine, just this error on the server side. > ----- > And just one thing: why are there (in the member view popup) validated inputs, when the changed value is not updated in/to the data table? -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13602) Problem with ajax request in Internet Explorer 11

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13602?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13602: ------------------------------------ That's a pretty old release of Mojarra. Can you test that you still have a problem in a recent JBoss EAP release? That will at least help identify whether or not we are looking at an upstream problem. > Problem with ajax request in Internet Explorer 11 > ------------------------------------------------- > > Key: RF-13602 > URL: https://issues.jboss.org/browse/RF-13602 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: base functionality > Affects Versions: 4.0.0.Final > Environment: Windows 2008, JBoss AS 7.x > Reporter: Walter Maidub > Assignee: Juraj Húska > Labels: ie11, waiting_on_user > Attachments: Dear Juraj Húska.docx, ie11-1.png, ie11-2.png, ie11-3.png > > > I have a form with a FileUploader component (disabled) and a rich: select and this one is populated with 3 options, when one of them is selected in the managed bean a boolean variable is set to "true" and the FileUploader panel is updated to enable it. > {code} > <rich:select id="tipoArchivo" value="#{Bean.tipoArchivo}" > required="true" listWidth="320px" styleClass="rf-select-large-width"> > <f:selectItems value="#{Bean.Catalogo}" /> > <a4j:ajax event="selectitem" > execute="@this" > render="upload,seccionCarga" > listener="#{Bean.activarPanelCarga}" /> > </rich:select> > > <h:panelGrid columns="1"> > <h:panelGroup id="seccionCarga"> > <rich:panel bodyClass="info" titleStyleClass="rf-p-hdr" > > > <f:facet name="header"> > <h:outputText value="Detalle del archivo Cargado" /> > </f:facet> > > <h:panelGrid columns="2" columnClasses="columnOnCenter,columnOnCenter"> > <h:panelGroup style="text-align:center;display:block;width:550px;height:35px"> > <div align="center"> > <rich:fileUpload id="upload" > styleClass="top" > . > . > . > {code} > > The problem is that the FileUploader remains disabled, it is as if the panel had not been updated. > > Generally <a4j:ajax event="selectitem"> requests fail, this only in IE 11.0.4 (KB2925418) > > Currently there is a filter to ensure compatibility with IE 8. > > When the page is loaded in developer tools (F12) the IE8 compatibility option is set correctly. > > The configuration of the environment is: > Richfaces 4.0.0. > IE11 > JSF2 > Eclipse Kepler > > Is there any way to correct the problems with these ajax requests? -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13582) Revert the core package re-factoring

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13582?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13582: ------------------------------- Labels: needs-qe (was: ) > Revert the core package re-factoring > ------------------------------------ > > Key: RF-13582 > URL: https://issues.jboss.org/browse/RF-13582 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Assignee: Michal Petrov > Labels: needs-qe > Fix For: 4.5.0.Alpha3 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > To improve compatibility with RichFaces 4.3, the package re-factorings introduced should be reverted. These include (but are not limited to): > * .servlet (PushServlet, ResourceServlet) > * .push.cdi (@PUsh) > * .push. (TopicContext) > * FileUploadException > A good test for this would be to compile and run the RichFaces 4.3 showcase and metamer samples against RichFaces 4.5 looking for failures. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13608) Apply appropriate package and artifact names to the component poms

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13608?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13608: ------------------------------------ I suggest we rename the component artifacts (a4j, rich, parent) to: * {{org.richfaces.ui.a4j}} * {{org.richfaces.ui.rich}} * {{org.richfaces.ui.rparent}} Alternatives to {{ui}} are: * {{components}} * {{comps}} * _nothing_ IMO {{ui}} is the most clear. [~lfryc] do you have any input here? > Apply appropriate package and artifact names to the component poms > ------------------------------------------------------------------ > > Key: RF-13608 > URL: https://issues.jboss.org/browse/RF-13608 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The current package {{org.richfaces.compat}} is inappropriate for the RichFaces 4.5 release. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13608) Apply appropriate package and artifact names to the component poms

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13608?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-13608: ---------------------------------- Assignee: Brian Leathem > Apply appropriate package and artifact names to the component poms > ------------------------------------------------------------------ > > Key: RF-13608 > URL: https://issues.jboss.org/browse/RF-13608 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The current package {{org.richfaces.compat}} is inappropriate for the RichFaces 4.5 release. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13623) Merge components/pom with components/parent/pom in 4.5.x

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13623?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-13623. -------------------------------- Resolution: Done > Merge components/pom with components/parent/pom in 4.5.x > -------------------------------------------------------- > > Key: RF-13623 > URL: https://issues.jboss.org/browse/RF-13623 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.5.0.Alpha2 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > components/pom.xml doesn't contain any useful information so it should be merged with components/parent/pom.xml. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13623) Merge components/pom with components/parent/pom in 4.5.x

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13623?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-13623: ---------------------------------- Assignee: Brian Leathem > Merge components/pom with components/parent/pom in 4.5.x > -------------------------------------------------------- > > Key: RF-13623 > URL: https://issues.jboss.org/browse/RF-13623 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.5.0.Alpha2 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > components/pom.xml doesn't contain any useful information so it should be merged with components/parent/pom.xml. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13623) Merge components/pom with components/parent/pom in 4.5.x

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13623?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13623: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 1 > Merge components/pom with components/parent/pom in 4.5.x > -------------------------------------------------------- > > Key: RF-13623 > URL: https://issues.jboss.org/browse/RF-13623 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.5.0.Alpha2 > Reporter: Pavol Pitonak > Fix For: 4.5.0.Alpha3 > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > components/pom.xml doesn't contain any useful information so it should be merged with components/parent/pom.xml. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues May 2014