[JBoss JIRA] (RF-13154) a4j:push fails with CNFE for org.apache.coyote.http11.upgrade.UpgradeInbound on latest EAP 6
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13154?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13154:
-------------------------------
Workaround Description:
A workaround then is to disable WebSockets use in Atmosphere with the following web.xml configuration:
{code}
<context-param>
<param-name>org.atmosphere.useWebSocket</param-name>
<param-value>false</param-value>
</context-param>
{code}
Workaround: Workaround Exists
> a4j:push fails with CNFE for org.apache.coyote.http11.upgrade.UpgradeInbound on latest EAP 6
> --------------------------------------------------------------------------------------------
>
> Key: RF-13154
> URL: https://issues.jboss.org/browse/RF-13154
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.3
> Environment: EAP 6.1.1.ER7
> Reporter: Ken Finnigan
> Fix For: 4.3.4
>
>
> When accessing a4j:push example in showcase on EAP 6.1.1.ER7 the network tab of the developer console in Chrome shows failed network attempts for richfaces push and the following exception in the server logs:
> {code}
> 15:21:29,295 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[AutoRegisteredPushServlet]] (http-/127.0.0.1:8080-2) JBWEB000236: Servlet.service() for servlet AutoRegisteredPushServlet threw exception: java.lang.ClassNotFoundException: org.apache.coyote.http11.upgrade.UpgradeInbound from [Module "deployment.richfaces-showcase-4.3.3.Final-jbas71.war:main" from Service Module Loader]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.2.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.2.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.2.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.2.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.2.Final-redhat-1]
> at org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.service(Tomcat7AsyncSupportWithWebSocket.java:59) [atmosphere-runtime-1.0.10.jar:1.0.10]
> at org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:1370) [atmosphere-runtime-1.0.10.jar:1.0.10]
> at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:293) [atmosphere-runtime-1.0.10.jar:1.0.10]
> at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:279) [atmosphere-runtime-1.0.10.jar:1.0.10]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.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.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 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:724) [rt.jar:1.7.0_25]
> {code}
> Running the exact same showcase example war on EAP 6.1.0.GA works fine.
--
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, 4 months
[JBoss JIRA] (RF-13154) a4j:push fails with CNFE for org.apache.coyote.http11.upgrade.UpgradeInbound on latest EAP 6
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13154?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13154:
-------------------------------
Workaround Description:
Disable WebSockets use in Atmosphere with the following web.xml configuration:
{code}
<context-param>
<param-name>org.atmosphere.useWebSocket</param-name>
<param-value>false</param-value>
</context-param>
{code}
was:
A workaround then is to disable WebSockets use in Atmosphere with the following web.xml configuration:
{code}
<context-param>
<param-name>org.atmosphere.useWebSocket</param-name>
<param-value>false</param-value>
</context-param>
{code}
> a4j:push fails with CNFE for org.apache.coyote.http11.upgrade.UpgradeInbound on latest EAP 6
> --------------------------------------------------------------------------------------------
>
> Key: RF-13154
> URL: https://issues.jboss.org/browse/RF-13154
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.3
> Environment: EAP 6.1.1.ER7
> Reporter: Ken Finnigan
> Fix For: 4.3.4
>
>
> When accessing a4j:push example in showcase on EAP 6.1.1.ER7 the network tab of the developer console in Chrome shows failed network attempts for richfaces push and the following exception in the server logs:
> {code}
> 15:21:29,295 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[AutoRegisteredPushServlet]] (http-/127.0.0.1:8080-2) JBWEB000236: Servlet.service() for servlet AutoRegisteredPushServlet threw exception: java.lang.ClassNotFoundException: org.apache.coyote.http11.upgrade.UpgradeInbound from [Module "deployment.richfaces-showcase-4.3.3.Final-jbas71.war:main" from Service Module Loader]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.2.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.2.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.2.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.2.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.2.Final-redhat-1]
> at org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.service(Tomcat7AsyncSupportWithWebSocket.java:59) [atmosphere-runtime-1.0.10.jar:1.0.10]
> at org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:1370) [atmosphere-runtime-1.0.10.jar:1.0.10]
> at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:293) [atmosphere-runtime-1.0.10.jar:1.0.10]
> at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:279) [atmosphere-runtime-1.0.10.jar:1.0.10]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.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.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 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:724) [rt.jar:1.7.0_25]
> {code}
> Running the exact same showcase example war on EAP 6.1.0.GA works fine.
--
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, 4 months
[JBoss JIRA] (RF-13155) Unable to trigger hidden FileUpload in IE with an associated Label: missing Id on generated <input type=“file“>
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13155?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13155:
-------------------------------
Labels: low_hanging_fruit (was: )
> Unable to trigger hidden FileUpload in IE with an associated Label: missing Id on generated <input type=“file“>
> ---------------------------------------------------------------------------------------------------------------
>
> Key: RF-13155
> URL: https://issues.jboss.org/browse/RF-13155
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.3.2
> Environment: Internet Explorer 8
> Reporter: Benoit Pflieger
> Priority: Minor
> Labels: low_hanging_fruit
>
> A hidden FileUpload was triggered by clicking an associated label to the generated tag <input type=“file“>.
> That's the security workaround to trigger an <input type=“file“> under Internet Explorer.
> It worked with Richfaces 3.3.
> This workaround can't be achieved anymore with Richfaces 4.3.2 because the <input type=“file“> is only generated without the attribute "id".
--
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, 4 months
[JBoss JIRA] (RF-13127) onvalid and oninvalide pass wrong element when using rich:element with String field
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13127?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-13127:
----------------------------------
Assignee: Pavol Pitonak
QA, please verify this issue.
> onvalid and oninvalide pass wrong element when using rich:element with String field
> -----------------------------------------------------------------------------------
>
> Key: RF-13127
> URL: https://issues.jboss.org/browse/RF-13127
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.3
> Reporter: Louis Parisi
> Assignee: Pavol Pitonak
> Attachments: JSFTemplate.zip, richfaces.zip
>
>
> I have a bean iterated in a datatable. Using the rich:validator on fields in the bean I am executing javascript when a field is validated and apply styling based on valid or invalid state. The code below returns the correct element when the underlying field is a BigDecimal but intermittently returns the element from row zero and sometimes another rown when the field is a String. If I just reference a String vs. BigDecimal and display the element passed to the javascript I get form:myTable:4:myField for a BigDecimal field and always form:myTable:0:myField no matter the row for a String field.
> {code}
> <h:inputText id="vendor" value="#{car.vendor}" valueChangeListener="#{car.valueChanged}">
> <rich:validator oninvalid="valueModified(#{rich:element('vendor')}, false)"
> onvalid="valueModified(#{rich:element('vendor')}, true)"/>
> </h:inputText>
> {code}
> {code}
> <script>
> function valueModified(element, valid) {
> // use element.style rather than jQuery as it
> // does not set entire background
> alert("valueModified: " + element.id + " | valid: " + valid);
> element.style.background='yellow';
> if (valid) {
> jQuery(element).css("border-color", "lightgray");
> } else {
> jQuery(element).css("border-color", "red");
> }
> }
> </script>
> {code}
> Some other tests I did while trying to debug are:
> * I passed the rowKeyVar to a javascript method in the onvalid event and it passed the correct row for a BigDecimal and always zero for a String field.
> * The oncomplete event of the validator does not seem to fire for a String field but does for a BigDecimal 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
12 years, 4 months
[JBoss JIRA] (RF-13127) onvalid and oninvalide pass wrong element when using rich:element with String field
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13127?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13127:
------------------------------------
Note: onvalid and oninvalid were added in RF-12457 with the commit:
https://github.com/richfaces4/components/commit/d04ba1dc12372765efc196a2e...
> onvalid and oninvalide pass wrong element when using rich:element with String field
> -----------------------------------------------------------------------------------
>
> Key: RF-13127
> URL: https://issues.jboss.org/browse/RF-13127
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.3
> Reporter: Louis Parisi
> Attachments: JSFTemplate.zip, richfaces.zip
>
>
> I have a bean iterated in a datatable. Using the rich:validator on fields in the bean I am executing javascript when a field is validated and apply styling based on valid or invalid state. The code below returns the correct element when the underlying field is a BigDecimal but intermittently returns the element from row zero and sometimes another rown when the field is a String. If I just reference a String vs. BigDecimal and display the element passed to the javascript I get form:myTable:4:myField for a BigDecimal field and always form:myTable:0:myField no matter the row for a String field.
> {code}
> <h:inputText id="vendor" value="#{car.vendor}" valueChangeListener="#{car.valueChanged}">
> <rich:validator oninvalid="valueModified(#{rich:element('vendor')}, false)"
> onvalid="valueModified(#{rich:element('vendor')}, true)"/>
> </h:inputText>
> {code}
> {code}
> <script>
> function valueModified(element, valid) {
> // use element.style rather than jQuery as it
> // does not set entire background
> alert("valueModified: " + element.id + " | valid: " + valid);
> element.style.background='yellow';
> if (valid) {
> jQuery(element).css("border-color", "lightgray");
> } else {
> jQuery(element).css("border-color", "red");
> }
> }
> </script>
> {code}
> Some other tests I did while trying to debug are:
> * I passed the rowKeyVar to a javascript method in the onvalid event and it passed the correct row for a BigDecimal and always zero for a String field.
> * The oncomplete event of the validator does not seem to fire for a String field but does for a BigDecimal 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
12 years, 4 months
[JBoss JIRA] (RF-13035) Simpleapp Archetype: mobile version shows modal dialog
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13035?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13035:
------------------------------------
I am not able to reproduce this with the staged 4.3.4.Final simpleapp archetype.
I generate the archetype with the command:
{code}
mvn archetype:generate -DarchetypeGroupId=org.richfaces.archetypes -DarchetypeArtifactId=richfaces-archetype-simpleapp -DarchetypeVersion=4.3.4.Final -DgroupId=org.richfaces.test -DartifactId=simpleapp-test -Denterprise=false -Dmobile-optimized=false
{code}
with either mobileOptimzed={true|false}
Pavol can you confirm that you are still able to reproduce this issue, and provide instructions on how to do so?
> Simpleapp Archetype: mobile version shows modal dialog
> -------------------------------------------------------
>
> Key: RF-13035
> URL: https://issues.jboss.org/browse/RF-13035
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: archetype
> Affects Versions: 4.1.0.Final, 5.0.0.Alpha1
> Reporter: Jan Papousek
> Assignee: Brian Leathem
> Fix For: 4.3.4, 5.0.0.Alpha2
>
> Attachments: modal-iphone.png, richfaces-simpleapp-jee6.war, simpleapp-modal.png
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> When the simpleapp archetype is built with "-Dmobile-optimized=true", the welcome page shows modal dialog (see 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
12 years, 4 months
[JBoss JIRA] (RF-13046) EDT in EDT: when @frozenColumns is equal to number of columns then there is no vertical scroller in EDT
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13046?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-13046.
--------------------------------
Labels: needs-qe (was: )
Resolution: Done
I prevented the EDT from claiming nested EDT parts as its own parts.
Note: This may have a significant (positive impact) wherever nested EDTs are used. @QE please check if any other existing nested EDT issues are resolved by this fix.
> EDT in EDT: when @frozenColumns is equal to number of columns then there is no vertical scroller in EDT
> -------------------------------------------------------------------------------------------------------
>
> Key: RF-13046
> URL: https://issues.jboss.org/browse/RF-13046
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> GlassFish Server Open Source Edition 3.1.2.2
> Java(TM) SE Runtime Environment 1.7.0_21-b11 @ Linux
> Firefox 18.0 @ Linux x86_64
> Reporter: Jiří Štefek
> Assignee: Brian Leathem
> Labels: needs-qe
> Fix For: 4.3.4
>
> Attachments: EDTinEDTmaxFrozenColumnsNoScrollers.png, EDTinEDTmaxFrozenColumnsScrollersAfterColumnReposition.png, EDTinEDTWhenNoFrozenColsOrWhenFrozenColsLesserThanMaxCols.png
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> EDT(1st) in EDT(2nd), when @frozenColumns (of 1st) is equal to number of columns (of 1st), then there is no vertical scroller in EDT (1st). But when you reorganize the columns (of 1st), the scroller and the 'footer' facet appears (1st).
--
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, 4 months
[JBoss JIRA] (RF-13156) Custom sorting on extended datatable not working.
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13156?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13156:
------------------------------------
I believe this is a duplicate of RF-12943. Can you build the latest RF 4 SNAPSHOT and test it? Alternatively you can grab a staged release from the JBoss Nexus staging repository:
https://repository.jboss.org/nexus/content/groups/staging/
(Note however that our QE has identified some bugs with the staged release, so you won't want to use it in production).
You could also just wait until 4.3.4 is released to check.
> Custom sorting on extended datatable not working.
> -------------------------------------------------
>
> Key: RF-13156
> URL: https://issues.jboss.org/browse/RF-13156
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.3
> Environment: Oracle Glassfish 3.1.2 - JEE 6 Full Profile
> Reporter: Fabio Turizo
> Labels: extendedDataTable, sorting
>
> Custom sorting on a extended datatable is not working well. With a extended data table configured with this layout:
> {code:xml}
> <html xmlns="http://www.w3.org/1999/xhtml"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:f="http://java.sun.com/jsf/core"
> xmlns:a4j="http://richfaces.org/a4j"
> xmlns:rich="http://richfaces.org/rich">
> <h:head>
> <title>Titulo</title>
> </h:head>
> <h:body>
> <h:form>
> <h:panelGrid cellpadding="5" cellspacing="5" columns="4" width="100%">
> <f:facet name="footer">
> <h:panelGrid cellspacing="10" columns="2" width="80%">
> <a4j:commandButton actionListener="#{consultaFactibilidad.consultarDocumentos}"
> execute="this"
> render="documentos"
> value="Buscar"
> styleClass="boton"/>
> </h:panelGrid>
> </f:facet>
> </h:panelGrid>
> <rich:extendedDataTable var="documento"
> value="#{consultaFactibilidad.documentos}"
> id="documentos">
> <rich:column id="formato" width="200px"
> sortBy="#{documento.formato.nombreCalificado}"
> sortType="custom" sortOrder="#{controlOrdenTablas.orden}">
> <f:facet name="header">
> <a4j:commandLink execute="@this"
> action="#{controlOrdenTablas.ordenar}"
> render="documentos">
> <h:outputLabel value="Formato" />
> </a4j:commandLink>
> </f:facet>
> <h:outputText value="#{documento.formato.nombreCalificado}"/>
> </rich:column>
> </rich:extendedDataTable>
> </h:form>
> </h:body>
> </html>{code}
> When the user clicks on the link for the only column on the table the table sorts correctly ONLY the first time, the next click simply doesn't sort the data. No error messages on the server log, no error messages on a a4j:log either. The next time stops working completely. This only happens after the value collection is retrieved on the action listener {code}#{consultaFactibilidad.consultarDocumentos}{code} is called. When the data is retrieved before the page load, say on the postconstruct event listener on the backing bean, then the sort works correctly all times. Finally this ONLY happens with the extended datatable. It doesn't happen with a simple datatable.
--
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, 4 months