September 2013 - richfaces-issues

[JBoss JIRA] (RF-13217) RichFaces 5 framework tests sporadically get stuck

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13217?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13217: --------------------------------- Tests fail on both, EAP 6.1 and AS 7.1 in {{ITRegionRichAjax}} test. > RichFaces 5 framework tests sporadically get stuck > -------------------------------------------------- > > Key: RF-13217 > URL: https://issues.jboss.org/browse/RF-13217 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha2 > Reporter: Lukáš Fryč > > This happens after upgrade of Graphene to Beta2 and Warp to snapshot: > https://github.com/richfaces/richfaces/commit/7de83449e60c81fcf51df5247ca... > We need to investigate what is a cause of failure since it's not evident from the debug logs. > {{mvn verify -Dintegration=jbosseap61 -Dsmoke -DskipTests=true -Darquillian.debug=true -Doptimization.skip -Dgeneration.skip -Darquillian.container.distribution=file:///home/lfryc/Distributions/jboss-eap-6.1.0-Final.zip}} -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13217) RichFaces 5 framework tests sporadically get stuck

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13217?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13217: --------------------------------- On this place the test is stuck ([whole log|https://gist.github.com/lfryc/ce01e446850cb37b614f]): {code} Running org.richfaces.ui.region.ITRegionRichAjax ... (E) Test (I) TestContextHandler.createSuiteContext (I) TestContextHandler.createClassContext (E) TestClass (I) TestContextHandler.createTestContext (I) ContainerEventController.createTestContext (O) ClientTestExecuter.execute (E) ExecutionEvent (O) LocalTestExecuter.execute (E) ExecuteWarp (I) WarpExecutionInitializer.provideWarpContext (E) WarpContext (E) SynchronizationPoint (O) WarpExecutionObserver.executeWarp (E) AdvertiseEnrichment (O) WarpExecutionObserver.advertiseEnrichment (E) FinishEnrichment (O) WarpExecutionObserver.finishEnrichment (E) Activity (O) WarpExecutionObserver.executeActivity (E) AwaitResponse (O) WarpExecutionObserver.awaitResponse (E) CleanEnrichment (O) WarpExecutionObserver.cleanEnrichment (E) ExecuteWarp (I) WarpExecutionInitializer.provideWarpContext (E) WarpContext (E) SynchronizationPoint (O) WarpExecutionObserver.executeWarp (E) AdvertiseEnrichment (O) WarpExecutionObserver.advertiseEnrichment (E) FinishEnrichment (O) WarpExecutionObserver.finishEnrichment (E) Activity (O) WarpExecutionObserver.executeActivity (E) AwaitResponse (O) WarpExecutionObserver.awaitResponse (E) CleanEnrichment (O) WarpExecutionObserver.cleanEnrichment (E) TestResult (E) After (I) TestContextHandler.createSuiteContext (I) TestContextHandler.createClassContext (E) TestClass (I) TestContextHandler.createTestContext (I) ContainerEventController.createAfterContext (I) CreationalContextDestroyer.destory (O) FailureScreenshot.takeScreenshotOnFailure (O) ClientBeforeAfterLifecycleEventExecuter.on (O) RemoteSuiteLifecyclePropagation.sendAfter (O) ClassProxyUsageTracker.unregisterOperationalContext (O) DroneDestructor.destroyMethodScopedDrone (O) CommandBusObserver.afterTest (E) StopBus (O) CommandBusObserver.stopEventBus Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.793 sec {code} > RichFaces 5 framework tests sporadically get stuck > -------------------------------------------------- > > Key: RF-13217 > URL: https://issues.jboss.org/browse/RF-13217 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha2 > Reporter: Lukáš Fryč > > This happens after upgrade of Graphene to Beta2 and Warp to snapshot: > https://github.com/richfaces/richfaces/commit/7de83449e60c81fcf51df5247ca... > We need to investigate what is a cause of failure since it's not evident from the debug logs. > {{mvn verify -Dintegration=jbosseap61 -Dsmoke -DskipTests=true -Darquillian.debug=true -Doptimization.skip -Dgeneration.skip -Darquillian.container.distribution=file:///home/lfryc/Distributions/jboss-eap-6.1.0-Final.zip}} -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13218) Check existence of src/main/widgets with enforcer plugin

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-13218: ------------------------------- Summary: Check existence of src/main/widgets with enforcer plugin Key: RF-13218 URL: https://issues.jboss.org/browse/RF-13218 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: build/distribution Affects Versions: 5.0.0.Alpha1 Reporter: Lukáš Fryč RichFaces 5 may fail when {{src/main/widgets}} aren't checked out properly. I suggest to use enforcer plugin to check that e.g. {{src/main/widgets/Grunfile.js}} file exists: http://maven.apache.org/enforcer/enforcer-rules/requireFilesExist.html -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13217) RichFaces 5 framework tests sporadically get stuck

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13217?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13217: ---------------------------- Description: This happens after upgrade of Graphene to Beta2 and Warp to snapshot: https://github.com/richfaces/richfaces/commit/7de83449e60c81fcf51df5247ca... We need to investigate what is a cause of failure since it's not evident from the debug logs. {code} mvn verify -Dintegration=jbosseap61 -Dsmoke -DskipTests=true -Darquillian.debug=true -Doptimization.skip -Dgeneration.skip -Darquillian.container.distribution=file:///home/lfryc/Distributions/jboss-eap-6.1.0-Final.zip {code} was: This happens after upgrade of Graphene to Beta2 and Warp to snapshot: https://github.com/richfaces/richfaces/commit/7de83449e60c81fcf51df5247ca... We need to investigate what is a cause of failure since it's not evident from the debug logs. > RichFaces 5 framework tests sporadically get stuck > -------------------------------------------------- > > Key: RF-13217 > URL: https://issues.jboss.org/browse/RF-13217 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha2 > Reporter: Lukáš Fryč > > This happens after upgrade of Graphene to Beta2 and Warp to snapshot: > https://github.com/richfaces/richfaces/commit/7de83449e60c81fcf51df5247ca... > We need to investigate what is a cause of failure since it's not evident from the debug logs. > {code} > mvn verify -Dintegration=jbosseap61 -Dsmoke -DskipTests=true -Darquillian.debug=true -Doptimization.skip -Dgeneration.skip -Darquillian.container.distribution=file:///home/lfryc/Distributions/jboss-eap-6.1.0-Final.zip > {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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13217) RichFaces 5 framework tests sporadically get stuck

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13217?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13217: ---------------------------- Description: This happens after upgrade of Graphene to Beta2 and Warp to snapshot: https://github.com/richfaces/richfaces/commit/7de83449e60c81fcf51df5247ca... We need to investigate what is a cause of failure since it's not evident from the debug logs. {{mvn verify -Dintegration=jbosseap61 -Dsmoke -DskipTests=true -Darquillian.debug=true -Doptimization.skip -Dgeneration.skip -Darquillian.container.distribution=file:///home/lfryc/Distributions/jboss-eap-6.1.0-Final.zip}} was: This happens after upgrade of Graphene to Beta2 and Warp to snapshot: https://github.com/richfaces/richfaces/commit/7de83449e60c81fcf51df5247ca... We need to investigate what is a cause of failure since it's not evident from the debug logs. {code} mvn verify -Dintegration=jbosseap61 -Dsmoke -DskipTests=true -Darquillian.debug=true -Doptimization.skip -Dgeneration.skip -Darquillian.container.distribution=file:///home/lfryc/Distributions/jboss-eap-6.1.0-Final.zip {code} > RichFaces 5 framework tests sporadically get stuck > -------------------------------------------------- > > Key: RF-13217 > URL: https://issues.jboss.org/browse/RF-13217 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha2 > Reporter: Lukáš Fryč > > This happens after upgrade of Graphene to Beta2 and Warp to snapshot: > https://github.com/richfaces/richfaces/commit/7de83449e60c81fcf51df5247ca... > We need to investigate what is a cause of failure since it's not evident from the debug logs. > {{mvn verify -Dintegration=jbosseap61 -Dsmoke -DskipTests=true -Darquillian.debug=true -Doptimization.skip -Dgeneration.skip -Darquillian.container.distribution=file:///home/lfryc/Distributions/jboss-eap-6.1.0-Final.zip}} -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13217) RichFaces 5 framework tests sporadically get stuck

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-13217: ------------------------------- Summary: RichFaces 5 framework tests sporadically get stuck Key: RF-13217 URL: https://issues.jboss.org/browse/RF-13217 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: tests - functional Affects Versions: 5.0.0.Alpha2 Reporter: Lukáš Fryč This happens after upgrade of Graphene to Beta2 and Warp to snapshot: https://github.com/richfaces/richfaces/commit/7de83449e60c81fcf51df5247ca... We need to investigate what is a cause of failure since it's not evident from the debug logs. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13216) PoupPanel doesn't disappear when rendered="false" and rerender it.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RF-13216?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration updated RF-13216: ----------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1011466 > PoupPanel doesn't disappear when rendered="false" and rerender it. > ------------------------------------------------------------------ > > Key: RF-13216 > URL: https://issues.jboss.org/browse/RF-13216 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.3 > Reporter: Takayuki Konishi > Attachments: rf3_3_4-modalpanel.zip, rf4_3_3-popuppanel.zip > > > If you use the richfaces popupPanel in the default domElementAttachment="body" mode it will not disappear under specific conditions. > {code:xml} > <h:body title="page 1"> > <a4j:outputPanel id="myPanel"> > <rich:popupPanel domElementAttachment="body" show="true" rendered="#{test.showPopup}"> > <h:form> > <a4j:commandButton action="#{test.switchPopup()}" value="switch off" render="myPanel"/> > </h:form> > </rich:popupPanel> > <h:form> > <a4j:commandButton action="#{test.switchPopup()}" value="switch on" render="myPanel"/> > </h:form> > </a4j:outputPanel> > </h:body> > {code} > In Richfaces 3.3.x, on the other hand, there was a component cleanup system ({{memory.js _cleanComponentNodes}}) which was responsible to remove components after ajax calls if the component was removed from the current view. > Therefore the above example (revert {{popupPanel}} to {{modalPanel}}) works in RF3.3.4.Final. > Note: > In case {{domElementAttachment="parent"}}, it will show [the other JSF2 bug|https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-790] where the view state was lost, therefore you must click the action button twice to really call the function. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13216) PoupPanel doesn't disappear when rendered="false" and rerender it.

by Takayuki Konishi (JIRA)

[ https://issues.jboss.org/browse/RF-13216?page=com.atlassian.jira.plugin.s... ] Takayuki Konishi updated RF-13216: ---------------------------------- Attachment: rf3_3_4-modalpanel.zip > PoupPanel doesn't disappear when rendered="false" and rerender it. > ------------------------------------------------------------------ > > Key: RF-13216 > URL: https://issues.jboss.org/browse/RF-13216 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.3 > Reporter: Takayuki Konishi > Attachments: rf3_3_4-modalpanel.zip, rf4_3_3-popuppanel.zip > > > If you use the richfaces popupPanel in the default domElementAttachment="body" mode it will not disappear under specific conditions. > {code:xml} > <h:body title="page 1"> > <a4j:outputPanel id="myPanel"> > <rich:popupPanel domElementAttachment="body" show="true" rendered="#{test.showPopup}"> > <h:form> > <a4j:commandButton action="#{test.switchPopup()}" value="switch off" render="myPanel"/> > </h:form> > </rich:popupPanel> > <h:form> > <a4j:commandButton action="#{test.switchPopup()}" value="switch on" render="myPanel"/> > </h:form> > </a4j:outputPanel> > </h:body> > {code} > In Richfaces 3.3.x, on the other hand, there was a component cleanup system ({{memory.js _cleanComponentNodes}}) which was responsible to remove components after ajax calls if the component was removed from the current view. > Therefore the above example (revert {{popupPanel}} to {{modalPanel}}) works in RF3.3.4.Final. > Note: > In case {{domElementAttachment="parent"}}, it will show [the other JSF2 bug|https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-790] where the view state was lost, therefore you must click the action button twice to really call the function. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13216) PoupPanel doesn't disappear when rendered="false" and rerender it.

by Takayuki Konishi (JIRA)

[ https://issues.jboss.org/browse/RF-13216?page=com.atlassian.jira.plugin.s... ] Takayuki Konishi commented on RF-13216: --------------------------------------- rf3_3_4-modalpanel.zip is a test case for modalPanel in RF 3.3.4 and the test page is: http://localhost:8080/test/popup.jsf > PoupPanel doesn't disappear when rendered="false" and rerender it. > ------------------------------------------------------------------ > > Key: RF-13216 > URL: https://issues.jboss.org/browse/RF-13216 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.3 > Reporter: Takayuki Konishi > Attachments: rf3_3_4-modalpanel.zip, rf4_3_3-popuppanel.zip > > > If you use the richfaces popupPanel in the default domElementAttachment="body" mode it will not disappear under specific conditions. > {code:xml} > <h:body title="page 1"> > <a4j:outputPanel id="myPanel"> > <rich:popupPanel domElementAttachment="body" show="true" rendered="#{test.showPopup}"> > <h:form> > <a4j:commandButton action="#{test.switchPopup()}" value="switch off" render="myPanel"/> > </h:form> > </rich:popupPanel> > <h:form> > <a4j:commandButton action="#{test.switchPopup()}" value="switch on" render="myPanel"/> > </h:form> > </a4j:outputPanel> > </h:body> > {code} > In Richfaces 3.3.x, on the other hand, there was a component cleanup system ({{memory.js _cleanComponentNodes}}) which was responsible to remove components after ajax calls if the component was removed from the current view. > Therefore the above example (revert {{popupPanel}} to {{modalPanel}}) works in RF3.3.4.Final. > Note: > In case {{domElementAttachment="parent"}}, it will show [the other JSF2 bug|https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-790] where the view state was lost, therefore you must click the action button twice to really call the function. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13216) PoupPanel doesn't disappear when rendered="false" and rerender it.

by Takayuki Konishi (JIRA)

[ https://issues.jboss.org/browse/RF-13216?page=com.atlassian.jira.plugin.s... ] Takayuki Konishi updated RF-13216: ---------------------------------- Attachment: rf4_3_3-popuppanel.zip > PoupPanel doesn't disappear when rendered="false" and rerender it. > ------------------------------------------------------------------ > > Key: RF-13216 > URL: https://issues.jboss.org/browse/RF-13216 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.3 > Reporter: Takayuki Konishi > Attachments: rf4_3_3-popuppanel.zip > > > If you use the richfaces popupPanel in the default domElementAttachment="body" mode it will not disappear under specific conditions. > {code:xml} > <h:body title="page 1"> > <a4j:outputPanel id="myPanel"> > <rich:popupPanel domElementAttachment="body" show="true" rendered="#{test.showPopup}"> > <h:form> > <a4j:commandButton action="#{test.switchPopup()}" value="switch off" render="myPanel"/> > </h:form> > </rich:popupPanel> > <h:form> > <a4j:commandButton action="#{test.switchPopup()}" value="switch on" render="myPanel"/> > </h:form> > </a4j:outputPanel> > </h:body> > {code} > In Richfaces 3.3.x, on the other hand, there was a component cleanup system ({{memory.js _cleanComponentNodes}}) which was responsible to remove components after ajax calls if the component was removed from the current view. > Therefore the above example (revert {{popupPanel}} to {{modalPanel}}) works in RF3.3.4.Final. > Note: > In case {{domElementAttachment="parent"}}, it will show [the other JSF2 bug|https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-790] where the view state was lost, therefore you must click the action button twice to really call the function. -- 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, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues September 2013