April 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12871) Add support for the <procedure> docbook tag to asciidoc, or find an alternate tag

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12871?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-12871. -------------------------------- Resolution: Won't Fix It was fairly easy to work around this with numbered and nested lists. > Add support for the <procedure> docbook tag to asciidoc, or find an alternate tag > --------------------------------------------------------------------------------- > > Key: RF-12871 > URL: https://issues.jboss.org/browse/RF-12871 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha1 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12872) Integrate the jboss doc style into the asciidoc generated docs

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12872?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-12872. -------------------------------- Resolution: Rejected This is not required when using the pressgang docbook toolchain to render the html. For the direct asciidoc -> html render using asciidoctor, we should look at using one of the asciidoctor base styles. > Integrate the jboss doc style into the asciidoc generated docs > -------------------------------------------------------------- > > Key: RF-12872 > URL: https://issues.jboss.org/browse/RF-12872 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12904) Review the documentation generated from the asciidoc correcting errors

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12904?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12904: ------------------------------- Original Estimate: 2 days (was: 1 day) Remaining Estimate: 2 days (was: 1 day) > Review the documentation generated from the asciidoc correcting errors > ---------------------------------------------------------------------- > > Key: RF-12904 > URL: https://issues.jboss.org/browse/RF-12904 > 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: 2 days > Remaining Estimate: 2 days > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12904) Review the documentation generated from the asciidoc correcting errors

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12904?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-12904. -------------------------------- Resolution: Done > Review the documentation generated from the asciidoc correcting errors > ---------------------------------------------------------------------- > > Key: RF-12904 > URL: https://issues.jboss.org/browse/RF-12904 > 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: 2 days > Remaining Estimate: 2 days > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12682) extendedDataTable render issue with rich:tabPanel

by Kaveh A. (JIRA)

[ https://issues.jboss.org/browse/RF-12682?page=com.atlassian.jira.plugin.s... ] Kaveh A. commented on RF-12682: ------------------------------- Brian, After some more investigation the bug mentioned in RF-12193 (with RF 4.3.1 and javax.faces 2.1.20) has fixed all the issues with extended data table that we have encountered (thank you very much). We did not make the change in the appropriate run time file (packed.js) However the problem of non responsive tabPanel when the tabPanel contains an empty extended data table still exists. I believe this problem was introduced in 4.3.0 since the previous version did not have this problem. This problem is not as important to us at the moment. Thank you for all your help > extendedDataTable render issue with rich:tabPanel > ------------------------------------------------- > > Key: RF-12682 > URL: https://issues.jboss.org/browse/RF-12682 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.3.Final, 4.3.0.M3, 4.3.0.CR1, 4.3.0.Final > Reporter: Kaveh A. > Labels: extendedDataTable, render, richfaces, tabpanel, testcase_provided > Fix For: 5-Tracking > > Attachments: richfacesBug2.zip, RichFacesBugEclipseProject.zip > > > This issue is not just specific to tabPanel. Anytime the extendedDataTable is hidden (when the page loads) and then it is made visible later the table can not display the data (table is empty at the load time). > In this particular case if we load a page with two tabs. Furthermore if we have one extendedDataTable in each tab (the first tab shows and the second tab is not shown at first). In this case once the user clicks on the second tab and tries to populate the extendedDataTable (via any action). Then the table is not rendered properly. A sample project has been provided at the following link that further describe this issue. You can download the eclipse project attached at the end of the following message to reproduce this issue. > https://community.jboss.org/message/783787 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12911) The release plugin doesn't change version in Java sources

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12911: ------------------------------- Summary: The release plugin doesn't change version in Java sources Key: RF-12911 URL: https://issues.jboss.org/browse/RF-12911 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: build/distribution Affects Versions: 5.0.0.Alpha1 Reporter: Lukáš Fryč The version in {{VersionBean}} and {{FundamentalTestConfiguration}} stays {{5.0.0-SNAPSHOT}} after tagging (using {{mvn release:prepare}}). -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12910) Include the built WARs in distribution

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12910: ------------------------------- Summary: Include the built WARs in distribution Key: RF-12910 URL: https://issues.jboss.org/browse/RF-12910 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: build/distribution Affects Versions: 5.0.0.Alpha1 Reporter: Lukáš Fryč The distribution currently contains just sources of WAR example projects (photoalbum / showcase). Some users might want just deploy those WARs and do not work with project sources, thus I propose to include built WARs directly. -- 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, 12 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 Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12909: ------------------------------- Summary: 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č Priority: Minor 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, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12908) Distribution ZIP doesn't contain any examples

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12908: ------------------------------- Summary: Distribution ZIP doesn't contain any examples Key: RF-12908 URL: https://issues.jboss.org/browse/RF-12908 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: build/distribution Affects Versions: 5.0.0.Alpha1 Reporter: Lukáš Fryč There is just empty {{examples}} folder in the distribution ZIP. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12907) render="@form" problem with a4jCommand Button

by Jean ANDRE (JIRA)

[ https://issues.jboss.org/browse/RF-12907?page=com.atlassian.jira.plugin.s... ] Jean ANDRE updated RF-12907: ---------------------------- Attachment: Nested-Spring-3.2.2.zip Here is the project ITBH sent also for the bug JSF 2016 - With Spring 3.2.2 as CDI, ready to execute. Just add your suitable RF version. > render="@form" problem with a4jCommand Button > --------------------------------------------- > > Key: RF-12907 > URL: https://issues.jboss.org/browse/RF-12907 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.3.Final, 4.3.1 > Environment: JSF Mojarra 2.1.21 or 2.1.20 - Glassfish or WAS 8.0.0.x Servlet 3.0 or 2.5 > Reporter: Jean ANDRE > Priority: Blocker > Attachments: Nested-Spring-3.2.2.zip > > > Please see the report at: http://java.net/jira/browse/JAVASERVERFACES-2016 > It seems that that there is a problem with a4j button and the value of @form/render attribute. > The symptom we got is after refreshing the panel for building a list. Click on link form the result lisk does not trigger the action. -- 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, 12 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 April 2013