December 2011 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-11760) Remove parent section from richfaces-bom

by Karel Piwko (Created) (JIRA)

Remove parent section from richfaces-bom ---------------------------------------- Key: RF-11760 URL: https://issues.jboss.org/browse/RF-11760 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: build/distribution Affects Versions: 4.1.0.CR1 Reporter: Karel Piwko Priority: Blocker Having <parent> element in the BOM file is fundamentally wrong. If user imports dependencyManagement of the BOM file, it imports even the dependencies from its parent and upper ancestors. Since the ancestor is jboss-parent, it includes virtually the whole world. -- 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

14 years, 1 month

9
13
0 / 0

[JBoss JIRA] Created: (RF-8210) switchType=ajax on modalPanel

by Gonzalez Adrian (JIRA)

switchType=ajax on modalPanel ----------------------------- Key: RF-8210 URL: https://jira.jboss.org/jira/browse/RF-8210 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Gonzalez Adrian Lately, I'm mostly (80% of times) rendering my rich:modalPanels in ajax mode [1] : - a4j:commandButton calls a backing bean method, and rerenders the a4j:outputPanel surrounding rich;modalPanel. oncomplete js handler call Richfaces.showPanel. - the rich:modalPanel is inside a a4j:outputPanel nd its rendered attribute points to a backing bean property. This is because each modalPanels weights more or less 5 ko (I've seen 4 different application and it was always at least 5 ko). This code is repetitive. Could it be possible to add a switchType (or mode) attribute on rich:calendar, the meaning of which would be : 1. if switchType=client, behaviour unchanged. 2. if switchType=ajax, Richfaces.showModal would make an ajax call, rerender the rich:modalPanel (so rich:modalPanel would always be contained in an invisible <span> or shting like this) and show it. -- 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

14 years, 1 month

4
5
0 / 0

[JBoss JIRA] (RF-11842) Support for macrosubstitutions in the contextMenu

by Brian Leathem (Created) (JIRA)

Support for macrosubstitutions in the contextMenu ------------------------------------------------- Key: RF-11842 URL: https://issues.jboss.org/browse/RF-11842 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-menu Affects Versions: 4.1.1.Final Reporter: Brian Leathem Fix For: 4.2.0.Tracking The RichFaces 3 contextMenu supported _macrosubstitutions_, whereby a single instance of the contextMenu will be created and among multiple components. This RichFaces 4 contextMenu should support this feature. See the [RichFaces 3 showcase|http://livedemo.exadel.com/richfaces-demo/richfaces/contextMenu.jsf] for an example of this behaviour. -- 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

14 years, 1 month

5
4
0 / 0

[JBoss JIRA] Created: (RF-11392) rich:collapsibleSubTable - can't scroll in Mojarra

by Jan Papousek (JIRA)

rich:collapsibleSubTable - can't scroll in Mojarra -------------------------------------------------- Key: RF-11392 URL: https://issues.jboss.org/browse/RF-11392 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.1.0.Milestone2 Environment: RichFaces 4.1.0.20110910-M2 r.0d4276b62c8366e0eaa1b7cd1c350d373e65ed79 Metamer 4.1.0.20110910-M2 r.22701 Mojarra 2.1.2-FCS Apache Tomcat 7.0.16 OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.112 Safari/534.30 RichFaces 4.1.0.20110910-M2 r.0d4276b62c8366e0eaa1b7cd1c350d373e65ed79 Metamer 4.1.0.20110910-M2 r.22701 Mojarra 2.1.2-FCS Apache Tomcat 7.0.16 OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0 Reporter: Jan Papousek Open Metamer page in */faces/components/richCollapsibleSubTable/scroller.xhtml*: *The First Problem* - User can't move to the page 3 using the button *»*. - Number buttons work properly. *The Second Problem* - Move in the *Men* section to the second page - Move in the *Women* section to the second page. - The first page in the section *Men* is displayed (wrong). ---- Using MyFaces everything is OK. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
4
0 / 0

[JBoss JIRA] (RF-11833) Label for calendar results in non-valid markup

by Pavol Pitonak (Created) (JIRA)

Label for calendar results in non-valid markup ---------------------------------------------- Key: RF-11833 URL: https://issues.jboss.org/browse/RF-11833 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.1.0.Final Reporter: Pavol Pitonak The code in first code snippet results in markup below which is not valid. The for attribute of the label element must refer to a form control, e.g. the actual input inside calendar (that with ID dateForm:fromDateInputDate). {code:xml} <h:outputLabel value="From date" for="fromDate" /> <rich:calendar id="fromDate" .../> {code} {code:xml} <label for="dateForm:fromDate">From date</label> <span class="calendar" id="dateForm:fromDate"> <span id="dateForm:fromDatePopup" style="white-space: nowrap;"> <input class="rf-cal-inp " id="dateForm:fromDateInputDate" name="dateForm:fromDateInputDate" readonly="readonly" style="vertical-align: middle; " type="text" value="Nov 19, 2011" /> ... {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

14 years, 1 month

5
19
0 / 0

[JBoss JIRA] Created: (RF-9324) a4j:queue event handlers doesn't work at all

by Lukas Fryc (JIRA)

a4j:queue event handlers doesn't work at all -------------------------------------------- Key: RF-9324 URL: https://jira.jboss.org/browse/RF-9324 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 4.0.0.Milestone2 Environment: Java(TM) SE Runtime Environment 1.6.0_20-b02 Linux 2.6.31-22-generic Mojarra 2.0.2-FCS Firefox 3.6.3 Apache Tomcat 6.0.26 core-demo : M2 https://repository.jboss.org/nexus/content/groups/public/org/richfaces/ex... http://localhost:8080/core-demo/queue.jsf Reporter: Lukas Fryc I modified queue.html sample to look like this: <a4j:queue requestDelay="500" oncomplete="alert('1')" /> <h:form> <h:commandLink value="Common link"> <a4j:ajax /> </h:commandLink> </h:form> It seems queue is working, because it handlers multiple events and triggers only one request, but alert is not shown on completion. The same for other event handlers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

6
14
0 / 0

[JBoss JIRA] (RF-11560) Showcase on OpenShift Express: Push stops to work after first long-polling request

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

Showcase on OpenShift Express: Push stops to work after first long-polling request ---------------------------------------------------------------------------------- Key: RF-11560 URL: https://issues.jboss.org/browse/RF-11560 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.1.0.Milestone3 Reporter: Lukáš Fryč Assignee: Lukáš Fryč Priority: Critical Fix For: 4.1.0.Milestone4 Both demos affected: TopicsContext and Push CDI. -- 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

14 years, 1 month

8
10
0 / 0

[JBoss JIRA] (RF-11781) rich:list and rich:dataScroller: numbering on other than the first page

by Jan Papousek (Created) (JIRA)

rich:list and rich:dataScroller: numbering on other than the first page ----------------------------------------------------------------------- Key: RF-11781 URL: https://issues.jboss.org/browse/RF-11781 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.1.0.CR2 Reporter: Jan Papousek When the rich:list and rich:dataScroller are used together, the first items in lists on pages 2, 3, ... shouldn't be numbered with number 1. For example, when the number of items on one page is limited to 10, the first item on the second page should be numbered with 11 (not 1). To try the behaviour of this components working together deploy Metamer and open http://localhost:8080/metamer/faces/components/richList/scroller.xhtml. -- 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

14 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (RF-10782) Input components: add attribute "width"

by Gleb Galkin (JIRA)

Input components: add attribute "width" --------------------------------------- Key: RF-10782 URL: https://issues.jboss.org/browse/RF-10782 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: component, component-input Affects Versions: 4.0.0.Final Reporter: Gleb Galkin Fix For: 4.Future For input components we can define width using attribute style. For more description see the linked issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (RF-6026) PickList doesn't accept comma in string value of SelectItem

by Andrzej Haczewski (JIRA)

PickList doesn't accept comma in string value of SelectItem ----------------------------------------------------------- Key: RF-6026 URL: https://jira.jboss.org/jira/browse/RF-6026 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.0 Environment: WebLogic 10, JSF 1.2, RichFaces 3.3.0, Hibernate JPA, Facelets 1.1.14 Reporter: Andrzej Haczewski When you use a List<SelectItem> where SelectItems are created like this: new SelectItem("SOME STRING,CONTAINING COMMA", "A nice string to show in list") as a PickList <h:selectItems>, and use List<String> as PickList value, then PickList doesn't validate when you add that item to target list. The reason is that UISelectMany is trying to validate values "SOME STRINGS" and "CONTAINING COMMA" with available items. The exact point is the UISelectMany.matchValue() method, which returns false on validation of that PickList. Sample code: --- BackingBean.java class BackingBean { private List<SelectItem> picklistItems; private List<String> result; public BackingBean() { picklistItems = new ArrayList<SelectItem>(); picklistItems.add(new SelectItem("SAMPLE,EXAMPLE", "Sample example")); } // then comes getters and setters for picklistItems and result } --- PickList.xhtml <rich:pickList value="#{backingBean.result}"> <h:selectItems value="#{backingBean.picklistItems}"> </rich:pickList> -- 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

14 years, 1 month

4
8
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues December 2011