[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:
-------------------------------
Description:
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.
was:
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.
> 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)
10 years, 5 months
[JBoss JIRA] (RF-13789) Push component with Wildfly 8.1
by Matej Novotny (JIRA)
Matej Novotny created RF-13789:
----------------------------------
Summary: 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.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RF-11453) Add autocomplete functionality to the rich:select component
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-11453?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek commented on RF-11453:
----------------------------------
Good job, now it works also on Firefox.
I have looked at the newly introduced attributes: {{mode}}, {{minChars}} (not mentioning those already used in sample) and found that:
* {{minChars}} works only with *ajax {{mode}}, is it correct ?
* using {{autocompleteList}} with {{clientFilterFunction}} doesn't work when used with *ajax {{mode}}. Is it correct?
* there should be a note in javadocs about {{mode}} and {{minChars}} which works only in 'autocomplete mode'
You can now use Metamer Application to verify this (only on branch RF-11453 now).
I have discovered another issue with {{minChars}} which can be reproduced in Metamer:
# deploy metamer and open http://localhost:8080/metamer/faces/components/richSelect/autocompleteMet...
# set {{minChars}} to 2
# type {{al}} in the select, two suggestions will appear (Alaska, Alabama)
# delete last character // >>> "a"
# type {{q}} // >>> "aq" ; this will produce no suggestions
# delete last character // >>> "a"
# type {{l}} again // >>> "al"
** expected: two suggestions will appear (Alaska, Alabama)
** have: no suggestion will appear and the select is broken, no value can be selected thereafter, even if you delete the input
[~michpetrov] or [~bleathem] could you look at this?
> Add autocomplete functionality to the rich:select component
> -----------------------------------------------------------
>
> Key: RF-11453
> URL: https://issues.jboss.org/browse/RF-11453
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-selects
> Reporter: Cody Lerum
> Assignee: Michal Petrov
> Fix For: 4.5.0.Beta1
>
> Original Estimate: 3 days
> Time Spent: 2 days
> Remaining Estimate: 1 day
>
> Add an "autocompleteMethod" to rich:select
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RF-13788) Built-in filtering doesn't update dataScroller
by Martin Tomasek (JIRA)
Martin Tomasek created RF-13788:
-----------------------------------
Summary: Built-in filtering doesn't update dataScroller
Key: RF-13788
URL: https://issues.jboss.org/browse/RF-13788
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-tables
Affects Versions: cdk-4.5.0.Alpha1
Reporter: Martin Tomasek
Built-in sorting doesn't update number of pages in outer dataScroller. The same behaviour is for dataTable and extendedDataTable.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RF-13787) Push not using WebSockets
by Matej Novotny (JIRA)
Matej Novotny created RF-13787:
----------------------------------
Summary: Push not using WebSockets
Key: RF-13787
URL: https://issues.jboss.org/browse/RF-13787
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.1.28-jbossorg-2
JBoss AS 7.4.0.Final-redhat-12 (EAP 6.3)
Java(TM) SE Runtime Environment 1.7.0_25-b15 @ Linux
Chrome 36.0.1985.143 @ Linux x86_64
_____
Same with latest FF, but Chrome has better verification tools in this case.
Reporter: Matej Novotny
Fix For: 4.5.0.Beta1
When using push, connection should be established via WebSockets.
This does not happen and the old method is used. I also tried a workaround which was needed in earlier versions of EAP - [manually enabling websockets|http://blog.arungupta.me/2014/05/websocket-jboss-eap-6-3/].
I used EAP 6.3 and Metamer/Showcase. Please see steps to reproduce.
As for verification of WebSockets usage, Chrome dev tools can detect connection establishment as described [here|http://blog.kaazing.com/2012/05/09/inspecting-websocket-traffic-with...].
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RF-13787) Push with EAP 6.3 not using WebSockets
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RF-13787?page=com.atlassian.jira.plugin.s... ]
Matej Novotny updated RF-13787:
-------------------------------
Summary: Push with EAP 6.3 not using WebSockets (was: Push not using WebSockets)
> Push with EAP 6.3 not using WebSockets
> --------------------------------------
>
> Key: RF-13787
> URL: https://issues.jboss.org/browse/RF-13787
> 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.1.28-jbossorg-2
> JBoss AS 7.4.0.Final-redhat-12 (EAP 6.3)
> Java(TM) SE Runtime Environment 1.7.0_25-b15 @ Linux
> Chrome 36.0.1985.143 @ Linux x86_64
> _____
> Same with latest FF, but Chrome has better verification tools in this case.
> Reporter: Matej Novotny
> Fix For: 4.5.0.Beta1
>
>
> When using push, connection should be established via WebSockets.
> This does not happen and the old method is used. I also tried a workaround which was needed in earlier versions of EAP - [manually enabling websockets|http://blog.arungupta.me/2014/05/websocket-jboss-eap-6-3/].
> I used EAP 6.3 and Metamer/Showcase. Please see steps to reproduce.
> As for verification of WebSockets usage, Chrome dev tools can detect connection establishment as described [here|http://blog.kaazing.com/2012/05/09/inspecting-websocket-traffic-with...].
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 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
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
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months