[JBoss JIRA] (RF-12682) extendedDataTable render issue with rich:tabPanel
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12682?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reopened RF-12682:
--------------------------------
> extendedDataTable render issue with rich:tabPanel
> -------------------------------------------------
>
> Key: RF-12682
> URL: https://issues.jboss.org/browse/RF-12682
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.3.Final, 4.3.0.M3, 4.3.0.CR1, 4.3.0.Final
> Reporter: Kaveh A.
> Labels: extendedDataTable, render, richfaces, tabpanel, testcase_provided
> Attachments: richfacesBug2.zip, RichFacesBugEclipseProject.zip
>
>
> This issue is not just specific to tabPanel. Anytime the extendedDataTable is hidden (when the page loads) and then it is made visible later the table can not display the data (table is empty at the load time).
> In this particular case if we load a page with two tabs. Furthermore if we have one extendedDataTable in each tab (the first tab shows and the second tab is not shown at first). In this case once the user clicks on the second tab and tries to populate the extendedDataTable (via any action). Then the table is not rendered properly. A sample project has been provided at the following link that further describe this issue. You can download the eclipse project attached at the end of the following message to reproduce this issue.
> https://community.jboss.org/message/783787
--
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, 11 months
[JBoss JIRA] (RF-12682) extendedDataTable render issue with rich:tabPanel
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12682?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-12682:
------------------------------------
Thanks for the update [~kaveh_a]. I'll close this issue as a duplicate of RF-12193. Would you please file a new issue describing the possible regression of an unresponsive tabPanel containing an empty EDT?
> extendedDataTable render issue with rich:tabPanel
> -------------------------------------------------
>
> Key: RF-12682
> URL: https://issues.jboss.org/browse/RF-12682
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.3.Final, 4.3.0.M3, 4.3.0.CR1, 4.3.0.Final
> Reporter: Kaveh A.
> Labels: extendedDataTable, render, richfaces, tabpanel, testcase_provided
> Fix For: 5-Tracking
>
> Attachments: richfacesBug2.zip, RichFacesBugEclipseProject.zip
>
>
> This issue is not just specific to tabPanel. Anytime the extendedDataTable is hidden (when the page loads) and then it is made visible later the table can not display the data (table is empty at the load time).
> In this particular case if we load a page with two tabs. Furthermore if we have one extendedDataTable in each tab (the first tab shows and the second tab is not shown at first). In this case once the user clicks on the second tab and tries to populate the extendedDataTable (via any action). Then the table is not rendered properly. A sample project has been provided at the following link that further describe this issue. You can download the eclipse project attached at the end of the following message to reproduce this issue.
> https://community.jboss.org/message/783787
--
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, 11 months
[JBoss JIRA] (RF-12682) extendedDataTable render issue with rich:tabPanel
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12682?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-12682.
--------------------------------
Fix Version/s: (was: 5-Tracking)
Resolution: Done
> extendedDataTable render issue with rich:tabPanel
> -------------------------------------------------
>
> Key: RF-12682
> URL: https://issues.jboss.org/browse/RF-12682
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.3.Final, 4.3.0.M3, 4.3.0.CR1, 4.3.0.Final
> Reporter: Kaveh A.
> Labels: extendedDataTable, render, richfaces, tabpanel, testcase_provided
> Attachments: richfacesBug2.zip, RichFacesBugEclipseProject.zip
>
>
> This issue is not just specific to tabPanel. Anytime the extendedDataTable is hidden (when the page loads) and then it is made visible later the table can not display the data (table is empty at the load time).
> In this particular case if we load a page with two tabs. Furthermore if we have one extendedDataTable in each tab (the first tab shows and the second tab is not shown at first). In this case once the user clicks on the second tab and tries to populate the extendedDataTable (via any action). Then the table is not rendered properly. A sample project has been provided at the following link that further describe this issue. You can download the eclipse project attached at the end of the following message to reproduce this issue.
> https://community.jboss.org/message/783787
--
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, 11 months
[JBoss JIRA] (RF-12907) render="@form" problem with a4jCommand Button
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12907?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-12907:
------------------------------------
Can you provide a sample without Spring? This will help us to more quickly narrow down (and subsequently fix) the source of the problem.
> render="@form" problem with a4jCommand Button
> ---------------------------------------------
>
> Key: RF-12907
> URL: https://issues.jboss.org/browse/RF-12907
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.2.3.Final, 4.3.1
> Environment: JSF Mojarra 2.1.21 or 2.1.20 - Glassfish or WAS 8.0.0.x Servlet 3.0 or 2.5
> Reporter: Jean ANDRE
> Priority: Blocker
> Attachments: Nested-Spring-3.2.2.zip
>
>
> Please see the report at: http://java.net/jira/browse/JAVASERVERFACES-2016
> It seems that that there is a problem with a4j button and the value of @form/render attribute.
> The symptom we got is after refreshing the panel for building a list. Click on link form the result lisk does not trigger the action.
--
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, 11 months
[JBoss JIRA] (RF-12899) Deadlock appears in push component
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12899?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-12899:
----------------------------------
Assignee: Lukáš Fryč
Lukas, please assess and schedule as you find appropriate.
> Deadlock appears in push component
> ----------------------------------
>
> Key: RF-12899
> URL: https://issues.jboss.org/browse/RF-12899
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-push/poll
> Affects Versions: 4.2.2.Final
> Reporter: Jiří Mikulášek
> Assignee: Lukáš Fryč
>
> Our application freezes occasionally. We used Jstack and have seen the deadlock below. It seems to be very simillar to RF12013, but the stack is slightly different
> Found one Java-level deadlock:
> =============================
> {code}
> "localhost-startStop-2":
> waiting to lock monitor 0x000000000782a368 (object 0x000000078da957e0, a org.richfaces.application.push.impl.SessionImpl),
> which is held by "http-nio-30085-exec-4"
> "http-nio-30085-exec-4":
> waiting to lock monitor 0x00000000085cbe00 (object 0x000000078e8ecf90, a org.atmosphere.cpr.AtmosphereResourceImpl),
> which is held by "Atmosphere-AsyncWrite-0"
> "Atmosphere-AsyncWrite-0":
> waiting to lock monitor 0x000000000782a368 (object 0x000000078da957e0, a org.richfaces.application.push.impl.SessionImpl),
> which is held by "http-nio-30085-exec-4"
> {code}
> Java stack information for the threads listed above:
> ===================================================
> {code}
> "localhost-startStop-2":
> at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117)
> - waiting to lock <0x000000078da957e0> (a org.richfaces.application.push.impl.SessionImpl)
> at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:128)
> at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:136)
> at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:658)
> at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:607)
> at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:591)
> at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:187)
> - locked <0x000000078e8b64a8> (a org.atmosphere.cpr.AtmosphereResourceImpl)
> at org.atmosphere.cpr.DefaultBroadcaster.resumeAll(DefaultBroadcaster.java:300)
> - locked <0x000000078e8d1ac8> (a java.util.concurrent.ConcurrentLinkedQueue)
> at org.atmosphere.cpr.DefaultBroadcasterFactory.destroy(DefaultBroadcasterFactory.java:274)
> - locked <0x000000078cb112d8> (a org.atmosphere.cpr.DefaultBroadcasterFactory)
> at org.atmosphere.cpr.AtmosphereServlet.destroy(AtmosphereServlet.java:867)
> at org.atmosphere.cpr.MeteorServlet.destroy(MeteorServlet.java:88)
> at org.apache.catalina.core.StandardWrapper.unload(StandardWrapper.java:1481)
> - locked <0x0000000784b6a168> (a org.apache.catalina.core.StandardWrapper)
> at org.apache.catalina.core.StandardWrapper.stopInternal(StandardWrapper.java:1842)
> - locked <0x0000000784b6a168> (a org.apache.catalina.core.StandardWrapper)
> at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232)
> - locked <0x0000000784b6a168> (a org.apache.catalina.core.StandardWrapper)
> at org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5471)
> - locked <0x000000078312e828> (a org.apache.catalina.core.StandardContext)
> at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232)
> - locked <0x000000078312e828> (a org.apache.catalina.core.StandardContext)
> at org.apache.catalina.core.ContainerBase$StopChild.call(ContainerBase.java:1575)
> at org.apache.catalina.core.ContainerBase$StopChild.call(ContainerBase.java:1564)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:662)
> "http-nio-30085-exec-4":
> at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:168)
> - waiting to lock <0x000000078e8ecf90> (a org.atmosphere.cpr.AtmosphereResourceImpl)
> at org.atmosphere.cpr.Meteor.resume(Meteor.java:240)
> at org.richfaces.application.push.impl.RequestImpl.resume(RequestImpl.java:71)
> at org.richfaces.application.push.impl.SessionImpl.releaseRequest(SessionImpl.java:112)
> at org.richfaces.application.push.impl.SessionImpl.connect(SessionImpl.java:85)
> - locked <0x000000078da957e0> (a org.richfaces.application.push.impl.SessionImpl)
> at org.richfaces.application.push.impl.RequestImpl.onSuspend(RequestImpl.java:119)
> at org.atmosphere.cpr.AtmosphereResourceImpl.onSuspend(AtmosphereResourceImpl.java:652)
> at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:611)
> at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:591)
> at org.atmosphere.cpr.AtmosphereResourceImpl.suspend(AtmosphereResourceImpl.java:347)
> at org.atmosphere.cpr.Meteor.suspend(Meteor.java:213)
> at org.richfaces.application.push.impl.RequestImpl.suspend(RequestImpl.java:67)
> at org.richfaces.webapp.PushHandlerFilter.doFilter(PushHandlerFilter.java:107)
> at org.atmosphere.util.AtmosphereFilterChain.doFilter(AtmosphereFilterChain.java:139)
> at org.atmosphere.util.AtmosphereFilterChain.invokeFilterChain(AtmosphereFilterChain.java:116)
> at org.atmosphere.handler.ReflectorServletProcessor$FilterChainServletWrapper.service(ReflectorServletProcessor.java:293)
> at org.atmosphere.handler.ReflectorServletProcessor.onRequest(ReflectorServletProcessor.java:151)
> at org.atmosphere.cpr.AsynchronousProcessor.action(AsynchronousProcessor.java:219)
> at org.atmosphere.cpr.AsynchronousProcessor.suspended(AsynchronousProcessor.java:154)
> at org.atmosphere.container.Tomcat7CometSupport.service(Tomcat7CometSupport.java:85)
> at org.atmosphere.cpr.AtmosphereServlet.doCometSupport(AtmosphereServlet.java:1218)
> at org.atmosphere.cpr.AtmosphereServlet.event(AtmosphereServlet.java:1286)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEvent(ApplicationFilterChain.java:484)
> at org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(ApplicationFilterChain.java:377)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
> at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
> at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
> at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1686)
> - locked <0x000000078e7fcc28> (a org.apache.tomcat.util.net.NioChannel)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:662)
> "Atmosphere-AsyncWrite-0":
> at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117)
> - waiting to lock <0x000000078da957e0> (a org.richfaces.application.push.impl.SessionImpl)
> at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:128)
> at org.richfaces.application.push.impl.RequestImpl.onDisconnect(RequestImpl.java:140)
> at org.atmosphere.cpr.AtmosphereResourceImpl.onDisconnect(AtmosphereResourceImpl.java:664)
> at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:609)
> at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:591)
> at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:719)
> at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:749)
> - locked <0x000000078e8ecf90> (a org.atmosphere.cpr.AtmosphereResourceImpl)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:662)
> {code}
> Found 1 deadlock.
--
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, 11 months
[JBoss JIRA] (RF-12887) Nodes with types that are not listed in <rich:treeNode> are not rendered
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12887?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12887:
-------------------------------
Fix Version/s: 5-Tracking
> Nodes with types that are not listed in <rich:treeNode> are not rendered
> ------------------------------------------------------------------------
>
> Key: RF-12887
> URL: https://issues.jboss.org/browse/RF-12887
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-tree
> Affects Versions: 4.3.0.Final
> Environment: RichFaces 4.3.0.Final and JSF 2.2
> JBoss AS 7.1.1.Final
> Reporter: Sergey Suvorov
> Priority: Minor
> Fix For: 5-Tracking
>
>
> When using attribute "type" of <rich:treeNode> nodes with different types are not rendered. In the following tree only nodes with types "1", "2" and "1_1" will be rendered
> {code}
> <rich:tree id="tree" nodeType="#{item.data.type}" var="item" value="#{backingBean.rootNode}" toggleType="client" selectionType="ajax">
> <rich:treeNode type="1">
> #{item.data.label}
> </rich:treeNode>
> <rich:treeNode type="2">
> #{item.data.label}
> </rich:treeNode>
> <rich:treeNode type="1_1">
> #{item.data.label}
> </rich:treeNode>
> </rich:tree>
> {code}
--
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, 11 months
[JBoss JIRA] (RF-12842) Allow CSS files with resource EL to be packed
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12842?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-12842:
----------------------------------
Assignee: Lukáš Fryč
> Allow CSS files with resource EL to be packed
> ---------------------------------------------
>
> Key: RF-12842
> URL: https://issues.jboss.org/browse/RF-12842
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: cdk
> Affects Versions: 4.3.1
> Reporter: Bernard Labno
> Assignee: Lukáš Fryč
>
> I want to package all my custom css files together with RF css files into single css file.
> I'm using maven-richfaces-resources-plugin for that.
> The problem is that css files with resource EL (i.e. #{resource['image.png']}) are excluded from packaging.
> The reason was RF-10474, but as discussed with Lukas Fryc, resource EL could be allowed.
--
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, 11 months
[JBoss JIRA] (RF-12876) Add "for" attribute to rich:focus
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12876?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-12876:
----------------------------------
Assignee: Lukáš Fryč
[~lfryc] please assess and schedule as appropriate.
> Add "for" attribute to rich:focus
> ---------------------------------
>
> Key: RF-12876
> URL: https://issues.jboss.org/browse/RF-12876
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-misc
> Affects Versions: 4.3.1
> Reporter: Bernard Labno
> Assignee: Lukáš Fryč
>
> Sandbox version of focus component allowed to specify "focus"
> for particular component. I'm missing this very much.
> If we have single form with 2 popup panels each with single input then with rich:focus we cannot specify which input should be focused.
> And when we open popup A then we want to have input in that popup to be focused, not the one in popup B.
--
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, 11 months