[JBoss JIRA] (RF-12533) UIDataAdaptor throws NPE with disabled PSS (webflow 2.3)
by David Rawlings (JIRA)
[ https://issues.jboss.org/browse/RF-12533?page=com.atlassian.jira.plugin.s... ]
David Rawlings updated RF-12533:
--------------------------------
Attachment: TreeStructureManager.java
I had the same problem, using webflow 2.3.1, myfaces 2.1.12 and RichFaces 4.3.3.Final. I'm not sure what the 'correct' fix is, but I've implemented the attached patch (spring faces 2.3.1 TreeStructureManager) that seems to work ok. I've added comments in the attached source to show where the patch starts/finishes.
I'm no myfaces/webflow/RichFaces expert so use at your own risk...
> UIDataAdaptor throws NPE with disabled PSS (webflow 2.3)
> --------------------------------------------------------
>
> Key: RF-12533
> URL: https://issues.jboss.org/browse/RF-12533
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.2.Final, 4.2.3.CR1, 4.3.0.M1
> Environment: spring webflow 2.3.1, myfaces-impl 2.1.8
> Reporter: Anton Zukovskij
> Priority: Critical
> Labels: partial_state_saving, spring
> Fix For: 5-Tracking
>
> Attachments: log-2.txt, log.txt, swf-rf4.zip, TreeStructureManager.java
>
>
> When partial state saving is disabled(javax.faces.PARTIAL_STATE_SAVING=false), nullpointer exception is thrown during restore state phase of webflow rendered view that contains UIDataAdaptor component. In other words NPE exception is thrown on every page submit of webflow rendered views that contain components that exted UIDataAdaptor. Please see log attached and sample application.
--
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
[JBoss JIRA] (RF-13377) NullPointerException in calendar page fragment
by Pavol Pitonak (JIRA)
Pavol Pitonak created RF-13377:
----------------------------------
Summary: NullPointerException in calendar page fragment
Key: RF-13377
URL: https://issues.jboss.org/browse/RF-13377
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: page-fragments
Affects Versions: 5.0.0.Alpha2
Environment: RichFaces 5.0.0-SNAPSHOT
Metamer 5.0.0-SNAPSHOT
Reporter: Pavol Pitonak
# run a Metamer test for r:calendar using page fragments, e.g.
{code}
mvn clean verify -P jbossas-managed-7-1 -Dtest=TestCalendarAttributes
{code}
result:
* all tests are skipped because a NPE in calendar page fragment
{quote}
*org.jboss.arquillian.graphene.enricher.exception.PageFragmentInitializationException: java.lang.reflect.InvocationTargetException*
at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.createPageFragment(PageFragmentEnricher.java:171)
at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.setupPageFragment(PageFragmentEnricher.java:208)
at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.enrich(PageFragmentEnricher.java:85)
at org.jboss.arquillian.graphene.enricher.GrapheneEnricher.enrich(GrapheneEnricher.java:51)
at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52)
at org.jboss.arquillian.container.test.impl.ClientTestInstanceEnricher.enrich(ClientTestInstanceEnricher.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:95)
at org.jboss.arquillian.testng.Arquillian.arquillianBeforeTest(Arquillian.java:130)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:613)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
at org.testng.TestRunner.privateRun(TestRunner.java:757)
at org.testng.TestRunner.run(TestRunner.java:608)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
at org.testng.TestNG.run(TestNG.java:999)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:91)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:128)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:112)
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:113)
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
*Caused by: java.lang.reflect.InvocationTargetException*
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at org.jboss.arquillian.graphene.enricher.AbstractSearchContextEnricher.instantiate(AbstractSearchContextEnricher.java:174)
at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.createPageFragment(PageFragmentEnricher.java:144)
... 76 more
*Caused by: java.lang.NullPointerException: configuration is null - it needs to be setup before starting to use it*
at org.richfaces.fragment.configuration.RichFacesPageFragmentsConfigurationContext.get(RichFacesPageFragmentsConfigurationContext.java:43)
at org.richfaces.fragment.configuration.RichFacesPageFragmentsConfigurationContext$2.getTarget(RichFacesPageFragmentsConfigurationContext.java:97)
at org.richfaces.fragment.configuration.RichFacesPageFragmentsConfigurationContext$1.invoke(RichFacesPageFragmentsConfigurationContext.java:57)
at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.intercept(GrapheneProxyHandler.java:92)
at org.richfaces.fragment.configuration.RichFacesPageFragmentsConfiguration$$EnhancerByGraphene$$e41cfe31.isUseJSInteractionStrategy(<generated>)
at org.richfaces.fragment.calendar.RichFacesCalendar.<init>(RichFacesCalendar.java:52)
... 82 more
{quote}
--
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
[JBoss JIRA] (RF-13374) RichFaces push registered as $.fn.push overrides jQuery function
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13374?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč resolved RF-13374.
-----------------------------
Resolution: Done
> RichFaces push registered as $.fn.push overrides jQuery function
> ----------------------------------------------------------------
>
> Key: RF-13374
> URL: https://issues.jboss.org/browse/RF-13374
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-push/poll
> Affects Versions: 5.0.0.Alpha2
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Priority: Blocker
> Fix For: 5.0.0.Alpha2
>
>
> The real cause of an issue mentioned in RF-13359 isn't an invalid implementation of _destroy method (RF-13371), but rather conflict caused by registering $.fn.push function.
> The solution is to rename that jQuery function, e.g. {{$.fn.richfacespush}} or namespace it in other way (e.g. {{$.fn.rf.push}} - question is how it would be called then). Let's investigate further how we can namespace our jQuery plugins.
--
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
[JBoss JIRA] (RF-13365) push: cannot be disabled with ajax request
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13365?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč resolved RF-13365.
-----------------------------
Resolution: Done
I believe the original issue is resolved now. Let's higher the priority of RF-12543 to get a fix for re-rendered Push.
> push: cannot be disabled with ajax request
> ------------------------------------------
>
> Key: RF-13365
> URL: https://issues.jboss.org/browse/RF-13365
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 5.0.0.Alpha2
> Environment: EAP 6.1, Glassfish 3.1.2.2
> FF 25, Chrome 31
> Reporter: Jiří Štefek
> Assignee: Lukáš Fryč
> Labels: regression
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> Worked in 4.3.4.Final.
--
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
[JBoss JIRA] (RF-13365) push: cannot be disabled with ajax request
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13365?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč edited comment on RF-13365 at 11/22/13 8:14 AM:
-----------------------------------------------------------
Disabling now works fine as can be seen in commited dev sample in push-demo (the inability to function correctly was caused by wrong destroy logic - RF-13371)
However it takes time before the Push start to work again - I believe this issue might be related to RF-12543.
was (Author: lfryc):
Disabling now works fine as can be seen in commited dev sample in push-demo.
However it takes time before the Push start to work again - I believe this issue might be related to RF-12543.
> push: cannot be disabled with ajax request
> ------------------------------------------
>
> Key: RF-13365
> URL: https://issues.jboss.org/browse/RF-13365
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 5.0.0.Alpha2
> Environment: EAP 6.1, Glassfish 3.1.2.2
> FF 25, Chrome 31
> Reporter: Jiří Štefek
> Assignee: Lukáš Fryč
> Labels: regression
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> Worked in 4.3.4.Final.
--
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
[JBoss JIRA] (RF-13365) push: cannot be disabled with ajax request
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13365?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13365:
---------------------------------
Disabling now works fine as can be seen in commited dev sample in push-demo.
However it takes time before the Push start to work again - I believe this issue might be related to RF-12543.
> push: cannot be disabled with ajax request
> ------------------------------------------
>
> Key: RF-13365
> URL: https://issues.jboss.org/browse/RF-13365
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 5.0.0.Alpha2
> Environment: EAP 6.1, Glassfish 3.1.2.2
> FF 25, Chrome 31
> Reporter: Jiří Štefek
> Assignee: Lukáš Fryč
> Labels: regression
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> Worked in 4.3.4.Final.
--
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
[JBoss JIRA] (RF-13376) Visual issues when updated to RW with RCUE theme
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13376?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-13376:
----------------------------
Description:
Fonts {{Open Sans}} can't be loadedin the component-demo.
I can't reproduce this issue in Showcase.
----
Additionally we should review demos that they all still look correctly.
----
I suggest to disable default controls (buttons/inputs/...) skinning so that the themes RichFaces/RichWidgets do not conflict.
was:
Fonts {{Open Sans}} can't be loadedin the component-demo.
I can't reproduce this issue in Showcase.
----
Additionally we should review demos that they all still look correctly.
----
I would suggest to disable default controls (buttons/inputs/...) skinning so that the themes RichFaces/RichWidgets do not conflict.
> Visual issues when updated to RW with RCUE theme
> ------------------------------------------------
>
> Key: RF-13376
> URL: https://issues.jboss.org/browse/RF-13376
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component, examples, showcase
> Affects Versions: 5.0.0.Alpha2
> Reporter: Lukáš Fryč
> Fix For: 5.0.0.Alpha2
>
>
> Fonts {{Open Sans}} can't be loadedin the component-demo.
> I can't reproduce this issue in Showcase.
> ----
> Additionally we should review demos that they all still look correctly.
> ----
> I suggest to disable default controls (buttons/inputs/...) skinning so that the themes RichFaces/RichWidgets do not conflict.
--
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