[JBoss JIRA] (RF-13378) extendedDataTable not shown inside Bootstrap tab panel
by Salvo Isaja (JIRA)
Salvo Isaja created RF-13378:
--------------------------------
Summary: extendedDataTable not shown inside Bootstrap tab panel
Key: RF-13378
URL: https://issues.jboss.org/browse/RF-13378
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-tables
Affects Versions: 4.3.4
Environment: Tested on Ubuntu 12.04, Firefox 25, JDK 7u45, GlassFish 3.1.2.2
Reporter: Salvo Isaja
As described in RF-12682, when an extendedDataTable is placed in a parent which is not displayed by default, showing the parent causes the table to be invisible. This was reported to be solved on 4.3.2 for tables inside rich:tabPanel, while this issue is on 4.3.4 for tables inside a tab panel from Bootstrap 3.
Attached a minimal project which demonstrates the issue.
Thanks.
--
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 Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13376?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13376:
------------------------------------
[~lfryc] I suggest we address this along with theming in 5.0.0.Alpha3?
> 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
[JBoss JIRA] (RF-13376) Visual issues when updated to RW with RCUE theme
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13376?page=com.atlassian.jira.plugin.s... ]
Brian Leathem edited comment on RF-13376 at 11/22/13 2:41 PM:
--------------------------------------------------------------
[~lfryc] I suggest we address this along with theming in 5.0.0.Alpha3.
was (Author: bleathem):
[~lfryc] I suggest we address this along with theming in 5.0.0.Alpha3?
> 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
[JBoss JIRA] (RF-13377) NullPointerException in calendar page fragment
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13377?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-13377:
----------------------------------
Assignee: Pavol Pitonak
Pavol, page fragments are owned by QE. Please assess, schedule, and assign this issue as you see fit.
> 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
> Assignee: 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-6678) RichFaces Select components: implement disabled state support for selectItem
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-6678?page=com.atlassian.jira.plugin.sy... ]
Brian Leathem reassigned RF-6678:
---------------------------------
Assignee: Pavol Pitonak
QE, would you please confirm one way or another the status of disabled SelectItems in select and inplaceSelect components?
> RichFaces Select components: implement disabled state support for selectItem
> ----------------------------------------------------------------------------
>
> Key: RF-6678
> URL: https://issues.jboss.org/browse/RF-6678
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 4.0.0.Milestone5
> Reporter: Ilya Shaikovsky
> Assignee: Pavol Pitonak
> Fix For: 5-Tracking
>
>
> components:
> inplaceSelect
> select
> In future we should support the same in:
> listShuttle
> orderingList
> note: s:selectItems disabled attribute should also works fine.
--
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-13371) Clarify and fix Push destroy logic
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13371?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13371:
-------------------------------
Description:
I need to comment on the approach I took for destroying the Push component which follows approximately what Widget Factory does.
I have also found that the widget _destroy method isn't called at all, because there is no such event as {{cleanDom}}.
richfaces.js throws {{beforeDomClean}} and {{afterDomClean}}. The foremost is the right event to listen for for component cleanup.
was:
I need to commend on the approach I take for destroying Push component which follows approximately what Widget Factory does.
I have also found that the widget _destro method isn't called at all, because there is no such event as {{cleanDom}}.
richfaces.js throws {{beforeDomClean}} and {{afterDomClean}}. The foremost is the right event to listen for for component cleanup.
> Clarify and fix Push destroy logic
> ----------------------------------
>
> Key: RF-13371
> URL: https://issues.jboss.org/browse/RF-13371
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Priority: Critical
> Fix For: 5.0.0.Alpha2
>
>
> I need to comment on the approach I took for destroying the Push component which follows approximately what Widget Factory does.
> I have also found that the widget _destroy method isn't called at all, because there is no such event as {{cleanDom}}.
> richfaces.js throws {{beforeDomClean}} and {{afterDomClean}}. The foremost is the right event to listen for for component cleanup.
--
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-12533) UIDataAdaptor throws NPE with disabled PSS (webflow 2.3)
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12533?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-12533:
------------------------------------
Is there a corresponding Spring Webflow issue tracking this?
> 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-10131) Improve SelectItem(s) handling compatibility with JSF 2.0
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-10131?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-10131:
------------------------------------
This issue states it was resolved in the select and inplaceSelect components. RF-4491 address seeing this impl'ed in the pick and ordering list.
> Improve SelectItem(s) handling compatibility with JSF 2.0
> ---------------------------------------------------------
>
> Key: RF-10131
> URL: https://issues.jboss.org/browse/RF-10131
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: compatibility
> Environment: myfaces 2.0.3, richfaces 4.0 trunk rev. 20883
> Reporter: Martin Kočí
> Assignee: Gleb Galkin
> Fix For: 4.0.0.Milestone6
>
>
> 1) JSF 2.0 specifies new attributes itemLabel, itemDescription and itemDisabled for f:selectItem(s). Unfortunately those attributes are not part of public API but every renderkit must reimplement it again in own code base. RichFaces org.richfaces.component.util.SelectUtils.getSelectItems(FacesContext, UIComponent) currently support only old JSF 1.2 style (SelectItem instances are obtained from value="#{}").
> Implement support for f:selectItems value="#{}" var="variable"
> itemLabel="#{...}" itemValue="#{...}"/>
> 2) null or empty SelectItems handling: o.j.rf.SelectUtils throws an exception if no SelectItem(s) are available. If think this is too agressive and not very useful for user. I suggest to use myfaces-like solution: a warning in development stage like:
> WARNING: ValueExpression #{de.bier.humpen} of UISelectItems with component-path {Component-Path : [Class: javax.faces.component.UIViewRoot,ViewId: /X500Form.xhtml][Class: javax.faces.component.html.HtmlBody, ... ][Class: javax.faces.component.UISelectItems,Id: selectItemsId} does not reference an Object of type SelectItem, array, Iterable or Map, but of type: null
--
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