[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 commented on RF-13154:
------------------------------------
Hmm, aside from that mailing list announcement, I cannot find any other mention of the AtmosphereLegacyServlet.
----
Looking more closely at what is triggering the Tomcat7 websocket from Atmosphere, I can see that tomcat checks for the presence of a tomcat7 class here:
https://github.com/Atmosphere/atmosphere/blob/atmosphere-1.0.x/modules/cp...
https://github.com/Atmosphere/atmosphere/blob/atmosphere-1.0.x/modules/cp...
And this class is included in JBoss Web 7.2.2.Final:
http://anonsvn.jboss.org/repos/jbossweb/tags/JBOSSWEB_7_2_2_FINAL/src/mai...
[~jfclere] Is there a reason the Tomcat7 websocket class is included in JBossWeb 7.2.2.Final?
Not only does it's presence break Richfaces push, but it's going to break push for *any* JBoss EAP application that uses the Atmosphere library.
> 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, 3 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:
------------------------------------
Release 4.3.4 is currently undergoing QA, and will be released shortly.
> Custom sorting on extended datatable not working.
> -------------------------------------------------
>
> Key: RF-13156
> URL: https://issues.jboss.org/browse/RF-13156
> Project: RichFaces
> Issue Type: Bug
> 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, waiting_on_user
>
> 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, 3 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 resolved RF-13156.
--------------------------------
Labels: extendedDataTable sorting (was: extendedDataTable sorting waiting_on_user)
Resolution: Duplicate Issue
> Custom sorting on extended datatable not working.
> -------------------------------------------------
>
> Key: RF-13156
> URL: https://issues.jboss.org/browse/RF-13156
> Project: RichFaces
> Issue Type: Bug
> 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, 3 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 updated RF-13156:
-------------------------------
Component/s: component-tables
> Custom sorting on extended datatable not working.
> -------------------------------------------------
>
> Key: RF-13156
> URL: https://issues.jboss.org/browse/RF-13156
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> 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, 3 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 commented on RF-13154:
------------------------------------
We are currently using AtmosphereServlet:
https://github.com/richfaces4/core/blob/master/impl/src/main/java/org/ric...
Here's the announcement for AtmosphereLegacyServlet:
http://atmosphere-framework.2306103.n4.nabble.com/Vote-1-1-Dropping-Tomca...
{quote}
I'm ready to drop native support for Tomcat 6/7 and JBoss Web. The
changes would be simple. An application that wants to be deployed in
Tomcat6/Tomcat7/JBossX will need to use the
AtmosphereLegacyServlet
where normal web app would just use the
AtmosphereServlet
like before? That would remove, by default, all the
atmosphere-compat-XXX jar file.
{quote}
I'll try switching to the AtmosphereLegacyServlet and see if that resolves the problem.
> 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, 3 months
[JBoss JIRA] (RF-13156) Custom sorting on extended datatable not working.
by Fabio Turizo (JIRA)
[ https://issues.jboss.org/browse/RF-13156?page=com.atlassian.jira.plugin.s... ]
Fabio Turizo commented on RF-13156:
-----------------------------------
Ok, having this tested with the 4.3.4 version the bug seems to be gone and the sorting works as expected. In accordance to the roadmap when is this version expected to be released?
> Custom sorting on extended datatable not working.
> -------------------------------------------------
>
> Key: RF-13156
> URL: https://issues.jboss.org/browse/RF-13156
> Project: RichFaces
> Issue Type: Bug
> 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, waiting_on_user
>
> 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, 3 months
[JBoss JIRA] (RF-13159) Add Maven compiler properties and remove Maven plugin from the the quickstart POM files
by Sande Gilda (JIRA)
Sande Gilda created RF-13159:
--------------------------------
Summary: Add Maven compiler properties and remove Maven plugin from the the quickstart POM files
Key: RF-13159
URL: https://issues.jboss.org/browse/RF-13159
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: examples
Reporter: Sande Gilda
1. Make sure the following properties are defined in each quickstart POM file:
<maven.compiler.target>1.6</maven.compiler.target>
<maven.compiler.source>1.6</maven.compiler.source>
2. Remove the Maven plugin from each quickstart POM file:
- <!-- Compiler plugin enforces Java 1.6 compatibility and activates annotation processors -->
- <plugin>
- <artifactId>maven-compiler-plugin</artifactId>
- <version>${version.compiler.plugin}</version>
- <configuration>
- <source>${maven.compiler.source}</source>
- <target>${maven.compiler.target}</target>
- </configuration>
- </plugin>
--
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, 3 months