[JBoss JIRA] (RF-13791) Push in Showcase with EAP 6.2
by Matej Novotny (JIRA)
Matej Novotny created RF-13791:
----------------------------------
Summary: Push in Showcase with EAP 6.2
Key: RF-13791
URL: https://issues.jboss.org/browse/RF-13791
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-a4j-core
Affects Versions: 4.5.0.Alpha3
Environment: Showcase 4.5.x
EAP 6.2
Any browser
Reporter: Matej Novotny
This issue happens since the upgrade of Atmosphere.
Once you attempt to deploy Showcase to EAP 6.2 and access a push sample page, you get the following error in server console:
{code}
14:28:20,881 ERROR [org.atmosphere.container.JBossWebCometSupport] (http-/127.0.0.1:8080-5) HttpEvent is null, JBoss APR Not Properly installed
14:28:20,881 WARN [org.atmosphere.cpr.AtmosphereFramework] (http-/127.0.0.1:8080-5) Failed using comet support: org.atmosphere.container.JBossWebCometSupport, error: JBoss failed to detect this is a Comet application because the APR Connector is not enabled.
Make sure atmosphere-compat-jboss.jar is not under your WEB-INF/lib and You must use the atmosphere-native-runtime dependency in order to use native Comet Support
there is no context.xml under WEB-INF Is the NIO or APR Connector enabled?
14:28:20,881 ERROR [org.atmosphere.cpr.AtmosphereFramework] (http-/127.0.0.1:8080-5) If you have more than one Connector enabled, make sure they both use the same protocol, e.g NIO/APR or HTTP for all. If not, org.atmosphere.container.BlockingIOCometSupport will be used and cannot be changed.: java.lang.IllegalStateException: JBoss failed to detect this is a Comet application because the APR Connector is not enabled.
Make sure atmosphere-compat-jboss.jar is not under your WEB-INF/lib and You must use the atmosphere-native-runtime dependency in order to use native Comet Support
there is no context.xml under WEB-INF
at org.atmosphere.container.JBossWebCometSupport.<clinit>(JBossWebCometSupport.java:49) [atmosphere-runtime-2.2.0.jar:2.2.0]
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_25]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_25]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_25]
at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_25]
at org.atmosphere.cpr.DefaultAsyncSupportResolver.newCometSupport(DefaultAsyncSupportResolver.java:225) [atmosphere-runtime-2.2.0.jar:2.2.0]
at org.atmosphere.cpr.DefaultAsyncSupportResolver.resolveMultipleNativeSupportConflict(DefaultAsyncSupportResolver.java:318) [atmosphere-runtime-2.2.0.jar:2.2.0]
at org.atmosphere.cpr.DefaultAsyncSupportResolver.resolveNativeCometSupport(DefaultAsyncSupportResolver.java:302) [atmosphere-runtime-2.2.0.jar:2.2.0]
at org.atmosphere.cpr.DefaultAsyncSupportResolver.resolve(DefaultAsyncSupportResolver.java:281) [atmosphere-runtime-2.2.0.jar:2.2.0]
at org.atmosphere.cpr.AtmosphereFramework.autoDetectContainer(AtmosphereFramework.java:1811) [atmosphere-runtime-2.2.0.jar:2.2.0]
at org.atmosphere.cpr.AtmosphereFramework.init(AtmosphereFramework.java:872) [atmosphere-runtime-2.2.0.jar:2.2.0]
at org.atmosphere.cpr.AtmosphereFramework.init(AtmosphereFramework.java:765) [atmosphere-runtime-2.2.0.jar:2.2.0]
at org.atmosphere.cpr.AtmosphereServlet.configureFramework(AtmosphereServlet.java:101) [atmosphere-runtime-2.2.0.jar:2.2.0]
at org.atmosphere.cpr.AtmosphereServlet.init(AtmosphereServlet.java:80) [atmosphere-runtime-2.2.0.jar:2.2.0]
at org.richfaces.webapp.PushServlet.init(PushServlet.java:67) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1194) [jbossweb-7.3.2.Final-redhat-1.jar:7.3.2.Final-redhat-1]
at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:950) [jbossweb-7.3.2.Final-redhat-1.jar:7.3.2.Final-redhat-1]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:151) [jbossweb-7.3.2.Final-redhat-1.jar:7.3.2.Final-redhat-1]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.3.2.Final-redhat-1.jar:7.3.2.Final-redhat-1]
at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1]
at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1]
at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.3.2.Final-redhat-1.jar:7.3.2.Final-redhat-1]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.3.2.Final-redhat-1.jar:7.3.2.Final-redhat-1]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.3.2.Final-redhat-1.jar:7.3.2.Final-redhat-1]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.3.2.Final-redhat-1.jar:7.3.2.Final-redhat-1]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.3.2.Final-redhat-1.jar:7.3.2.Final-redhat-1]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.3.2.Final-redhat-1.jar:7.3.2.Final-redhat-1]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.3.2.Final-redhat-1.jar:7.3.2.Final-redhat-1]
at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
14:28:20,885 WARN [org.atmosphere.cpr.AtmosphereFramework] (http-/127.0.0.1:8080-5) Using org.atmosphere.container.BlockingIOCometSupport
{code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (RF-13786) Showcase - disable built in sorting/filtering for custom sorting/filtering DataTable examples
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13786?page=com.atlassian.jira.plugin.s... ]
Juraj Húska commented on RF-13786:
----------------------------------
Linked PR which disables built in sorting/filtering for Arrangeable example.
> Showcase - disable built in sorting/filtering for custom sorting/filtering DataTable examples
> ---------------------------------------------------------------------------------------------
>
> Key: RF-13786
> URL: https://issues.jboss.org/browse/RF-13786
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: showcase
> Affects Versions: 4.5.0.Beta1
> Reporter: Juraj Húska
> Assignee: Juraj Húska
>
> {{rich:dataTable}} has enabled built in sorting/filtering feature as well as {{extendedDataTable}}.
> It needs to be switched off for examples where custom sorting/filtering is showcased.
> {{filterType="custom"}} attribute has to be set on {{rich:column}} s
> and also
> {{sortingType="custom"}}.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (RF-13786) Showcase - disable built in sorting/filtering for custom sorting/filtering DataTable examples
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13786?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-13786:
-----------------------------
Description:
{{rich:dataTable}} has enabled built in sorting/filtering feature as well as {{extendedDataTable}}.
It needs to be switched off for examples where custom sorting/filtering is showcased.
{{filterType="custom"}} attribute has to be set on {{rich:column}} s
and also
{{sortingType="custom"}}.
was:
{{rich:dataTable}} has enabled build in sorting/filtering feature as well as {{extendedDataTable}}.
It needs to be switched off for examples where custom sorting/filtering is showcased.
{{filterType="custom"}} attribute has to be set on {{rich:column}} s
and also
{{sortingType="custom"}}.
> Showcase - disable built in sorting/filtering for custom sorting/filtering DataTable examples
> ---------------------------------------------------------------------------------------------
>
> Key: RF-13786
> URL: https://issues.jboss.org/browse/RF-13786
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: showcase
> Affects Versions: 4.5.0.Beta1
> Reporter: Juraj Húska
> Assignee: Juraj Húska
>
> {{rich:dataTable}} has enabled built in sorting/filtering feature as well as {{extendedDataTable}}.
> It needs to be switched off for examples where custom sorting/filtering is showcased.
> {{filterType="custom"}} attribute has to be set on {{rich:column}} s
> and also
> {{sortingType="custom"}}.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (RF-13786) Showcase - disable built in sorting/filtering for custom sorting/filtering DataTable examples
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13786?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-13786:
-----------------------------
Summary: Showcase - disable built in sorting/filtering for custom sorting/filtering DataTable examples (was: Showcase - disable build in sorting/filtering for custom sorting/filtering DataTable examples)
> Showcase - disable built in sorting/filtering for custom sorting/filtering DataTable examples
> ---------------------------------------------------------------------------------------------
>
> Key: RF-13786
> URL: https://issues.jboss.org/browse/RF-13786
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: showcase
> Affects Versions: 4.5.0.Beta1
> Reporter: Juraj Húska
> Assignee: Juraj Húska
>
> {{rich:dataTable}} has enabled build in sorting/filtering feature as well as {{extendedDataTable}}.
> It needs to be switched off for examples where custom sorting/filtering is showcased.
> {{filterType="custom"}} attribute has to be set on {{rich:column}} s
> and also
> {{sortingType="custom"}}.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (RF-13786) Showcase - disable build in sorting/filtering for custom sorting/filtering DataTable examples
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13786?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-13786:
-----------------------------
Description:
{{rich:dataTable}} has enabled build in sorting/filtering feature as well as {{extendedDataTable}}.
It needs to be switched off for examples where custom sorting/filtering is showcased.
{{filterType="custom"}} attribute has to be set on {{rich:column}} s
and also
{{sortingType="custom"}}.
was:
{{rich:dataTable}} has enabled build in sorting/filtering feature as well as {{extendedDataTable}}.
It needs to be switched off for examples where custom sorting/filtering is showcased.
{{filterType="custom"}} attribute has to be set on {{rich:column}} s
> Showcase - disable build in sorting/filtering for custom sorting/filtering DataTable examples
> ---------------------------------------------------------------------------------------------
>
> Key: RF-13786
> URL: https://issues.jboss.org/browse/RF-13786
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: showcase
> Affects Versions: 4.5.0.Beta1
> Reporter: Juraj Húska
> Assignee: Juraj Húska
>
> {{rich:dataTable}} has enabled build in sorting/filtering feature as well as {{extendedDataTable}}.
> It needs to be switched off for examples where custom sorting/filtering is showcased.
> {{filterType="custom"}} attribute has to be set on {{rich:column}} s
> and also
> {{sortingType="custom"}}.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (RF-13790) Showcase - dataTable Styling example - broken styling after built in sorting/filtering is enabled
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13790?page=com.atlassian.jira.plugin.s... ]
Juraj Húska edited comment on RF-13790 at 8/19/14 8:18 AM:
-----------------------------------------------------------
My question is how do we want to change this ?
Do we want filtering enabled in this sample ? IMHO it is better to not have it. There are other samples which demonstrates build in sorting, filtering. This example should demonstrate the styling option.
I can send a PR once I know what is the desired result ...
was (Author: jhuska):
My question is how do we want to change this ?
Do we want filtering enabled in this sample ? IMHO it is better to not have it. There are other samples which demonstrates build in sorting, filtering. This example should demonstrate the styling option.
> Showcase - dataTable Styling example - broken styling after built in sorting/filtering is enabled
> -------------------------------------------------------------------------------------------------
>
> Key: RF-13790
> URL: https://issues.jboss.org/browse/RF-13790
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: showcase
> Affects Versions: 4.5.0.Beta1
> Reporter: Juraj Húska
>
> Please checkout the screenshot to see how the styling of the table is broken (every odd row should have different background color).
> There are multiple wrong places in the facelet for this example, which causes this break of styling.
> * code for first column uses attribute {{accept}}, which is not defined for RF4, there should be {{filter}} instead
> * there is typo in EL to reference a bean in the same place, there is {{carsFiteringBean}}, instead of {{carsFilteringBean}}
> * when I change this two things, the filtering does not work either, because in the referenced filter implementation, the {{mileage}} or {{vendor}} is always {{null}}.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (RF-13790) Showcase - dataTable Styling example - broken styling after built in sorting/filtering is enabled
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13790?page=com.atlassian.jira.plugin.s... ]
Juraj Húska edited comment on RF-13790 at 8/19/14 8:17 AM:
-----------------------------------------------------------
My question is how do we want to change this ?
Do we want filtering enabled in this sample ? IMHO it is better to not have it. There are other samples which demonstrates build in sorting, filtering. This example should demonstrate the styling option.
was (Author: jhuska):
My question is how do we want to change this ?
Do we want filtering enabled in this sample ? IMHO it is better to not have it. There are other sample which demonstrates build in sorting, filtering. This example should demonstrate the styling option.
> Showcase - dataTable Styling example - broken styling after built in sorting/filtering is enabled
> -------------------------------------------------------------------------------------------------
>
> Key: RF-13790
> URL: https://issues.jboss.org/browse/RF-13790
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: showcase
> Affects Versions: 4.5.0.Beta1
> Reporter: Juraj Húska
>
> Please checkout the screenshot to see how the styling of the table is broken (every odd row should have different background color).
> There are multiple wrong places in the facelet for this example, which causes this break of styling.
> * code for first column uses attribute {{accept}}, which is not defined for RF4, there should be {{filter}} instead
> * there is typo in EL to reference a bean in the same place, there is {{carsFiteringBean}}, instead of {{carsFilteringBean}}
> * when I change this two things, the filtering does not work either, because in the referenced filter implementation, the {{mileage}} or {{vendor}} is always {{null}}.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (RF-13790) Showcase - dataTable Styling example - broken styling after built in sorting/filtering is enabled
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13790?page=com.atlassian.jira.plugin.s... ]
Juraj Húska commented on RF-13790:
----------------------------------
My question is how do we want to change this ?
Do we want filtering enabled in this sample ? IMHO it is better to not have it. There are other sample which demonstrates build in sorting, filtering. This example should demonstrate the styling option.
> Showcase - dataTable Styling example - broken styling after built in sorting/filtering is enabled
> -------------------------------------------------------------------------------------------------
>
> Key: RF-13790
> URL: https://issues.jboss.org/browse/RF-13790
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: showcase
> Affects Versions: 4.5.0.Beta1
> Reporter: Juraj Húska
>
> Please checkout the screenshot to see how the styling of the table is broken (every odd row should have different background color).
> There are multiple wrong places in the facelet for this example, which causes this break of styling.
> * code for first column uses attribute {{accept}}, which is not defined for RF4, there should be {{filter}} instead
> * there is typo in EL to reference a bean in the same place, there is {{carsFiteringBean}}, instead of {{carsFilteringBean}}
> * when I change this two things, the filtering does not work either, because in the referenced filter implementation, the {{mileage}} or {{vendor}} is always {{null}}.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (RF-13789) Push component with Wildfly 8.1
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RF-13789?page=com.atlassian.jira.plugin.s... ]
Matej Novotny updated RF-13789:
-------------------------------
Steps to Reproduce:
With Metamer:
* Start Wildfly 8.1
* Deploy Metamer
* Go to [this page|http://localhost:8080/metamer/faces/components/a4jPush/simple.xhtml]
* Click the 'Message Producer' link on that page
** If you are using FF as browser attempt to send a message to get the error
* See server console for error
Or you can reproduce it with the Showcase sample:
* Start Wildfly
* Deploy Showcase
* *Using Chrome* go to [this page|http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=push&sample=pushCdi&skin=blueSky]
** I managed to reproduce it with FF too but I am unable to do it again this way
* See server console for errors
was:
With Metamer:
* Start Wildfly 8.1
* Deploy Metamer
* Go to [this page|http://localhost:8080/metamer/faces/components/a4jPush/simple.xhtml]
* Click the 'Message Producer' link on that page
* See server console for error
Or you can reproduce it with the Showcase sample:
* Start Wildfly
* Deploy Showcase
* Go to [this page|http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=push&sample=pushCdi&skin=blueSky]
* See server console for errors
> Push component with Wildfly 8.1
> -------------------------------
>
> Key: RF-13789
> URL: https://issues.jboss.org/browse/RF-13789
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.5.0.Alpha3
> Environment: RichFaces 4.5.0-SNAPSHOT
> Metamer 4.5.0-SNAPSHOT
> Mojarra 2.2.6-jbossorg-4
> JBoss AS 8.1.0.Final
> Java(TM) SE Runtime Environment 1.7.0_25-b15 @ Linux
> Chrome 36.0.1985.143 @ Linux x86_64
> Reporter: Matej Novotny
>
> When you deploy Metamer (or Showcase) 4.5.x to Wildfly 8.1, access the push sample page and attempt to switch to Message Producer you get the following error:
> {code}
> 13:59:19,459 ERROR [stderr] (default task-55) Exception in thread "default task-55" java.lang.RuntimeException: java.io.IOException: Broken pipe
> 13:59:19,459 ERROR [stderr] (default task-55) at io.undertow.servlet.spec.HttpServletResponseImpl.responseDone(HttpServletResponseImpl.java:527)
> 13:59:19,460 ERROR [stderr] (default task-55) at io.undertow.servlet.spec.AsyncContextImpl$3.run(AsyncContextImpl.java:294)
> 13:59:19,460 ERROR [stderr] (default task-55) at io.undertow.servlet.spec.AsyncContextImpl$6.run(AsyncContextImpl.java:432)
> 13:59:19,460 ERROR [stderr] (default task-55) at io.undertow.servlet.spec.AsyncContextImpl$TaskDispatchRunnable.run(AsyncContextImpl.java:517)
> 13:59:19,461 ERROR [stderr] (default task-55) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> 13:59:19,461 ERROR [stderr] (default task-55) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> 13:59:19,461 ERROR [stderr] (default task-55) at java.lang.Thread.run(Thread.java:724)
> 13:59:19,462 ERROR [stderr] (default task-55) Caused by: java.io.IOException: Broken pipe
> 13:59:19,462 ERROR [stderr] (default task-55) at sun.nio.ch.FileDispatcherImpl.write0(Native Method)
> 13:59:19,463 ERROR [stderr] (default task-55) at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47)
> 13:59:19,463 ERROR [stderr] (default task-55) at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:94)
> 13:59:19,463 ERROR [stderr] (default task-55) at sun.nio.ch.IOUtil.write(IOUtil.java:65)
> 13:59:19,464 ERROR [stderr] (default task-55) at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:466)
> 13:59:19,464 ERROR [stderr] (default task-55) at org.xnio.nio.NioSocketConduit.write(NioSocketConduit.java:150)
> 13:59:19,465 ERROR [stderr] (default task-55) at io.undertow.server.protocol.http.HttpResponseConduit.write(HttpResponseConduit.java:531)
> 13:59:19,465 ERROR [stderr] (default task-55) at io.undertow.conduits.ChunkedStreamSinkConduit.flush(ChunkedStreamSinkConduit.java:256)
> 13:59:19,466 ERROR [stderr] (default task-55) at org.xnio.conduits.ConduitStreamSinkChannel.flush(ConduitStreamSinkChannel.java:162)
> 13:59:19,466 ERROR [stderr] (default task-55) at io.undertow.channels.DetachableStreamSinkChannel.flush(DetachableStreamSinkChannel.java:100)
> 13:59:19,467 ERROR [stderr] (default task-55) at org.xnio.channels.Channels.flushBlocking(Channels.java:63)
> 13:59:19,467 ERROR [stderr] (default task-55) at io.undertow.servlet.spec.ServletOutputStreamImpl.close(ServletOutputStreamImpl.java:625)
> 13:59:19,467 ERROR [stderr] (default task-55) at io.undertow.servlet.spec.HttpServletResponseImpl.closeStreamAndWriter(HttpServletResponseImpl.java:451)
> 13:59:19,468 ERROR [stderr] (default task-55) at io.undertow.servlet.spec.HttpServletResponseImpl.responseDone(HttpServletResponseImpl.java:525)
> 13:59:19,468 ERROR [stderr] (default task-55) ... 6 more
> {code}
> This exception is only thrown with Wildfly, I tried this on EAP 6.2 and EAP 6.3 and there is no such exception.
> Despite the error, the component keeps working. However it does not use WebSockets, same as described in RF-13787.
> Please see steps to reproduce.
> Note: Use Chrome rather than FF. The issue is reproducible in both, but with FF it is slightly different.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (RF-13790) Showcase - dataTable Styling example - broken styling after built in sorting/filtering is enabled
by Juraj Húska (JIRA)
Juraj Húska created RF-13790:
--------------------------------
Summary: Showcase - dataTable Styling example - broken styling after built in sorting/filtering is enabled
Key: RF-13790
URL: https://issues.jboss.org/browse/RF-13790
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: showcase
Affects Versions: 4.5.0.Beta1
Reporter: Juraj Húska
Please checkout the screenshot to see how the styling of the table is broken (every odd row should have different background color).
There are multiple wrong places in the facelet for this example, which causes this break of styling.
* code for first column uses attribute {{accept}}, which is not defined for RF4, there should be {{filter}} instead
* there is typo in EL to reference a bean in the same place, there is {{carsFiteringBean}}, instead of {{carsFilteringBean}}
* when I change this two things, the filtering does not work either, because in the referenced filter implementation, the {{mileage}} or {{vendor}} is always {{null}}.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months