[JBoss JIRA] (RF-12683) Provide a configuration option to disable built-in sorting/filtering
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12683?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-12683:
----------------------------------
Assignee: Brian Leathem
> Provide a configuration option to disable built-in sorting/filtering
> --------------------------------------------------------------------
>
> Key: RF-12683
> URL: https://issues.jboss.org/browse/RF-12683
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.0.M3
> Reporter: Brian Leathem
> Assignee: Brian Leathem
> Fix For: 4.3.0.CR1
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> The built-in sorting/filtering feature introduced in 4.3.0.M3 requires developer who are already using the EDT sorting/filtering functionality to introduce the _sortType=custom_ and _filterType=custom_ attributes to prevent a "doulbing up" of the sort and filter controls.
> To make it easier for people to migrate from RichFaces 4.2 to 4.3, we should provide a central configuration option (ie. a web.xml context-param) to disable built-in sorting/filtering, so developers can introduce the new attributes to their facelets at their leisure.
--
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
12 years, 2 months
[JBoss JIRA] (RF-12662) Showcase - rich:extendedDataTable - Built-in sorting and filtering - ELException when text filter value provided instead of expected numbers
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12662?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-12662:
----------------------------------
Assignee: Brian Leathem
> Showcase - rich:extendedDataTable - Built-in sorting and filtering - ELException when text filter value provided instead of expected numbers
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: RF-12662
> URL: https://issues.jboss.org/browse/RF-12662
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables, showcase
> Affects Versions: 4.3.0.M3
> Environment: showcase M3 release
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Priority: Minor
> Fix For: 4.3.0.CR1
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> When providing characters as filter value for column Price instead of numbers , an ELException is thrown on the the server console:
> {code}
> 14:59:21,603 SEVERE [org.richfaces.log.Context] (http--0.0.0.0-8080-4) javax.el.ELException: /richfaces/extendedDataTable/samples/edt-builtin-sorting-and-filtering-sample.xhtml @38,75 filterValue="#{carsFilteringBean.mileageFilter}": Cannot convert gg of type class java.lang.String to class java.lang.Long: javax.faces.FacesException: javax.el.ELException: /richfaces/extendedDataTable/samples/edt-builtin-sorting-and-filtering-sample.xhtml @38,75 filterValue="#{carsFilteringBean.mileageFilter}": Cannot convert gg of type class java.lang.String to class java.lang.Long
> at org.richfaces.renderkit.SortingFilteringRowsRenderer.updateAttribute(SortingFilteringRowsRenderer.java:144) [richfaces-components-ui-4.3.0.20121214-M3.jar:4.3.0.20121214-M3]
> at org.richfaces.renderkit.SortingFilteringRowsRenderer.decodeFiltering(SortingFilteringRowsRenderer.java:84) [richfaces-components-ui-4.3.0.20121214-M3.jar:4.3.0.20121214-M3]
> at org.richfaces.renderkit.SortingFilteringRowsRenderer.decodeSortingFiltering(SortingFilteringRowsRenderer.java:62) [richfaces-components-ui-4.3.0.20121214-M3.jar:4.3.0.20121214-M3]
> at org.richfaces.renderkit.ExtendedDataTableRenderer.doDecode(ExtendedDataTableRenderer.java:945) [richfaces-components-ui-4.3.0.20121214-M3.jar:4.3.0.20121214-M3]
> at org.richfaces.renderkit.RendererBase.decode(RendererBase.java:80) [richfaces-components-ui-4.3.0.20121214-M3.jar:4.3.0.20121214-M3]
> at javax.faces.component.UIComponentBase.decode(UIComponentBase.java:787) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at org.richfaces.component.UIDataAdaptor.processDecodes(UIDataAdaptor.java:820) [richfaces-components-ui-4.3.0.20121214-M3.jar:4.3.0.20121214-M3]
> at org.richfaces.context.PartialViewExecuteVisitCallback.visit(PartialViewExecuteVisitCallback.java:53) [richfaces-core-impl-4.3.0.20121214-M3.jar:4.3.0.20121214-M3]
> at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:321) [richfaces-core-impl-4.3.0.20121214-M3.jar:4.3.0.20121214-M3]
> at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1320) [richfaces-components-ui-4.3.0.20121214-M3.jar:4.3.0.20121214-M3]
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at javax.faces.component.UIForm.visitTree(UIForm.java:371) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at org.richfaces.context.ExtendedPartialViewContextImpl.executeComponents(ExtendedPartialViewContextImpl.java:237) [richfaces-core-impl-4.3.0.20121214-M3.jar:4.3.0.20121214-M3]
> at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialExecutePhase(ExtendedPartialViewContextImpl.java:217) [richfaces-core-impl-4.3.0.20121214-M3.jar:4.3.0.20121214-M3]
> at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:196) [richfaces-core-impl-4.3.0.20121214-M3.jar:4.3.0.20121214-M3]
> at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:931) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:78) [jsf-impl-2.1.7-jbossorg-2.jar:]
> at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.7-jbossorg-2.jar:]
> at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.7-jbossorg-2.jar:]
> at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.execute(PersistenceLifecycle.java:58) [classes:]
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:]
> at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05]
> Caused by: javax.el.ELException: /richfaces/extendedDataTable/samples/edt-builtin-sorting-and-filtering-sample.xhtml @38,75 filterValue="#{carsFilteringBean.mileageFilter}": Cannot convert gg of type class java.lang.String to class java.lang.Long
> at com.sun.faces.facelets.el.TagValueExpression.setValue(TagValueExpression.java:139) [jsf-impl-2.1.7-jbossorg-2.jar:]
> at org.richfaces.renderkit.SortingFilteringRowsRenderer.updateAttribute(SortingFilteringRowsRenderer.java:142) [richfaces-components-ui-4.3.0.20121214-M3.jar:4.3.0.20121214-M3]
> ... 42 more
> {code}
> IMHO {{rich:message}} should be placed there to warn user about incorrect input and the exception should be handled.
--
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
12 years, 2 months
[JBoss JIRA] (RF-12670) JSF 2.0 compatibility issue, NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12670?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-12670.
--------------------------------
Resolution: Done
Looked for the javax.faces.visit.SKIP_ITERATION attribute in the FacesContext instead of using the VisitHint.SKIP_ITERATION.
> JSF 2.0 compatibility issue, NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION
> ---------------------------------------------------------------------------------------------------
>
> Key: RF-12670
> URL: https://issues.jboss.org/browse/RF-12670
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.0.M3
> Reporter: Dupont Dupont
> Assignee: Brian Leathem
> Fix For: 4.3.0.CR1
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> When using RF 4.3.0-SNAPSHOT with a JSF 2.0 implementation (i.e. Websphere 8), I get a
> {code}
> java.lang.NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION
> at org.richfaces.component.UIDataAdaptor.requiresRowIteration(UIDataAdaptor.java:1387)
> at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1304)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:793)
> at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007)
> at javax.faces.component.UIForm.visitTree(UIForm.java:269)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:793)
> at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:793)
> at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007)
> at org.apache.myfaces.lifecycle.DefaultRestoreViewSupport.processComponentBinding(DefaultRestoreViewSupport.java:90)
> at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:142)
> at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:171)
> at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
> at
> {code}
> RF 4.3.0-SNAPSHOT is using an API introduced with JSF 2.1 in UIDataAdaptor.
> See https://github.com/richfaces/components/commit/d65e614ef03adf87c0b6df2288...
--
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
12 years, 2 months
[JBoss JIRA] (RF-12671) dropTarget does not work inside dynamic tabs when switchType is ajax or server
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12671?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reopened RF-12671:
--------------------------------
> dropTarget does not work inside dynamic tabs when switchType is ajax or server
> ------------------------------------------------------------------------------
>
> Key: RF-12671
> URL: https://issues.jboss.org/browse/RF-12671
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.0.M3
> Reporter: Ken H
> Assignee: Brian Leathem
> Fix For: 4.3.0.CR1
>
> Original Estimate: 3 hours
> Remaining Estimate: 3 hours
>
> The following works fine:
> {code}
> <rich:tabPanel switchType="client">
> <a4j:repeat value="#{bean.thingsToIterate}" var="thing">
> <rich:tab header="Tab #{thing}">
> <rich:panel style="width: 100px;">
> <rich:dragSource dragValue="drag-#{thing}" type="term" />
> drag #{thing}
> </rich:panel>
> <rich:panel style="width: 100px;">
> <rich:dropTarget dropValue="drop-#{thing}" acceptedTypes="term" dropListener="#{bean.processDrop}" execute="@form" render="@form" />
> drop #{thing}
> </rich:panel>
> </rich:tab>
> </a4j:repeat>
> </rich:tabPanel>
> public void processDrop(DropEvent evt) {
> log.info("processDrop called - dragVal: "+evt.getDragValue()+", dropVal: "+evt.getDropValue());
> }
> {code}
> However, changing the switch type to ajax or server results in processDrop not being called. The POST data appears to be identical.
--
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
12 years, 2 months
[JBoss JIRA] (RF-12671) dropTarget does not work inside dynamic tabs when switchType is ajax or server
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12671?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12671:
-------------------------------
Sprint: 4.3.0.CR1 - Regression Fixes
> dropTarget does not work inside dynamic tabs when switchType is ajax or server
> ------------------------------------------------------------------------------
>
> Key: RF-12671
> URL: https://issues.jboss.org/browse/RF-12671
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.0.M3
> Reporter: Ken H
> Assignee: Brian Leathem
> Fix For: 4.3.0.CR1
>
> Original Estimate: 3 hours
> Remaining Estimate: 3 hours
>
> The following works fine:
> {code}
> <rich:tabPanel switchType="client">
> <a4j:repeat value="#{bean.thingsToIterate}" var="thing">
> <rich:tab header="Tab #{thing}">
> <rich:panel style="width: 100px;">
> <rich:dragSource dragValue="drag-#{thing}" type="term" />
> drag #{thing}
> </rich:panel>
> <rich:panel style="width: 100px;">
> <rich:dropTarget dropValue="drop-#{thing}" acceptedTypes="term" dropListener="#{bean.processDrop}" execute="@form" render="@form" />
> drop #{thing}
> </rich:panel>
> </rich:tab>
> </a4j:repeat>
> </rich:tabPanel>
> public void processDrop(DropEvent evt) {
> log.info("processDrop called - dragVal: "+evt.getDragValue()+", dropVal: "+evt.getDropValue());
> }
> {code}
> However, changing the switch type to ajax or server results in processDrop not being called. The POST data appears to be identical.
--
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
12 years, 2 months
[JBoss JIRA] (RF-12671) dropTarget does not work inside dynamic tabs when switchType is ajax or server
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12671?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-12671.
--------------------------------
Resolution: Done
> dropTarget does not work inside dynamic tabs when switchType is ajax or server
> ------------------------------------------------------------------------------
>
> Key: RF-12671
> URL: https://issues.jboss.org/browse/RF-12671
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.0.M3
> Reporter: Ken H
> Assignee: Brian Leathem
> Fix For: 4.3.0.CR1
>
> Original Estimate: 3 hours
> Remaining Estimate: 3 hours
>
> The following works fine:
> {code}
> <rich:tabPanel switchType="client">
> <a4j:repeat value="#{bean.thingsToIterate}" var="thing">
> <rich:tab header="Tab #{thing}">
> <rich:panel style="width: 100px;">
> <rich:dragSource dragValue="drag-#{thing}" type="term" />
> drag #{thing}
> </rich:panel>
> <rich:panel style="width: 100px;">
> <rich:dropTarget dropValue="drop-#{thing}" acceptedTypes="term" dropListener="#{bean.processDrop}" execute="@form" render="@form" />
> drop #{thing}
> </rich:panel>
> </rich:tab>
> </a4j:repeat>
> </rich:tabPanel>
> public void processDrop(DropEvent evt) {
> log.info("processDrop called - dragVal: "+evt.getDragValue()+", dropVal: "+evt.getDropValue());
> }
> {code}
> However, changing the switch type to ajax or server results in processDrop not being called. The POST data appears to be identical.
--
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
12 years, 2 months
[JBoss JIRA] (RF-12671) dropTarget does not work inside dynamic tabs when switchType is ajax or server
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12671?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-12671.
--------------------------------
Assignee: Brian Leathem
Resolution: Done
Added UIRepeat to the allowed visits for processing of decodes, validations and updates.
> dropTarget does not work inside dynamic tabs when switchType is ajax or server
> ------------------------------------------------------------------------------
>
> Key: RF-12671
> URL: https://issues.jboss.org/browse/RF-12671
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.0.M3
> Reporter: Ken H
> Assignee: Brian Leathem
> Fix For: 4.3.0.CR1
>
> Original Estimate: 3 hours
> Remaining Estimate: 3 hours
>
> The following works fine:
> {code}
> <rich:tabPanel switchType="client">
> <a4j:repeat value="#{bean.thingsToIterate}" var="thing">
> <rich:tab header="Tab #{thing}">
> <rich:panel style="width: 100px;">
> <rich:dragSource dragValue="drag-#{thing}" type="term" />
> drag #{thing}
> </rich:panel>
> <rich:panel style="width: 100px;">
> <rich:dropTarget dropValue="drop-#{thing}" acceptedTypes="term" dropListener="#{bean.processDrop}" execute="@form" render="@form" />
> drop #{thing}
> </rich:panel>
> </rich:tab>
> </a4j:repeat>
> </rich:tabPanel>
> public void processDrop(DropEvent evt) {
> log.info("processDrop called - dragVal: "+evt.getDragValue()+", dropVal: "+evt.getDropValue());
> }
> {code}
> However, changing the switch type to ajax or server results in processDrop not being called. The POST data appears to be identical.
--
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
12 years, 2 months
[JBoss JIRA] (RF-12670) JSF 2.0 compatibility issue, NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12670?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12670:
-------------------------------
Sprint: 4.3.0.CR1 - Regression Fixes
> JSF 2.0 compatibility issue, NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION
> ---------------------------------------------------------------------------------------------------
>
> Key: RF-12670
> URL: https://issues.jboss.org/browse/RF-12670
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.0.M3
> Reporter: Dupont Dupont
> Assignee: Brian Leathem
> Fix For: 4.3.0.CR1
>
>
> When using RF 4.3.0-SNAPSHOT with a JSF 2.0 implementation (i.e. Websphere 8), I get a
> {code}
> java.lang.NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION
> at org.richfaces.component.UIDataAdaptor.requiresRowIteration(UIDataAdaptor.java:1387)
> at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1304)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:793)
> at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007)
> at javax.faces.component.UIForm.visitTree(UIForm.java:269)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:793)
> at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:793)
> at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007)
> at org.apache.myfaces.lifecycle.DefaultRestoreViewSupport.processComponentBinding(DefaultRestoreViewSupport.java:90)
> at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:142)
> at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:171)
> at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
> at
> {code}
> RF 4.3.0-SNAPSHOT is using an API introduced with JSF 2.1 in UIDataAdaptor.
> See https://github.com/richfaces/components/commit/d65e614ef03adf87c0b6df2288...
--
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
12 years, 2 months
[JBoss JIRA] (RF-12670) JSF 2.0 compatibility issue, NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12670?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12670:
-------------------------------
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
> JSF 2.0 compatibility issue, NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION
> ---------------------------------------------------------------------------------------------------
>
> Key: RF-12670
> URL: https://issues.jboss.org/browse/RF-12670
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.0.M3
> Reporter: Dupont Dupont
> Assignee: Brian Leathem
> Fix For: 4.3.0.CR1
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> When using RF 4.3.0-SNAPSHOT with a JSF 2.0 implementation (i.e. Websphere 8), I get a
> {code}
> java.lang.NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION
> at org.richfaces.component.UIDataAdaptor.requiresRowIteration(UIDataAdaptor.java:1387)
> at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1304)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:793)
> at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007)
> at javax.faces.component.UIForm.visitTree(UIForm.java:269)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:793)
> at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:793)
> at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007)
> at org.apache.myfaces.lifecycle.DefaultRestoreViewSupport.processComponentBinding(DefaultRestoreViewSupport.java:90)
> at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:142)
> at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:171)
> at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
> at
> {code}
> RF 4.3.0-SNAPSHOT is using an API introduced with JSF 2.1 in UIDataAdaptor.
> See https://github.com/richfaces/components/commit/d65e614ef03adf87c0b6df2288...
--
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
12 years, 2 months
[JBoss JIRA] (RF-12671) dropTarget does not work inside dynamic tabs when switchType is ajax or server
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12671?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12671:
-------------------------------
Original Estimate: 3 minutes
Remaining Estimate: 3 minutes
> dropTarget does not work inside dynamic tabs when switchType is ajax or server
> ------------------------------------------------------------------------------
>
> Key: RF-12671
> URL: https://issues.jboss.org/browse/RF-12671
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.0.M3
> Reporter: Ken H
> Fix For: 4.3.0.CR1
>
> Original Estimate: 3 minutes
> Remaining Estimate: 3 minutes
>
> The following works fine:
> {code}
> <rich:tabPanel switchType="client">
> <a4j:repeat value="#{bean.thingsToIterate}" var="thing">
> <rich:tab header="Tab #{thing}">
> <rich:panel style="width: 100px;">
> <rich:dragSource dragValue="drag-#{thing}" type="term" />
> drag #{thing}
> </rich:panel>
> <rich:panel style="width: 100px;">
> <rich:dropTarget dropValue="drop-#{thing}" acceptedTypes="term" dropListener="#{bean.processDrop}" execute="@form" render="@form" />
> drop #{thing}
> </rich:panel>
> </rich:tab>
> </a4j:repeat>
> </rich:tabPanel>
> public void processDrop(DropEvent evt) {
> log.info("processDrop called - dragVal: "+evt.getDragValue()+", dropVal: "+evt.getDropValue());
> }
> {code}
> However, changing the switch type to ajax or server results in processDrop not being called. The POST data appears to be identical.
--
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
12 years, 2 months