[JBoss JIRA] (RF-11782) [rich:tabPanel] switching tabs doesn't work correctly with switchtype="ajax"
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-11782?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-11782:
-------------------------------
Fix Version/s: 4.5-Tracking
(was: 5-Tracking)
> [rich:tabPanel] switching tabs doesn't work correctly with switchtype="ajax"
> ----------------------------------------------------------------------------
>
> Key: RF-11782
> URL: https://issues.jboss.org/browse/RF-11782
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes
> Affects Versions: 4.1.0.CR1
> Environment: mojarra-2.1.4, RF-CR1
> Reporter: Rene O
> Assignee: Brian Leathem
> Labels: lazy-loaded
> Fix For: 4.5-Tracking
>
> Attachments: jsf2testcase.war
>
>
> A testcase to reproduce this issue is attached:
> http://localhost:8080/jsf2testcase/tabswitchtest.jsf
> Steps to reproduce the issue:
> 1. switch to 'Tab 3' -> console/server-log shows 'getTestListA' and 'getTestListB' -> this is a bug, expected is only 'getTestListB', because tab3 has only one table with testListB
> 2. switch to 'Tab 1' -> console/server-log shows 'getTestListB' -> this is a bug, expected is nothing new in console/server-log, because tab1 has no table
> {code:title=xhtml}
> ...
> <h:form id="testform">
> <rich:tabPanel id="tabpanel" switchType="ajax" activeItem="#{dataBean.activeTab}">
> <rich:tab id="tab1" header="Tab 1">
> Here is tab #1
> </rich:tab>
> <rich:tab id="tab2" header="Tab 2">
> <rich:dataTable value="#{dataBean.testListA}" var="item" rows="10">
> <rich:column >
> <f:facet name="header">
> List A
> </f:facet>
> <h:outputText value="#{item.a}"/>
> </rich:column>
> </rich:dataTable>
> </rich:tab>
> <rich:tab id="tab3" header="Tab 3">
> <rich:dataTable value="#{dataBean.testListB}" var="item" rows="10">
> <rich:column >
> <f:facet name="header">
> List B
> </f:facet>
> <h:outputText value="#{item.a}"/>
> </rich:column>
> </rich:dataTable>
> </rich:tab>
> </rich:tabPanel>
> </h:form>
> ...
> {code}
> {code:title=java}
> ...
> public List<TestObject> getTestListA() {
> System.out.println("getTestListA");
> return testListA;
> }
> ...
> public List<TestObject> getTestListB() {
> System.out.println("getTestListB");
> return testListB;
> }
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months
[JBoss JIRA] (RF-13711) a4j:ajax status does not work as expected
by Evgeny Mironenko (JIRA)
[ https://issues.jboss.org/browse/RF-13711?page=com.atlassian.jira.plugin.s... ]
Evgeny Mironenko commented on RF-13711:
---------------------------------------
[~manovotn] thank you for the explanation, but in my case I have one common status for more than one form. Therefore, I need a handed down status. Of course I will use {{render}} instead of {{status}} but it will be great, if this problem will be fixed in next versions.
> a4j:ajax status does not work as expected
> -----------------------------------------
>
> Key: RF-13711
> URL: https://issues.jboss.org/browse/RF-13711
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.7, 4.3.8
> Environment: IE8, Mozilla Firefox 30
> Reporter: Evgeny Mironenko
> Assignee: Matej Novotny
> Fix For: 4.5-Tracking
>
>
> Status attribute for {{a4j:ajax}} does not work as expected.
> I tried to create simple project with content:
> {code:title=index.xhtml}
> <?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:a4j="http://richfaces.org/a4j">
> <h:head>
> </h:head>
> <h:body>
> <a4j:status id="progress" onstart="console.log('start')"
> onstop="console.log('stop')"/>
> <div id="content">
> <h:form>
> <h:commandButton value="Click">
> <a4j:ajax event="click" status="progress" listener="#{testBean.invoke}"/>
> </h:commandButton>
> </h:form>
> </div>
> </h:body>
> </html>
> {code}
> It did not work for me. I do not see any log messages in the console.
> As workaround I can use the {{render}} attribute instead of {{status}}, but we use it for another goals, am I right?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months
[JBoss JIRA] (RF-12108) Components second tab changes are not rendered after performing some ajax action if attribute ajaxRendered="true" inside <rich:message /> located on first tab
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-12108?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-12108:
-----------------------------
Assignee: (was: Juraj Húska)
> Components second tab changes are not rendered after performing some ajax action if attribute ajaxRendered="true" inside <rich:message /> located on first tab
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: RF-12108
> URL: https://issues.jboss.org/browse/RF-12108
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.2.0.Final, 4.2.2.Final
> Environment: JDK1.6,
> JBoss 6.0.Final, JBoss 7.1.1.Final
> richfaces 4.1.0.Final/4.2.0.Final/4.2.2.Final
> seam 3.1
> IE 9, Chrome, Firefox
> Reporter: Artur Mioduszewski
> Fix For: 4.5-Tracking
>
> Attachments: sample.xhtml
>
>
> In case getting 2 tabs (in my case it is primefaces tabs):
> {code:title=RENDERING ON SECOND TAB NOT WORKS (after clicking link)}
> First tab:
> <h:selectOneMenu id="nSurfacePercentageOfWholePlayback" value="#{newSurface.percentageOfWholePlayback}">
> <f:selectItems value="#{staticPercentagesItems}"/>
> </h:selectOneMenu>
> <rich:message for="nSurfacePercentageOfWholePlayback" ajaxRendered="true"/>
> Second tab (some code with ajax)
> Ex.
> <a4j:commandLink styleClass="no-decor" execute="@this" action="#{componentManager.deactivateVertically}">
> <h:graphicImage value="/images/icons/delete.gif" alt="Deactivate Vertically"/>
> <a4j:param value="#{dayIndex.index + 1}" assignTo="#{componentManager.verticalDeactivationIndex}"/>
> </a4j:commandLink>
> {code}
> {code:title=RENDERING ON SECOND TAB CORRECTLY WORKS (after clicking link)}
> First tab:
> <h:selectOneMenu id="nSurfacePercentageOfWholePlayback" value="#{newSurface.percentageOfWholePlayback}">
> <f:selectItems value="#{staticPercentagesItems}"/>
> </h:selectOneMenu>
> <rich:message for="nSurfacePercentageOfWholePlayback" ajaxRendered="false"/>
> Second tab (some code with ajax)
> Ex.
> <a4j:commandLink styleClass="no-decor" execute="@this" action="#{componentManager.deactivateVertically}">
> <h:graphicImage value="/images/icons/delete.gif" alt="Deactivate Vertically"/>
> <a4j:param value="#{dayIndex.index + 1}" assignTo="#{componentManager.verticalDeactivationIndex}"/>
> </a4j:commandLink>
> {code}
> When I change tabs order, problem does not exist.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months
[JBoss JIRA] (RF-12108) Components second tab changes are not rendered after performing some ajax action if attribute ajaxRendered="true" inside <rich:message /> located on first tab
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-12108?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-12108:
-----------------------------
Labels: (was: needs-qe)
> Components second tab changes are not rendered after performing some ajax action if attribute ajaxRendered="true" inside <rich:message /> located on first tab
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: RF-12108
> URL: https://issues.jboss.org/browse/RF-12108
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.2.0.Final, 4.2.2.Final
> Environment: JDK1.6,
> JBoss 6.0.Final, JBoss 7.1.1.Final
> richfaces 4.1.0.Final/4.2.0.Final/4.2.2.Final
> seam 3.1
> IE 9, Chrome, Firefox
> Reporter: Artur Mioduszewski
> Assignee: Juraj Húska
> Fix For: 4.5-Tracking
>
> Attachments: sample.xhtml
>
>
> In case getting 2 tabs (in my case it is primefaces tabs):
> {code:title=RENDERING ON SECOND TAB NOT WORKS (after clicking link)}
> First tab:
> <h:selectOneMenu id="nSurfacePercentageOfWholePlayback" value="#{newSurface.percentageOfWholePlayback}">
> <f:selectItems value="#{staticPercentagesItems}"/>
> </h:selectOneMenu>
> <rich:message for="nSurfacePercentageOfWholePlayback" ajaxRendered="true"/>
> Second tab (some code with ajax)
> Ex.
> <a4j:commandLink styleClass="no-decor" execute="@this" action="#{componentManager.deactivateVertically}">
> <h:graphicImage value="/images/icons/delete.gif" alt="Deactivate Vertically"/>
> <a4j:param value="#{dayIndex.index + 1}" assignTo="#{componentManager.verticalDeactivationIndex}"/>
> </a4j:commandLink>
> {code}
> {code:title=RENDERING ON SECOND TAB CORRECTLY WORKS (after clicking link)}
> First tab:
> <h:selectOneMenu id="nSurfacePercentageOfWholePlayback" value="#{newSurface.percentageOfWholePlayback}">
> <f:selectItems value="#{staticPercentagesItems}"/>
> </h:selectOneMenu>
> <rich:message for="nSurfacePercentageOfWholePlayback" ajaxRendered="false"/>
> Second tab (some code with ajax)
> Ex.
> <a4j:commandLink styleClass="no-decor" execute="@this" action="#{componentManager.deactivateVertically}">
> <h:graphicImage value="/images/icons/delete.gif" alt="Deactivate Vertically"/>
> <a4j:param value="#{dayIndex.index + 1}" assignTo="#{componentManager.verticalDeactivationIndex}"/>
> </a4j:commandLink>
> {code}
> When I change tabs order, problem does not exist.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months
[JBoss JIRA] (RF-12108) Components second tab changes are not rendered after performing some ajax action if attribute ajaxRendered="true" inside <rich:message /> located on first tab
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-12108?page=com.atlassian.jira.plugin.s... ]
Juraj Húska commented on RF-12108:
----------------------------------
It seems that with recent RichFaces {{4.5.0.Alpha3-SNAPSHOT}} this issue is resolved.
> Components second tab changes are not rendered after performing some ajax action if attribute ajaxRendered="true" inside <rich:message /> located on first tab
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: RF-12108
> URL: https://issues.jboss.org/browse/RF-12108
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.2.0.Final, 4.2.2.Final
> Environment: JDK1.6,
> JBoss 6.0.Final, JBoss 7.1.1.Final
> richfaces 4.1.0.Final/4.2.0.Final/4.2.2.Final
> seam 3.1
> IE 9, Chrome, Firefox
> Reporter: Artur Mioduszewski
> Assignee: Juraj Húska
> Labels: needs-qe
> Fix For: 4.5-Tracking
>
> Attachments: sample.xhtml
>
>
> In case getting 2 tabs (in my case it is primefaces tabs):
> {code:title=RENDERING ON SECOND TAB NOT WORKS (after clicking link)}
> First tab:
> <h:selectOneMenu id="nSurfacePercentageOfWholePlayback" value="#{newSurface.percentageOfWholePlayback}">
> <f:selectItems value="#{staticPercentagesItems}"/>
> </h:selectOneMenu>
> <rich:message for="nSurfacePercentageOfWholePlayback" ajaxRendered="true"/>
> Second tab (some code with ajax)
> Ex.
> <a4j:commandLink styleClass="no-decor" execute="@this" action="#{componentManager.deactivateVertically}">
> <h:graphicImage value="/images/icons/delete.gif" alt="Deactivate Vertically"/>
> <a4j:param value="#{dayIndex.index + 1}" assignTo="#{componentManager.verticalDeactivationIndex}"/>
> </a4j:commandLink>
> {code}
> {code:title=RENDERING ON SECOND TAB CORRECTLY WORKS (after clicking link)}
> First tab:
> <h:selectOneMenu id="nSurfacePercentageOfWholePlayback" value="#{newSurface.percentageOfWholePlayback}">
> <f:selectItems value="#{staticPercentagesItems}"/>
> </h:selectOneMenu>
> <rich:message for="nSurfacePercentageOfWholePlayback" ajaxRendered="false"/>
> Second tab (some code with ajax)
> Ex.
> <a4j:commandLink styleClass="no-decor" execute="@this" action="#{componentManager.deactivateVertically}">
> <h:graphicImage value="/images/icons/delete.gif" alt="Deactivate Vertically"/>
> <a4j:param value="#{dayIndex.index + 1}" assignTo="#{componentManager.verticalDeactivationIndex}"/>
> </a4j:commandLink>
> {code}
> When I change tabs order, problem does not exist.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months
[JBoss JIRA] (RF-13711) a4j:ajax status does not work as expected
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RF-13711?page=com.atlassian.jira.plugin.s... ]
Matej Novotny edited comment on RF-13711 at 7/10/14 8:51 AM:
-------------------------------------------------------------
Alright I made a little bit of research on this because I found out we have this kind of usage in [Showcase|http://showcase.richfaces.org/richfaces/component-sample.jsf?dem...] and also we have similar use case in Metamer. So here are the results...
What matters is, whether you have {{status}} attribute set or not. I will use following code snippet to explain in better.
{code:xml}
<h:form>
<a4j:status id="progress" onstart="console.log('start')" onstop="console.log('stop')" />
<h:commandButton value="Click">
<a4j:ajax event="click" status="progress" /> <!-- not working -->
</h:commandButton>
<h:commandButton value="ClickMe2">
<a4j:ajax event="click" /> <!-- working -->
</h:commandButton>
</h:form>
{code}
The first button with attached ajax behavior has status set. This button *will not work*. This behaviour is IMHO a bug.
The other button, however, *will work*. (Too see why a4j:status affects components which do not specifically use status attribute see [documentation|http://docs.jboss.org/richfaces/latest_4_3_X/Component_Refe...]). This is a correct solution but with more complex page, a4j:status might react on more requests than intended. But still I think this can be considered a workaround until we investigate further.
Using a4j:commandButton instead of h:commandButton behaves equally.
NOTE: a4j:status with facets works correctly (for this we have Metamer [page|http://localhost:8080/metamer/faces/components/a4jStatus/referencedUsage.xhtml]), the problem is with onstart/onstop/onerror which should execute JS code
Also I made a mistake placing the reproducer in a4j:ajax instead of a4j:status, I will move and also alter the reproducer accordingly to my findings. I will update the issue information as well.
[~rustock0] you can try the workaround I suggested, it might fit your needs better.
was (Author: manovotn):
Alright I made a little bit of research on this because I found out we have this kind of usage in [Showcase|http://showcase.richfaces.org/richfaces/component-sample.jsf?dem...] and also we have similar use case in Metamer. So here are the results...
What matters is, whether you have {{status}} attribute set or not. I will use following code snippet to explain in better.
{code:xml}
<h:form>
<a4j:status id="progress" onstart="console.log('start')" onstop="console.log('stop')" />
<h:commandButton value="Click">
<a4j:ajax event="click" status="progress" /> <!-- not working -->
</h:commandButton>
<h:commandButton value="ClickMe2">
<a4j:ajax event="click" /> <!-- working -->
</h:commandButton>
</h:form>
{code}
The first button with attached ajax behavior has status set. This button *will not work*. This behaviour is IMHO a bug.
The other button, however, *will work*. (Too see why a4j:status affects components which do not specifically use status attribute see [documentation|http://docs.jboss.org/richfaces/latest_4_3_X/Component_Refe...]). This is a correct solution but with more complex page, a4j:status might react on more requests than intended. But still I think this can be considered a workaround until we investigate further.
Using a4j:commandButton instead of h:commandButton behaves equally.
Also I made a mistake placing the reproducer in a4j:ajax instead of a4j:status, I will move and also alter the reproducer accordingly to my findings. I will update the issue information as well.
[~rustock0] you can try the workaround I suggested, it might fit your needs better.
> a4j:ajax status does not work as expected
> -----------------------------------------
>
> Key: RF-13711
> URL: https://issues.jboss.org/browse/RF-13711
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.7, 4.3.8
> Environment: IE8, Mozilla Firefox 30
> Reporter: Evgeny Mironenko
> Assignee: Matej Novotny
> Fix For: 4.5-Tracking
>
>
> Status attribute for {{a4j:ajax}} does not work as expected.
> I tried to create simple project with content:
> {code:title=index.xhtml}
> <?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:a4j="http://richfaces.org/a4j">
> <h:head>
> </h:head>
> <h:body>
> <a4j:status id="progress" onstart="console.log('start')"
> onstop="console.log('stop')"/>
> <div id="content">
> <h:form>
> <h:commandButton value="Click">
> <a4j:ajax event="click" status="progress" listener="#{testBean.invoke}"/>
> </h:commandButton>
> </h:form>
> </div>
> </h:body>
> </html>
> {code}
> It did not work for me. I do not see any log messages in the console.
> As workaround I can use the {{render}} attribute instead of {{status}}, but we use it for another goals, am I right?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months
[JBoss JIRA] (RF-13718) Update release guide for 4.5
by Michal Petrov (JIRA)
Michal Petrov created RF-13718:
----------------------------------
Summary: Update release guide for 4.5
Key: RF-13718
URL: https://issues.jboss.org/browse/RF-13718
Project: RichFaces
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 4.5.0.Alpha3
Reporter: Michal Petrov
The howto-release.adoc describes the release for RF 5 which doesn't seem to be applicable, the components/howto-release.adoc is for 4.5 components from when there were dependent on RF 5 core.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months
[JBoss JIRA] (RF-13711) a4j:ajax status does not work as expected
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RF-13711?page=com.atlassian.jira.plugin.s... ]
Matej Novotny commented on RF-13711:
------------------------------------
Alright I made a little bit of research on this because I found out we have this kind of usage in [Showcase|http://showcase.richfaces.org/richfaces/component-sample.jsf?dem...] and also we have similar use case in Metamer. So here are the results...
What matters is, whether you have {{status}} attribute set or not. I will use following code snippet to explain in better.
{code:xml}
<h:form>
<a4j:status id="progress" onstart="console.log('start')" onstop="console.log('stop')" />
<h:commandButton value="Click">
<a4j:ajax event="click" status="progress" /> <!-- not working -->
</h:commandButton>
<h:commandButton value="ClickMe2">
<a4j:ajax event="click" /> <!-- working -->
</h:commandButton>
</h:form>
{code}
The first button with attached ajax behavior has status set. This button *will not work*. This behaviour is IMHO a bug.
The other button, however, *will work*. (Too see why a4j:status affects components which do not specifically use status attribute see [documentation|http://docs.jboss.org/richfaces/latest_4_3_X/Component_Refe...]). This is a correct solution but with more complex page, a4j:status might react on more requests than intended. But still I think this can be considered a workaround until we investigate further.
Using a4j:commandButton instead of h:commandButton behaves equally.
Also I made a mistake placing the reproducer in a4j:ajax instead of a4j:status, I will move and also alter the reproducer accordingly to my findings. I will update the issue information as well.
[~rustock0] you can try the workaround I suggested, it might fit your needs better.
> a4j:ajax status does not work as expected
> -----------------------------------------
>
> Key: RF-13711
> URL: https://issues.jboss.org/browse/RF-13711
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.7, 4.3.8
> Environment: IE8, Mozilla Firefox 30
> Reporter: Evgeny Mironenko
> Assignee: Matej Novotny
> Fix For: 4.5-Tracking
>
>
> Status attribute for {{a4j:ajax}} does not work as expected.
> I tried to create simple project with content:
> {code:title=index.xhtml}
> <?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:a4j="http://richfaces.org/a4j">
> <h:head>
> </h:head>
> <h:body>
> <a4j:status id="progress" onstart="console.log('start')"
> onstop="console.log('stop')"/>
> <div id="content">
> <h:form>
> <h:commandButton value="Click">
> <a4j:ajax event="click" status="progress" listener="#{testBean.invoke}"/>
> </h:commandButton>
> </h:form>
> </div>
> </h:body>
> </html>
> {code}
> It did not work for me. I do not see any log messages in the console.
> As workaround I can use the {{render}} attribute instead of {{status}}, but we use it for another goals, am I right?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months
[JBoss JIRA] (RF-13660) RichFaces 4.5 integration tests - error after test execution
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13660?page=com.atlassian.jira.plugin.s... ]
Juraj Húska edited comment on RF-13660 at 7/10/14 7:43 AM:
-----------------------------------------------------------
I was trying to proceed with this issue, and I am not able to resolve it without further information.
My observations and questions:
* {{SystemEventListener}} is part of JSF, it is not included in any of the above mentioned jars.
* {{FrameworkDeployment}} creates jar which is IMHO equal to {{richfaces-core-4.5.0-SNAPSHOT.jar}}, do we need to have all of them in deployed war ?
* why {{FrameworkDeployment}} is working only with core, and {{org.richfaces:richfaces-a4j:4.5.0-SNAPSHOT}} and with rich components as well ?
Because [~michpetrov] advised me that it is indeed a test issue, not the framework one, and after discussion with [~ppitonak], I would opt for shifting this issue to Beta1 sprint to not to delay 4.5.0.Alpha3 staging.
was (Author: jhuska):
I was trying to proceed with this issue, and I am not able to resolve it without further information.
My observations a questions:
* {{SystemEventListener}} is part of JSF, it is not included in any of the above mentioned jars.
* {{FrameworkDeployment}} creates jar which is IMHO equal to {{richfaces-core-4.5.0-SNAPSHOT.jar}}, do we need to have all of them in deployed war ?
* why {{FrameworkDeployment}} is working only with core, and {{org.richfaces:richfaces-a4j:4.5.0-SNAPSHOT}} and with rich components as well ?
Because [~michpetrov] advised me that it is indeed a test issue, not the framework one, and after discussion with [~ppitonak], I would opt for shifting this issue to Beta1 sprint to not to delay 4.5.0.Alpha3 staging.
> RichFaces 4.5 integration tests - error after test execution
> ------------------------------------------------------------
>
> Key: RF-13660
> URL: https://issues.jboss.org/browse/RF-13660
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 4.5.0.Alpha2
> Environment: AS: Wildfly
> Browser: PhantomJS
> Reporter: Matej Novotny
> Assignee: Juraj Húska
> Fix For: 4.5.0.Alpha3
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> This issue originated from RF-13591.
> There is an error in server log after execution of [ITResourceMapping|https://github.com/richfaces/richfaces/blob/4.5.x/core/...].
> The test itself passes (use PhantomJS) and afterwards there is an error in server console. This does not affect the build as everything gets completed however it results in Jenkins job failure on some machines.
> Currently the Jenkins job passes (machine running the tests was changed) but before it was failing after execution of this particular test. See the [Jenkins job resulsts|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/...].
> The exception in server console is:
> {code}
> 12:36:37,481 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-1) Unexpected exception when attempting to tear down the Mojarra runtime: java.lang.NullPointerException
> at org.richfaces.application.ServiceTracker.release(ServiceTracker.java:135) [richfaces.jar:]
> at org.richfaces.application.InitializationListener.onStop(InitializationListener.java:93) [richfaces.jar:]
> at org.richfaces.application.InitializationListener.processEvent(InitializationListener.java:165) [richfaces.jar:]
> at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5]
> at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) [jsf-impl-2.2.5-jbossorg-3.jar:]
> at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) [jsf-impl-2.2.5-jbossorg-3.jar:]
> at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:303) [jsf-impl-2.2.5-jbossorg-3.jar:]
> at org.jboss.as.jsf.injection.weld.ForwardingApplication.publishEvent(ForwardingApplication.java:294) [wildfly-jsf-injection-8.0.0.Final.jar:8.0.0.Final]
> at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:314) [jsf-impl-2.2.5-jbossorg-3.jar:]
> at io.undertow.servlet.core.ApplicationListeners.contextDestroyed(ApplicationListeners.java:185) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.core.DeploymentImpl.destroy(DeploymentImpl.java:216) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.core.DeploymentManagerImpl.undeploy(DeploymentManagerImpl.java:557) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:117)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stop(UndertowDeploymentService.java:100)
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056)
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months
[JBoss JIRA] (RF-13660) RichFaces 4.5 integration tests - error after test execution
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13660?page=com.atlassian.jira.plugin.s... ]
Juraj Húska edited comment on RF-13660 at 7/10/14 7:40 AM:
-----------------------------------------------------------
I was trying to proceed with this issue, and I am not able to resolve it without further information.
My observations a questions:
* {{SystemEventListener}} is part of JSF, it is not included in any of the above mentioned jars.
* {{FrameworkDeployment}} creates jar which is IMHO equal to {{richfaces-core-4.5.0-SNAPSHOT.jar}}, do we need to have all of them in deployed war ?
* why {{FrameworkDeployment}} is working only with core, and {{org.richfaces:richfaces-a4j:4.5.0-SNAPSHOT}} and with rich components as well ?
Because [~michpetrov] advised me that it is indeed a test issue, not the framework one, and after discussion with [~ppitonak], I would opt for shifting this issue to Beta1 sprint to not to delay 4.5.0.Alpha3 staging.
was (Author: jhuska):
I was trying to proceed with this issue, and I am not able to resolve it without further information.
My observations a questions:
* {{SystemEventListener}} is part of JSF, it is not included in any of the above mentioned jars.
* {{FrameworkDeployment}} creates jar which is IMHO equal to {{richfaces-core-4.5.0-SNAPSHOT.jar}}, do we need to have all of them in deployed war ?
* why {{FrameworkDeployment}} is working only with core, and {{org.richfaces:richfaces-a4j:4.5.0-SNAPSHOT}} and with rich components as well ?
Because [~michpetrov] advised me that it is indeed a test issue, not the framework one, and after discussion with [~ppitonak], I would opt for shifting this issue to Beta1 sprint.
> RichFaces 4.5 integration tests - error after test execution
> ------------------------------------------------------------
>
> Key: RF-13660
> URL: https://issues.jboss.org/browse/RF-13660
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 4.5.0.Alpha2
> Environment: AS: Wildfly
> Browser: PhantomJS
> Reporter: Matej Novotny
> Assignee: Juraj Húska
> Fix For: 4.5.0.Alpha3
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> This issue originated from RF-13591.
> There is an error in server log after execution of [ITResourceMapping|https://github.com/richfaces/richfaces/blob/4.5.x/core/...].
> The test itself passes (use PhantomJS) and afterwards there is an error in server console. This does not affect the build as everything gets completed however it results in Jenkins job failure on some machines.
> Currently the Jenkins job passes (machine running the tests was changed) but before it was failing after execution of this particular test. See the [Jenkins job resulsts|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/...].
> The exception in server console is:
> {code}
> 12:36:37,481 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-1) Unexpected exception when attempting to tear down the Mojarra runtime: java.lang.NullPointerException
> at org.richfaces.application.ServiceTracker.release(ServiceTracker.java:135) [richfaces.jar:]
> at org.richfaces.application.InitializationListener.onStop(InitializationListener.java:93) [richfaces.jar:]
> at org.richfaces.application.InitializationListener.processEvent(InitializationListener.java:165) [richfaces.jar:]
> at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5]
> at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) [jsf-impl-2.2.5-jbossorg-3.jar:]
> at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) [jsf-impl-2.2.5-jbossorg-3.jar:]
> at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:303) [jsf-impl-2.2.5-jbossorg-3.jar:]
> at org.jboss.as.jsf.injection.weld.ForwardingApplication.publishEvent(ForwardingApplication.java:294) [wildfly-jsf-injection-8.0.0.Final.jar:8.0.0.Final]
> at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:314) [jsf-impl-2.2.5-jbossorg-3.jar:]
> at io.undertow.servlet.core.ApplicationListeners.contextDestroyed(ApplicationListeners.java:185) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.core.DeploymentImpl.destroy(DeploymentImpl.java:216) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.core.DeploymentManagerImpl.undeploy(DeploymentManagerImpl.java:557) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:117)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stop(UndertowDeploymentService.java:100)
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056)
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months