May 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13009) drag and drop inside collapsible subtable causes assertion error

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13009?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13009: ------------------------------- Fix Version/s: 5.0.0.Alpha1 > drag and drop inside collapsible subtable causes assertion error > ---------------------------------------------------------------- > > Key: RF-13009 > URL: https://issues.jboss.org/browse/RF-13009 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-drag/drop, component-tables > Affects Versions: 5.0.0.Alpha1 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > JBoss Application Server: Weld Integration 7.1.1.Final > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.7.0_17-b02 @ Linux > Chrome 26.0.1410.63 @ Linux x86_64 > Reporter: Jan Papousek > Fix For: 5.0.0.Alpha1 > > > The issue is probably caused by this assertion: https://github.com/richfaces/richfaces/blob/master/framework/src/main/jav... > Here is the stack trace: > {code} > Daemon Thread [http-localhost-127.0.0.1-8080-1] (Suspended (breakpoint at line 880 in UIDataAdaptor)) > UICollapsibleSubTable(UIDataAdaptor).getIterationState() line: 880 > UICollapsibleSubTable(AbstractCollapsibleSubTable).getIterationState() line: 151 > SavedState.<init>(IterationStateHolder) line: 62 > UIDataTable(UIDataAdaptor).saveChildState(FacesContext, UIComponent) line: 309 > UIDataTable(UIDataAdaptor).saveChildState(FacesContext) line: 290 > UIDataTable(UIDataAdaptor).setRowKey(FacesContext, Object) line: 266 > UIDataTable(UIDataAdaptor).invokeOnComponent(FacesContext, String, ContextCallback) line: 1074 > HtmlForm(UIComponent).invokeOnComponent(FacesContext, String, ContextCallback) line: 1426 > HtmlForm(UIComponentBase).invokeOnComponent(FacesContext, String, ContextCallback) line: 669 > HtmlPanelGroup(UIComponent).invokeOnComponent(FacesContext, String, ContextCallback) line: 1426 > HtmlPanelGroup(UIComponentBase).invokeOnComponent(FacesContext, String, ContextCallback) line: 669 > UIOutput(UIComponent).invokeOnComponent(FacesContext, String, ContextCallback) line: 1426 > UIOutput(UIComponentBase).invokeOnComponent(FacesContext, String, ContextCallback) line: 669 > UIViewRoot(UIComponent).invokeOnComponent(FacesContext, String, ContextCallback) line: 1426 > UIViewRoot(UIComponentBase).invokeOnComponent(FacesContext, String, ContextCallback) line: 669 > DropTargetRenderer.doDecode(FacesContext, UIComponent) line: 86 > DropTargetRenderer(RendererBase).decode(FacesContext, UIComponent) line: 81 > UIDropTarget(UIComponentBase).decode(FacesContext) line: 787 > UIDropTarget(UIComponentBase).processDecodes(FacesContext) line: 1181 > PartialViewExecuteVisitCallback.visit(VisitContext, UIComponent) line: 53 > ExecuteExtendedVisitContext(BaseExtendedVisitContext).invokeVisitCallback(UIComponent, VisitCallback) line: 322 > UIDropTarget(UIComponent).visitTree(VisitContext, VisitCallback) line: 1612 > UIOutputPanel(UIComponent).visitTree(VisitContext, VisitCallback) line: 1623 > HtmlPanelGroup(UIComponent).visitTree(VisitContext, VisitCallback) line: 1623 > UIDataAdaptor$DataVisitorForVisitTree.process(FacesContext, Object, Object) line: 197 > SequenceDataModel<E>.walk(FacesContext, DataVisitor, Range, Object) line: 66 > UICollapsibleSubTable(UIDataAdaptor).walk(FacesContext, DataVisitor, Object) line: 807 > UICollapsibleSubTable(UIDataAdaptor).visitDataChildren(VisitContext, VisitCallback, boolean) line: 1280 > UICollapsibleSubTable(UIDataTableBase).visitDataChildren(VisitContext, VisitCallback, boolean) line: 416 > UICollapsibleSubTable(UIDataAdaptor).visitTree(VisitContext, VisitCallback) line: 1358 > UIDataAdaptor$DataVisitorForVisitTree.process(FacesContext, Object, Object) line: 197 > SequenceDataModel<E>.walk(FacesContext, DataVisitor, Range, Object) line: 66 > UIDataTable(UIDataAdaptor).walk(FacesContext, DataVisitor, Object) line: 807 > UIDataTable(UIDataAdaptor).visitDataChildren(VisitContext, VisitCallback, boolean) line: 1280 > UIDataTable(UIDataTableBase).visitDataChildren(VisitContext, VisitCallback, boolean) line: 416 > UIDataTable(UIDataAdaptor).visitTree(VisitContext, VisitCallback) line: 1358 > HtmlForm(UIComponent).visitTree(VisitContext, VisitCallback) line: 1623 > HtmlForm(UIForm).visitTree(VisitContext, VisitCallback) line: 371 > HtmlPanelGroup(UIComponent).visitTree(VisitContext, VisitCallback) line: 1623 > UIOutput(UIComponent).visitTree(VisitContext, VisitCallback) line: 1623 > UIViewRoot(UIComponent).visitTree(VisitContext, VisitCallback) line: 1623 > ExtendedPartialViewContextImpl.executeComponents(PhaseId, Collection<String>) line: 287 > ExtendedPartialViewContextImpl.processPartialExecutePhase(PhaseId) line: 267 > ExtendedPartialViewContextImpl.processPartial(PhaseId) line: 224 > UIViewRoot.processDecodes(FacesContext) line: 931 > ApplyRequestValuesPhase.execute(FacesContext) line: 78 > ApplyRequestValuesPhase(Phase).doPhase(FacesContext, Lifecycle, ListIterator<PhaseListener>) line: 101 > LifecycleImpl.execute(FacesContext) line: 118 > FacesServlet.service(ServletRequest, ServletResponse) line: 593 > ApplicationFilterChain.internalDoFilter(ServletRequest, ServletResponse) line: 329 > ApplicationFilterChain.doFilter(ServletRequest, ServletResponse) line: 248 > TestIdentityFilter.doFilter(ServletRequest, ServletResponse, FilterChain) line: 93 > ApplicationFilterChain.internalDoFilter(ServletRequest, ServletResponse) line: 280 > ApplicationFilterChain.doFilter(ServletRequest, ServletResponse) line: 248 > ConversationPropagationFilter.doFilter(ServletRequest, ServletResponse, FilterChain) line: 62 > ApplicationFilterChain.internalDoFilter(ServletRequest, ServletResponse) line: 280 > ApplicationFilterChain.doFilter(ServletRequest, ServletResponse) line: 248 > StandardWrapperValve.invoke(Request, Response) line: 275 > StandardContextValve.invoke(Request, Response) line: 161 > SecurityContextAssociationValve.invoke(Request, Response) line: 153 > StandardHostValve.invoke(Request, Response) line: 155 > ErrorReportValve.invoke(Request, Response) line: 102 > StandardEngineValve.invoke(Request, Response) line: 109 > CoyoteAdapter.service(Request, Response) line: 368 > Http11Processor.process(Socket) line: 877 > Http11Protocol$Http11ConnectionHandler.process(Socket) line: 671 > JIoEndpoint$Worker.run() line: 930 > Thread.run() line: 722 > {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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-13014) Photoalbum: resource-optimizer plugin warns about NullPointerException

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13014?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13014: ---------------------------- Sprint: 5.0.0.Alpha1 Sprint > Photoalbum: resource-optimizer plugin warns about NullPointerException > ---------------------------------------------------------------------- > > Key: RF-13014 > URL: https://issues.jboss.org/browse/RF-13014 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 5.0.0.Alpha1 > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12846) a4j:commandLink accesskey attribute missing

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12846?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč reassigned RF-12846: ------------------------------- Assignee: Lukáš Fryč (was: Brian Leathem) > a4j:commandLink accesskey attribute missing > ------------------------------------------- > > Key: RF-12846 > URL: https://issues.jboss.org/browse/RF-12846 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.2.Final, 4.2.3.Final, 4.3.1 > Reporter: John Yeary > Assignee: Lukáš Fryč > Priority: Trivial > Fix For: 4.3.2, 5.0.0.Alpha1 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > The a4j:commandLink supported accesskey in 3.3.3.final and the org.richfaces.renderkit.html.CommandLinkRenderer supports the accesskey attribute as a pass-through attribute. However it does not appear in the VDL documentation, and produces an error message in the IDE. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-13012) Push-depchain: parent.relativePath points at richfaces-build instead of richfaces-parent

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13012?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč reassigned RF-13012: ------------------------------- Assignee: Lukáš Fryč > Push-depchain: parent.relativePath points at richfaces-build instead of richfaces-parent > ---------------------------------------------------------------------------------------- > > Key: RF-13012 > URL: https://issues.jboss.org/browse/RF-13012 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha1 > Reporter: Pavol Pitonak > Assignee: Lukáš Fryč > Fix For: 5.0.0.Alpha1 > > > There is a warning when one wants to build RichFaces 5. It seems not to influence build. > {quote} > [WARNING] > [WARNING] Some problems were encountered while building the effective model for org.richfaces:richfaces-push-depchain:pom:5.0.0-SNAPSHOT > [WARNING] 'parent.relativePath' points at org.richfaces:richfaces-build instead of org.richfaces:richfaces-parent, please verify your project structure @ line 26, column 13 > [WARNING] > [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. > [WARNING] > [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. > [WARNING] > {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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-13012) Push-depchain: parent.relativePath points at richfaces-build instead of richfaces-parent

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13012?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13012: ---------------------------- Fix Version/s: 5.0.0.Alpha1 > Push-depchain: parent.relativePath points at richfaces-build instead of richfaces-parent > ---------------------------------------------------------------------------------------- > > Key: RF-13012 > URL: https://issues.jboss.org/browse/RF-13012 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha1 > Reporter: Pavol Pitonak > Fix For: 5.0.0.Alpha1 > > > There is a warning when one wants to build RichFaces 5. It seems not to influence build. > {quote} > [WARNING] > [WARNING] Some problems were encountered while building the effective model for org.richfaces:richfaces-push-depchain:pom:5.0.0-SNAPSHOT > [WARNING] 'parent.relativePath' points at org.richfaces:richfaces-build instead of org.richfaces:richfaces-parent, please verify your project structure @ line 26, column 13 > [WARNING] > [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. > [WARNING] > [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. > [WARNING] > {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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-13014) Photoalbum: resource-optimizer plugin warns about NullPointerException

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-13014: ------------------------------- Summary: Photoalbum: resource-optimizer plugin warns about NullPointerException Key: RF-13014 URL: https://issues.jboss.org/browse/RF-13014 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: examples Affects Versions: 5.0.0.Alpha1 Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 5.0.0.Alpha1 -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-13012) Push-depchain: parent.relativePath points at richfaces-build instead of richfaces-parent

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13012?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13012: ---------------------------- Sprint: 5.0.0.Alpha1 Sprint > Push-depchain: parent.relativePath points at richfaces-build instead of richfaces-parent > ---------------------------------------------------------------------------------------- > > Key: RF-13012 > URL: https://issues.jboss.org/browse/RF-13012 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha1 > Reporter: Pavol Pitonak > Fix For: 5.0.0.Alpha1 > > > There is a warning when one wants to build RichFaces 5. It seems not to influence build. > {quote} > [WARNING] > [WARNING] Some problems were encountered while building the effective model for org.richfaces:richfaces-push-depchain:pom:5.0.0-SNAPSHOT > [WARNING] 'parent.relativePath' points at org.richfaces:richfaces-build instead of org.richfaces:richfaces-parent, please verify your project structure @ line 26, column 13 > [WARNING] > [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. > [WARNING] > [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. > [WARNING] > {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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-13013) port @escape attribute for notify and notifyMessages from 4.3.0

by Jan Papousek (JIRA)

Jan Papousek created RF-13013: --------------------------------- Summary: port @escape attribute for notify and notifyMessages from 4.3.0 Key: RF-13013 URL: https://issues.jboss.org/browse/RF-13013 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 5.0.0.Alpha1 Reporter: Jan Papousek RF-12736 has introduced an attribute @escape for notify and notifyMessages components, but this attribute is not available in RichFaces 5. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12846) a4j:commandLink accesskey attribute missing

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12846?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12846: ------------------------------- Sprint: 4.3.2 Sprint 1, 5.0.0.Alpha1 Sprint (was: 4.3.2 Sprint 1) > a4j:commandLink accesskey attribute missing > ------------------------------------------- > > Key: RF-12846 > URL: https://issues.jboss.org/browse/RF-12846 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.2.Final, 4.2.3.Final, 4.3.1 > Reporter: John Yeary > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.3.2, 5.0.0.Alpha1 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > The a4j:commandLink supported accesskey in 3.3.3.final and the org.richfaces.renderkit.html.CommandLinkRenderer supports the accesskey attribute as a pass-through attribute. However it does not appear in the VDL documentation, and produces an error message in the IDE. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12846) a4j:commandLink accesskey attribute missing

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12846?page=com.atlassian.jira.plugin.s... ] Brian Leathem reopened RF-12846: -------------------------------- Re-opening, as this patch was missed in RichFaces 5 > a4j:commandLink accesskey attribute missing > ------------------------------------------- > > Key: RF-12846 > URL: https://issues.jboss.org/browse/RF-12846 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.2.Final, 4.2.3.Final, 4.3.1 > Reporter: John Yeary > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.3.2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > The a4j:commandLink supported accesskey in 3.3.3.final and the org.richfaces.renderkit.html.CommandLinkRenderer supports the accesskey attribute as a pass-through attribute. However it does not appear in the VDL documentation, and produces an error message in the IDE. -- 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, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues May 2013