May 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12989) Documentation for togglePanelItem is wrong and 4.2.2 components are not working anymore in 4.3.0.Final

by Andrea Martino (JIRA)

[ https://issues.jboss.org/browse/RF-12989?page=com.atlassian.jira.plugin.s... ] Andrea Martino updated RF-12989: -------------------------------- Issue Type: Bug (was: Feature Request) > Documentation for togglePanelItem is wrong and 4.2.2 components are not working anymore in 4.3.0.Final > ------------------------------------------------------------------------------------------------------ > > Key: RF-12989 > URL: https://issues.jboss.org/browse/RF-12989 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.3.0.Final > Environment: JBossAS 7.1.1 > Reporter: Andrea Martino > Priority: Minor > Labels: togglePanel > > In RichFaces 4.2.2 it was possible to define togglePane items using id as attribute, as following {code}<rich:togglePanelItem id="item1">{code} > With RichFaces 4.3.0 the page does not work anymore, I had to change the attribute to name {code}<rich:togglePanelItem name="item1">{code} > The docs still say id is valid, even when it's not [http://docs.jboss.org/richfaces/latest_4_3_X/Component_Reference/en-US/ht...]. Either the docs should be changed or id attribute should be accepted as it was before. -- 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-12989) Documentation for togglePanelItem is wrong and 4.2.2 components are not working anymore in 4.3.0.Final

by Andrea Martino (JIRA)

Andrea Martino created RF-12989: ----------------------------------- Summary: Documentation for togglePanelItem is wrong and 4.2.2 components are not working anymore in 4.3.0.Final Key: RF-12989 URL: https://issues.jboss.org/browse/RF-12989 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: doc Affects Versions: 4.3.0.Final Environment: JBossAS 7.1.1 Reporter: Andrea Martino Priority: Minor In RichFaces 4.2.2 it was possible to define togglePane items using id as attribute, as following {code}<rich:togglePanelItem id="item1">{code} With RichFaces 4.3.0 the page does not work anymore, I had to change the attribute to name {code}<rich:togglePanelItem name="item1">{code} The docs still say id is valid, even when it's not [http://docs.jboss.org/richfaces/latest_4_3_X/Component_Reference/en-US/ht...]. Either the docs should be changed or id attribute should be accepted as it was before. -- 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-12988) RichFaces 5 doc update

by Brian Leathem (JIRA)

Brian Leathem created RF-12988: ---------------------------------- Summary: RichFaces 5 doc update Key: RF-12988 URL: https://issues.jboss.org/browse/RF-12988 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: doc Reporter: Brian Leathem Fix For: 5.0.0.Alpha1 Make final changes to the Developer Guide and Component Reference reflecting the API changed introduced with the RichFaces 5 build re-structure -- 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-12929) PickList change event not firing correctly when ordering objects in target area

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12929?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12929: ------------------------------------ Thanks [~mimmazzo] for submitting a pull request resolving this issue! Note: [~mimmazzo] has signed the CLA. > PickList change event not firing correctly when ordering objects in target area > ------------------------------------------------------------------------------- > > Key: RF-12929 > URL: https://issues.jboss.org/browse/RF-12929 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.3.0.Final > Environment: JBoss AS 7 > Reporter: Simon Plangger > Labels: event, onchange, pickList > Fix For: 5-Tracking > > > The *change* event is not firing, when moving an element from the target area (selected side) to the top or to the bottom of the list. There is no problem with moving items and the change event as long as you don't make it the first or last entry. > To reproduce: > {code} > <rich:pickList > onchange="alert('changed')" > orderable="true" > > > <f:selectItem itemLabel="test 1" itemValue="test 1" /> > <f:selectItem itemLabel="test 2" itemValue="test 2" /> > <f:selectItem itemLabel="test 3" itemValue="test 3" /> > <f:selectItem itemLabel="test 4" itemValue="test 4" /> > <f:selectItem itemLabel="test 5" itemValue="test 5" /> > </rich:pickList> > {code} > Just *select all* items and move them around. -- 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-12867) Convert the docs from docbook xml to asciidoc

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12867?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12867: ------------------------------- Epic Status: Done (was: To Do) > Convert the docs from docbook xml to asciidoc > --------------------------------------------- > > Key: RF-12867 > URL: https://issues.jboss.org/browse/RF-12867 > Project: RichFaces > Issue Type: Epic > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > 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-12909) Aggregate all *.faces-config.xml in richfaces.jar:/META-INF to one faces-config.xml

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12909?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12909: ------------------------------- Fix Version/s: 5.0.0.Alpha2 (was: 5.0.0.Alpha1) > Aggregate all *.faces-config.xml in richfaces.jar:/META-INF to one faces-config.xml > ----------------------------------------------------------------------------------- > > Key: RF-12909 > URL: https://issues.jboss.org/browse/RF-12909 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Fix For: 5.0.0.Alpha2 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > These config files are not in src/main/config and thus they are not processed by CDK - they are included in the META-INF and thus they are processed by JSF in runtime. > It makes the META-INF unpolished. -- 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-12894) The richfaces-framework is not reloadable by JRebel

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12894?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12894: ------------------------------- Fix Version/s: 5.0.0.Alpha2 (was: 5.0.0.Alpha1) > The richfaces-framework is not reloadable by JRebel > --------------------------------------------------- > > Key: RF-12894 > URL: https://issues.jboss.org/browse/RF-12894 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Fix For: 5.0.0.Alpha2 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > It seems when you compile the framework with CDK, the faces-config.xml is re-generated and re-loaded by JRebel. > However the other configuration files stored in {{META-INF/}} (e.g. [core.faces-config.xml|https://github.com/richfaces/richfaces5/blob/master...]) directly (without CDK processing) are not taken into consideration in reloaded configuration, thus this configuration is ignored. As the result, no Core configuration is loaded and no RichFaces Core feature does work. > ---- > The JRebel reload and quick turnaround is one of the features we wanted to enable by build re-structure thus I consider this high priority to cooperate with JRebel team and make it work. -- 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-12918) Switch to using the asciidoctor plugin for asciidoc processing

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12918?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-12918. -------------------------------- Fix Version/s: 5.0.0.Alpha1 (was: 5-Tracking) Resolution: Done > Switch to using the asciidoctor plugin for asciidoc processing > -------------------------------------------------------------- > > Key: RF-12918 > URL: https://issues.jboss.org/browse/RF-12918 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 5.0.0.Alpha1 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > It is currently not possible to generate the RichFaces docbook xml from the asciidoc source using asciidoctor. Two bugs hold us back from switching to asciidoctor: > # https://github.com/asciidoctor/asciidoctor/issues/116 > # https://github.com/asciidoctor/asciidoctor/issues/222 > When these asciidoctor issues have been resolved, we can switch the richfaces docs project to generate the xml using the asciidoctor maven plugin. > Until then, the asciidoc is processed using the asciidoc command line as described in: > https://github.com/richfaces/docs/blob/master/conversion/src/main/bash/as... -- 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-12867) Convert the docs from docbook xml to asciidoc

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12867?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-12867. -------------------------------- Resolution: Done > Convert the docs from docbook xml to asciidoc > --------------------------------------------- > > Key: RF-12867 > URL: https://issues.jboss.org/browse/RF-12867 > Project: RichFaces > Issue Type: Epic > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > 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-12309) CDK: naming conventions to avoid necessity write all the FQNs of classes in Renderer template and Component stub

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12309?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12309: ------------------------------- Fix Version/s: 5.0.0.Alpha2 (was: 5.0.0.Alpha1) > CDK: naming conventions to avoid necessity write all the FQNs of classes in Renderer template and Component stub > ---------------------------------------------------------------------------------------------------------------- > > Key: RF-12309 > URL: https://issues.jboss.org/browse/RF-12309 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: cdk > Affects Versions: 4.2.0.Final > Reporter: Lukáš Fryč > Fix For: 5.0.0.Alpha2 > > > There are lot of bindings which needs to be manually hard-coded in order to make the component work: > Look at sample of the calendar component: > 1. [Renderer template|https://github.com/richfaces/components/blob/4.2.2.20120513-Fina...] > 2. [Component interface|https://github.com/richfaces/components/blob/4.2.2.20120513-Fin...] > ---- > What could follow naming conventions? > 1. *Renderer template* > * {{<class>}} - use the package where the template resides in: {{calendar.template.xml}} -> {{CalendarRenderer}} > * {{<superclass}} - use the {{<class> + Base}}: {{CalendarRenderer}} -> {{CalendarRendererBase}}, if not exists, use {{org.richfaces.renderkit.RendererBase}} > 2. *component* {{org.richfaces.component.AbstractCalendar}} > * component-type: {{org.richfaces.Calendar}} > * component-family: {{org.richfaces.Calendar}} > * generated class: {{org.richfaces.component.UICalendar}} > * renderer: {{org.richfaces.CalendarRenderer}} > * tag: {{@Tag(name = "calendar", handler = "org.richfaces.view.facelets.CalendarHandler")}} > Some definitions what need to be configured per component library: e.g. prefix for component type/family/renderer, etc. > Only classes which violates conventions would be necessary to configure specifically. -- 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