[JBoss JIRA] (RF-12033) ExtendedDataTable doesn't show up in tabpanel with switchType="client"
by Steve Oh (JIRA)
[ https://issues.jboss.org/browse/RF-12033?page=com.atlassian.jira.plugin.s... ]
Steve Oh updated RF-12033:
--------------------------
Attachment: rf12033_IE9_error.png
IE9, mojarra 2.1.20
> ExtendedDataTable doesn't show up in tabpanel with switchType="client"
> ----------------------------------------------------------------------
>
> Key: RF-12033
> URL: https://issues.jboss.org/browse/RF-12033
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.0.Final
> Environment: FireFox 10.0.2 (works in IE7)
> GlassFish 3.1
> Reporter: Josh Hill
> Assignee: Jiří Štefek
> Labels: lazy-loaded
> Attachments: rf-12033-jsf2.1.20-glassfish3.1.2.2-ie-source-OK.htm, rf-12033-jsf2.1.20-glassfish3.1.2.2-ie9-OK.png, rf12033_IE10_OK_resizing_window.png, rf12033_IE9_error.png, richfaces-test.zip
>
>
> ExtendedDataTable doesn't show up in tabpanel with switchType="client"
> Facelet file from the attached testcase:
> {code}
> <?xml version='1.0' encoding='UTF-8' ?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <html xmlns="http://www.w3.org/1999/xhtml"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:rich="http://richfaces.org/rich"
> xmlns:f="http://java.sun.com/jsf/core">
> <h:head>
> <title>Test One</title>
> </h:head>
> <h:body>
> <p>Extended datatable inside tabpanel with switchType "client"</p>
> <h:form>
> <rich:tabPanel switchType="client">
> <rich:tab>
> <f:facet name="header">
> Tab One
> </f:facet>
> Tab One
> </rich:tab>
> <rich:tab>
> <f:facet name="header">
> Tab Two
> </f:facet>
> <rich:extendedDataTable value="#{colorsBean.colors}" var="color">
> <rich:column>
> <f:facet name="header">
> Column 1
> </f:facet>
> #{color}
> </rich:column>
> </rich:extendedDataTable>
> </rich:tab>
> </rich:tabPanel>
> </h:form>
> </h:body>
> </html>
> {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
10 years, 2 months
[JBoss JIRA] (RF-2494) Multiple clicks on a particular Tree node doesn't fire nodeSelectListener method for each click (only for the first time)
by Kristina Chyzhewska (JIRA)
[ https://issues.jboss.org/browse/RF-2494?page=com.atlassian.jira.plugin.sy... ]
Kristina Chyzhewska commented on RF-2494:
-----------------------------------------
I solved this problem in our project as follows:
For the corresponding <rich:treeNode> uses <a4j:support> which calls <a4j:commandLink> which processes such action like nodeSelectListener
{code:title=treeNode.xhtml|borderStyle=solid}
<rich:tree id="treeId"
var="node"
ajaxkeys="#{null}"
ajaxSubmitSelection="true"
switchType="ajax"
nodeSelectListener="#{treeBean.processSelection}"
adviseNodeSelected="#{treeBean.adviseNodeSelected}"
adviseNodeOpened="#{treeBean.adviseNodeOpened}"
changeExpandListener="#{treeBean.processExpansion}"
limitToList="true"
reRender="…"
…>
<rich:treeNodesAdaptor var="root" nodes="#{ treeBean.getNodes()}">
<rich:treeNode>
<a4j:outputPanel layout="block">
<h:outputText value="…" />
</a4j:outputPanel>
<a4j:support event="onclick" oncomplete="document.getElementById('#{facesClientUtil.getClientIdSafely('nodeLink')}').click()" />
</rich:treeNode>
<a4j:commandLink id="nodeLink" actionListener="#{treeBean.processSelection}" reRender="…"/>
{code}
> Multiple clicks on a particular Tree node doesn't fire nodeSelectListener method for each click (only for the first time)
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: RF-2494
> URL: https://issues.jboss.org/browse/RF-2494
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.1.4
> Reporter: Mareks Malnacs
>
> Here is the problem:
> -construct Tree with recursiveTreeNodesAdaptor, switchType="client" and ajaxSubmitSelection="true"
> -add method binding to nodeSelectListener so that every click on tree node executes some business method (for tests - simple log message displaying clicked node id for example)
> Result:
> -tree is rendered fine, clicks on different node elements in a tree executes specified nodeSelectListener method also fine, BUT when user clicks same tree node twice, nodeSelectListener method is not fired - to get it fired for this particular node again You have to click some other node in a tree and then click back on desired one. Shouldn't nodeSelectListener be fired on each click on a tree node even though user is clicking on the same node multiple times ?
--
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
10 years, 2 months
[JBoss JIRA] (RF-12033) ExtendedDataTable doesn't show up in tabpanel with switchType="client"
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-12033?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek updated RF-12033:
-----------------------------
Attachment: rf-12033-jsf2.1.20-glassfish3.1.2.2-ie9-OK.png
rf-12033-jsf2.1.20-glassfish3.1.2.2-ie-source-OK.htm
Attached screenshot and source of what I get with configuration used by Steve Oh.
> ExtendedDataTable doesn't show up in tabpanel with switchType="client"
> ----------------------------------------------------------------------
>
> Key: RF-12033
> URL: https://issues.jboss.org/browse/RF-12033
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.0.Final
> Environment: FireFox 10.0.2 (works in IE7)
> GlassFish 3.1
> Reporter: Josh Hill
> Assignee: Jiří Štefek
> Labels: lazy-loaded
> Attachments: rf-12033-jsf2.1.20-glassfish3.1.2.2-ie-source-OK.htm, rf-12033-jsf2.1.20-glassfish3.1.2.2-ie9-OK.png, richfaces-test.zip
>
>
> ExtendedDataTable doesn't show up in tabpanel with switchType="client"
> Facelet file from the attached testcase:
> {code}
> <?xml version='1.0' encoding='UTF-8' ?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <html xmlns="http://www.w3.org/1999/xhtml"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:rich="http://richfaces.org/rich"
> xmlns:f="http://java.sun.com/jsf/core">
> <h:head>
> <title>Test One</title>
> </h:head>
> <h:body>
> <p>Extended datatable inside tabpanel with switchType "client"</p>
> <h:form>
> <rich:tabPanel switchType="client">
> <rich:tab>
> <f:facet name="header">
> Tab One
> </f:facet>
> Tab One
> </rich:tab>
> <rich:tab>
> <f:facet name="header">
> Tab Two
> </f:facet>
> <rich:extendedDataTable value="#{colorsBean.colors}" var="color">
> <rich:column>
> <f:facet name="header">
> Column 1
> </f:facet>
> #{color}
> </rich:column>
> </rich:extendedDataTable>
> </rich:tab>
> </rich:tabPanel>
> </h:form>
> </h:body>
> </html>
> {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
10 years, 2 months
[JBoss JIRA] (RF-12033) ExtendedDataTable doesn't show up in tabpanel with switchType="client"
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-12033?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek commented on RF-12033:
----------------------------------
Manually updated JSF implementation in Glassfish 3.1.2.2 to 2.1.20.
Tried with RF 4.3.4.Final on IE 9,10,11 and FF 27 and I still can't reproduce it.
> ExtendedDataTable doesn't show up in tabpanel with switchType="client"
> ----------------------------------------------------------------------
>
> Key: RF-12033
> URL: https://issues.jboss.org/browse/RF-12033
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.0.Final
> Environment: FireFox 10.0.2 (works in IE7)
> GlassFish 3.1
> Reporter: Josh Hill
> Assignee: Jiří Štefek
> Labels: lazy-loaded
> Attachments: richfaces-test.zip
>
>
> ExtendedDataTable doesn't show up in tabpanel with switchType="client"
> Facelet file from the attached testcase:
> {code}
> <?xml version='1.0' encoding='UTF-8' ?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <html xmlns="http://www.w3.org/1999/xhtml"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:rich="http://richfaces.org/rich"
> xmlns:f="http://java.sun.com/jsf/core">
> <h:head>
> <title>Test One</title>
> </h:head>
> <h:body>
> <p>Extended datatable inside tabpanel with switchType "client"</p>
> <h:form>
> <rich:tabPanel switchType="client">
> <rich:tab>
> <f:facet name="header">
> Tab One
> </f:facet>
> Tab One
> </rich:tab>
> <rich:tab>
> <f:facet name="header">
> Tab Two
> </f:facet>
> <rich:extendedDataTable value="#{colorsBean.colors}" var="color">
> <rich:column>
> <f:facet name="header">
> Column 1
> </f:facet>
> #{color}
> </rich:column>
> </rich:extendedDataTable>
> </rich:tab>
> </rich:tabPanel>
> </h:form>
> </h:body>
> </html>
> {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
10 years, 2 months
[JBoss JIRA] (RF-13250) Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final
by Pavel Slegr (JIRA)
[ https://issues.jboss.org/browse/RF-13250?page=com.atlassian.jira.plugin.s... ]
Pavel Slegr commented on RF-13250:
----------------------------------
sent https://github.com/richfaces4/core/pull/21 for 4.3.x
> Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final
> --------------------------------------------------------------
>
> Key: RF-13250
> URL: https://issues.jboss.org/browse/RF-13250
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4, 4.3.5
> Environment: Gentoo Linux, Tomcat 7.0.39, MyFaces 2.1.12, Tomahawk 1.1.14, RichFaces 4.3.4, APR 1.4.5
> Reporter: Milo van der Zee
> Assignee: Juraj Húska
> Labels: memoryleak
> Attachments: rf.patch
>
>
> Hello,
> I did an upgrade from RF 4.3.3.Final to 4.3.4.Final and the application started to crash with 'Out Off Memory' errors. I changed the POM back to 4.3.3.Final and the problem is gone.
> I also started seeing this message lot's of times:
> {{WARN org.atmosphere.cpr.AtmosphereResponse - Committed error code 400}}
> I don't know if that has anything to do with the error. I set {{org.atmosphere.cpr.sessionSupport}} to {{true}} and I did not see the message again. But still the application went out-of-memory.
> In the crashed system heap dump I see a lot of:
> - AtomicBoolean (751.000, 15.0MB)
> - ConcurrentLinkedQueue
> - AtmospereRequest$Builder (60.042, 13.8MB)
> To me it looks like it has something to do with Atmosphere. Any ideas?
> Thanks,
> Milo van der Zee
--
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
10 years, 2 months
[JBoss JIRA] (RF-9485) IE9 Beta - AJAX broken
by Nicolas Daniels (JIRA)
[ https://issues.jboss.org/browse/RF-9485?page=com.atlassian.jira.plugin.sy... ]
Nicolas Daniels commented on RF-9485:
-------------------------------------
I haven't tried it under IE10 but I think it should work.
Best is probably to test it :-)
> IE9 Beta - AJAX broken
> ----------------------
>
> Key: RF-9485
> URL: https://issues.jboss.org/browse/RF-9485
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: compatibility
> Affects Versions: 3.3.2.SR1, 3.3.3.Final
> Environment: Windows Vista SP2 (Virtual PC VM), IE9 Beta
> Reporter: Andrew May
> Labels: ie9
> Fix For: 3.Future
>
> Attachments: AJAX.js, AJAX.js, AJAX.js, IE9.txt, JSFAJAX.txt, sarissa.js
>
>
> In the Rich Faces Demo (3.3.3 Final) there are a couple of errors shown in the JavaScript Console in IE9, and the Ajax demos do not work.
> On loading a section:
> SCRIPT5007: 'undefined' is null or not an object - framework.pack.js.jsf, line 1870 character 65
> On trying one of the AJAX demos (e.g. the CommandButton demo):
> SCRIPT16386: No such interface supported - framework.pack.js.jsf, line 2373 character 3
> In our applications (3.2.SR1), we see an error for every Ajax request:
> SCRIPT16386: No such interface supported - 3_3_2.SR1org.ajax4jsf.javascript.AjaxScript, line 120 character 1
> For both the SCRIPT16386 errors, the JavaScript is assigning A.outerHTML = new XMLSerializer().serializeToString(C)
> I believe that this is the first version of IE9 to include XMLSerializer.
> I don't know enough about XMLSerializer to know whether this is an IE9 issue or a RichFaces issue.
--
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
10 years, 2 months
[JBoss JIRA] (RF-9485) IE9 Beta - AJAX broken
by Kalyan M (JIRA)
[ https://issues.jboss.org/browse/RF-9485?page=com.atlassian.jira.plugin.sy... ]
Kalyan M edited comment on RF-9485 at 2/21/14 8:32 PM:
-------------------------------------------------------
I am facing the same issue described above and felt excited to know that the fix suggested by Nicolas Daniels is working for some users on IE 9. Can i know if it will work in IE 10 too?
was (Author: kalyancm):
Will the solution suggested by Nicolas Daniels work for IE 10?
> IE9 Beta - AJAX broken
> ----------------------
>
> Key: RF-9485
> URL: https://issues.jboss.org/browse/RF-9485
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: compatibility
> Affects Versions: 3.3.2.SR1, 3.3.3.Final
> Environment: Windows Vista SP2 (Virtual PC VM), IE9 Beta
> Reporter: Andrew May
> Labels: ie9
> Fix For: 3.Future
>
> Attachments: AJAX.js, AJAX.js, AJAX.js, IE9.txt, JSFAJAX.txt, sarissa.js
>
>
> In the Rich Faces Demo (3.3.3 Final) there are a couple of errors shown in the JavaScript Console in IE9, and the Ajax demos do not work.
> On loading a section:
> SCRIPT5007: 'undefined' is null or not an object - framework.pack.js.jsf, line 1870 character 65
> On trying one of the AJAX demos (e.g. the CommandButton demo):
> SCRIPT16386: No such interface supported - framework.pack.js.jsf, line 2373 character 3
> In our applications (3.2.SR1), we see an error for every Ajax request:
> SCRIPT16386: No such interface supported - 3_3_2.SR1org.ajax4jsf.javascript.AjaxScript, line 120 character 1
> For both the SCRIPT16386 errors, the JavaScript is assigning A.outerHTML = new XMLSerializer().serializeToString(C)
> I believe that this is the first version of IE9 to include XMLSerializer.
> I don't know enough about XMLSerializer to know whether this is an IE9 issue or a RichFaces issue.
--
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
10 years, 2 months
[JBoss JIRA] (RF-9485) IE9 Beta - AJAX broken
by Kalyan M (JIRA)
[ https://issues.jboss.org/browse/RF-9485?page=com.atlassian.jira.plugin.sy... ]
Kalyan M commented on RF-9485:
------------------------------
Will the solution suggested by Nicolas Daniels work for IE 10?
> IE9 Beta - AJAX broken
> ----------------------
>
> Key: RF-9485
> URL: https://issues.jboss.org/browse/RF-9485
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: compatibility
> Affects Versions: 3.3.2.SR1, 3.3.3.Final
> Environment: Windows Vista SP2 (Virtual PC VM), IE9 Beta
> Reporter: Andrew May
> Labels: ie9
> Fix For: 3.Future
>
> Attachments: AJAX.js, AJAX.js, AJAX.js, IE9.txt, JSFAJAX.txt, sarissa.js
>
>
> In the Rich Faces Demo (3.3.3 Final) there are a couple of errors shown in the JavaScript Console in IE9, and the Ajax demos do not work.
> On loading a section:
> SCRIPT5007: 'undefined' is null or not an object - framework.pack.js.jsf, line 1870 character 65
> On trying one of the AJAX demos (e.g. the CommandButton demo):
> SCRIPT16386: No such interface supported - framework.pack.js.jsf, line 2373 character 3
> In our applications (3.2.SR1), we see an error for every Ajax request:
> SCRIPT16386: No such interface supported - 3_3_2.SR1org.ajax4jsf.javascript.AjaxScript, line 120 character 1
> For both the SCRIPT16386 errors, the JavaScript is assigning A.outerHTML = new XMLSerializer().serializeToString(C)
> I believe that this is the first version of IE9 to include XMLSerializer.
> I don't know enough about XMLSerializer to know whether this is an IE9 issue or a RichFaces issue.
--
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
10 years, 2 months
[JBoss JIRA] (RF-13250) Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13250?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13250:
------------------------------------
[~sebek64] would you like to formulate your patch as a Pull Request on github?
https://community.jboss.org/wiki/GuideToUsePullRequestsWithGitHubAndJIRA
Don't forget to sign the CLA:
https://cla.jboss.org/index.seam
Note: You do not have to create the PR, but it is the best way to assign and track appropriate attribution.
> Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final
> --------------------------------------------------------------
>
> Key: RF-13250
> URL: https://issues.jboss.org/browse/RF-13250
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4, 4.3.5
> Environment: Gentoo Linux, Tomcat 7.0.39, MyFaces 2.1.12, Tomahawk 1.1.14, RichFaces 4.3.4, APR 1.4.5
> Reporter: Milo van der Zee
> Assignee: Juraj Húska
> Labels: memoryleak
> Attachments: rf.patch
>
>
> Hello,
> I did an upgrade from RF 4.3.3.Final to 4.3.4.Final and the application started to crash with 'Out Off Memory' errors. I changed the POM back to 4.3.3.Final and the problem is gone.
> I also started seeing this message lot's of times:
> {{WARN org.atmosphere.cpr.AtmosphereResponse - Committed error code 400}}
> I don't know if that has anything to do with the error. I set {{org.atmosphere.cpr.sessionSupport}} to {{true}} and I did not see the message again. But still the application went out-of-memory.
> In the crashed system heap dump I see a lot of:
> - AtomicBoolean (751.000, 15.0MB)
> - ConcurrentLinkedQueue
> - AtmospereRequest$Builder (60.042, 13.8MB)
> To me it looks like it has something to do with Atmosphere. Any ideas?
> Thanks,
> Milo van der Zee
--
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
10 years, 2 months
[JBoss JIRA] (RF-10998) High CPU Utilization in Richfaces application
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-10998?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-10998:
------------------------------------
RichFaces 3.3.3.Final and JSF 1.2 are incredibly out-of-date and are no longer being developed. Many improvements have been made in RichFaces 4 and JSF 2 including some performance improvements. I recommend you upgrade to a modern and supported framework.
> High CPU Utilization in Richfaces application
> ---------------------------------------------
>
> Key: RF-10998
> URL: https://issues.jboss.org/browse/RF-10998
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.3.2.SR1
> Environment: Jboss 4.3.0.GA_CP03, jdk 1.6.0_05,jsf 1.2,facelets 1.1.14
> Reporter: Shah EM
> Labels: richfaces
> Fix For: 3.Future
>
>
> We have an application running on 3 node
> cluster.After running normally for some time one node CPU spikes to 80% from
> the normal usage of 6% and stays like that. meanwhile other nodes are working
> fine.
> We had contacted Redhat and they had advised to downgrad richfaces version to 3.3.1 sp2 to fix the issue.
> We have a doubt if the solution provided by Redhat to downgrade the rich faces version to 3.3.1-SP2 will solve the issue or not.
> The 3.3.1-SP2 release note says that the following issue is fixed - [RF-7248] - a4j creates infinite HashMap.get loop
> When we looked into more details of this issue that they fixed in the JBoss JIRA for this defect, the logs say that the issue is with a specific component in the a4j. Please have a look at the following trace from the issue logs.
> Stack trace:
> java.util.HashMap.get(HashMap.java:303)
> org.ajax4jsf.component.UIDataAdaptor.restoreChildState(UIDataAdaptor.java:965)
> org.ajax4jsf.component.UIDataAdaptor.restoreChildState(UIDataAdaptor.java:984)
> org.ajax4jsf.component.UIDataAdaptor.restoreChildState(UIDataAdaptor.java:943)
> In our case even though the issue is with the HashMap infinite loop, the cause of the issue does not seem to be this particular component. Our stack traces point to a different place where the infinite loop is happening.
> Thread: http-10.20.81.200-17180-31 : priority:5, demon:true, threadId:337, threadState:RUNNABLE, lockName:null
> java.util.HashMap.get(HashMap.java:305)
> org.apache.catalina.connector.Request.getAttribute(Request.java:878)
> org.apache.catalina.connector.RequestFacade.getAttribute(RequestFacade.java:263)
> com.sun.faces.application.WebappLifecycleListener.attributeReplaced(WebappLifecycleListener.java:168)
> com.sun.faces.config.ConfigureListener.attributeReplaced(ConfigureListener.java:318)
> org.apache.catalina.connector.Request.setAttribute(Request.java:1435)
> org.apache.catalina.connector.RequestFacade.setAttribute(RequestFacade.java:503)
> javax.servlet.ServletRequestWrapper.setAttribute(ServletRequestWrapper.java:284)
> com.sun.faces.context.RequestMap.put(ExternalContextImpl.java:1087)
> org.ajax4jsf.event.AjaxPhaseListener.afterPhase(AjaxPhaseListener.java:81)
> com.sun.faces.lifecycle.Phase.handleAfterPhase(Phase.java:175)
> com.sun.faces.lifecycle.Phase.doPhase(Phase.java:114)
> com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:104)
> com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
> javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206
--
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
10 years, 2 months