January 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-11585) mediaOutput doesn't work in CDI @ConversationScoped

by Edilmar Alves (Created) (JIRA)

mediaOutput doesn't work in CDI @ConversationScoped --------------------------------------------------- Key: RF-11585 URL: https://issues.jboss.org/browse/RF-11585 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component Affects Versions: 4.0.0.Final Environment: NetBeans7.0.1 + GlassFish 3.1.1 + CDI 1.1 + JSF2.1 + RichFaces4.0.0-Final. Reporter: Edilmar Alves Priority: Critical When using a controller with @ConversationScoped (CDI scope), the following exception arises: GRAVE: org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.ConversationScoped -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

5
7
0 / 0

[JBoss JIRA] Created: (RF-4308) rich:pickList: keep sort order of source list after add/remove operations

by Martin Höller (JIRA)

rich:pickList: keep sort order of source list after add/remove operations ------------------------------------------------------------------------- Key: RF-4308 URL: https://jira.jboss.org/jira/browse/RF-4308 Project: RichFaces Issue Type: Feature Request Reporter: Martin Höller When adding items from the source list to the target list and removing this items again, the original order of the source list is not preserved. This makes it hard to find items in a list that is longer than just a fest items. A good example is the second example on the livedemo at http://livedemo.exadel.com/richfaces-demo/richfaces/pickList.jsf. Add the first state (Alabama) and remove it. It can now be found at the very end of the otherwise alphabetical list of states. This can be rather unintuitive for a user. My suggestion is either remember the original sort order of the source list, or add some attribute that enables automatic sorting. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

4
3
0 / 0

[JBoss JIRA] Created: (RF-11175) [rich:extendedDataTable] columns should be automatically resized to fill empty space on right side

by Rene O (JIRA)

[rich:extendedDataTable] columns should be automatically resized to fill empty space on right side -------------------------------------------------------------------------------------------------- Key: RF-11175 URL: https://issues.jboss.org/browse/RF-11175 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0.0.Final Reporter: Rene O Attachments: table.PNG As an example: If you have an extendedDataTable with a width of 500px and 3 columns with the default width set. The columns do not fill the entire table width. There is empty space left on the right side of the tabel. It would be good, if the columns would automatically resize to fit the entire table. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

4
4
0 / 0

[JBoss JIRA] Created: (RF-11417) Tab: investigate why @action does not work

by Lukáš Fryč (JIRA)

Tab: investigate why @action does not work ------------------------------------------ Key: RF-11417 URL: https://issues.jboss.org/browse/RF-11417 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-panels-layout-themes Affects Versions: 4.1.0.Final Reporter: Lukáš Fryč Fix For: 4.1.0.Tracking Determine why rich:tab @action has not been implemented. Verify that its implementation can't affect current applications (and try to find possible workaround). Implement @action and @actionListener. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

4
5
0 / 0

[JBoss JIRA] (RF-11924) showcase - rich:context - tree ContextMenu - header of popup should be bigger

by Juraj Huska (JIRA)

Juraj Huska created RF-11924: -------------------------------- Summary: showcase - rich:context - tree ContextMenu - header of popup should be bigger Key: RF-11924 URL: https://issues.jboss.org/browse/RF-11924 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu, component-output, component-panels-layout-themes, showcase, skinning Affects Versions: 4.1.0.Final Environment: showcase app - 4.2.0-SNAPSHOT all browsers Reporter: Juraj Huska Priority: Trivial Attachments: contextMenuPopup.png The header of popup invoked from contextMenu in demos for rich:contextMenu, sample tree contextMenu is in some cases too small, and the cross for hiding the popup overlap with the header label. It is when the body of the popup is small in width. For example it is so when user select node USA, then the header of popup adapts the size of body, and the problem is there. Please see the screenshot for further reference. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

4
11
0 / 0

[JBoss JIRA] (RF-11668) CDK should support arbitrary objects with the <cdk:object> tag

by Brian Leathem (Created) (JIRA)

CDK should support arbitrary objects with the <cdk:object> tag -------------------------------------------------------------- Key: RF-11668 URL: https://issues.jboss.org/browse/RF-11668 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: cdk Reporter: Brian Leathem Fix For: 4.2.0.Tracking The _<cdk:object>_ tag should accept arbitrary classes in the _type_ parameter, and perform the cast in the generated code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

4
14
0 / 0

[JBoss JIRA] (RF-11853) Remove checkstyle-supressions.xml files

by Lukáš Fryč (Created) (JIRA)

Remove checkstyle-supressions.xml files --------------------------------------- Key: RF-11853 URL: https://issues.jboss.org/browse/RF-11853 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: build/distribution Affects Versions: 4.1.0.Final Reporter: Lukáš Fryč These general rules suppressions should not be needed anymore since we are using JBoss Community Checkstyle settings. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

4
6
0 / 0

[JBoss JIRA] (RF-11836) Replace ${project.version} definitions in the poms with actual version

by Lukáš Fryč (Created) (JIRA)

Replace ${project.version} definitions in the poms with actual version ---------------------------------------------------------------------- Key: RF-11836 URL: https://issues.jboss.org/browse/RF-11836 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: build/distribution Affects Versions: 4.1.0.Final Reporter: Lukáš Fryč This is requirement for uploading to Maven Central. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

8
22
0 / 0

[JBoss JIRA] (RF-11548) showcase - define our own error messages for rich:message, rich:messages and other components to have consistent error messages

by Juraj Huska (Created) (JIRA)

showcase - define our own error messages for rich:message, rich:messages and other components to have consistent error messages ------------------------------------------------------------------------------------------------------------------------------- Key: RF-11548 URL: https://issues.jboss.org/browse/RF-11548 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.1.0.Milestone3 Environment: showcase Reporter: Juraj Huska Priority: Minor The standard error messages provided by mojarra are changed from one version to another. For example there is quiet small change, but causes that for example in JBoss AS 6.0.0.Final I have this error message: Name: Validation Error: *Value* is less than allowable minimum of '3' and on JBoss AS 7.0.2.Final I have: Name: Validation Error: *Length* is less than allowable minimum of '3' this causes some problems when testing and also IMHO it would look better with unified error messages for all components. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

9
13
0 / 0

[JBoss JIRA] (RF-11559) showcase - rich:calendar - sample Simple Calendar - apply checkbox should be disabled when popup is unchecked

by Juraj Huska (Created) (JIRA)

showcase - rich:calendar - sample Simple Calendar - apply checkbox should be disabled when popup is unchecked ------------------------------------------------------------------------------------------------------------- Key: RF-11559 URL: https://issues.jboss.org/browse/RF-11559 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component-input, showcase Affects Versions: 4.1.0.Milestone3 Environment: showcase Reporter: Juraj Huska Priority: Trivial IMHO it will give to viewer of showcase better impression of us when: the apply checkbox will be disabled when the popup checkbox is unchecked, since when the calendar is not in popup mode then it is not possible to have there apply button and therefore I should be disabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

6
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues January 2012