December 2009 - richfaces-issues - Jboss List Archives

[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

12 years, 8 months

4
5
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

12 years, 9 months

4
8
0 / 0

[JBoss JIRA] Created: (RF-7351) Regression: "messages: globalOnly does not work properly"

by Joseph Miller (JIRA)

Regression: "messages: globalOnly does not work properly" --------------------------------------------------------- Key: RF-7351 URL: https://jira.jboss.org/jira/browse/RF-7351 Project: RichFaces Issue Type: Bug Components: component, regression Affects Versions: 3.3.1 Environment: Windows / JBoss 4.2.2.GA / Seam 2.1.1.GA / RichFaces 3.3.1.GA Reporter: Joseph Miller Looks like a regression of RF-615... I've upgraded my Seam project to sue RF 3.3.1, in order to fix a number of other bugs, but now messages intended for a single UI component (via the for= ) are appearing in the global messages list at the top of my page. My page template has: <rich:messages globalOnly="true" id="page-messages"> ... </rich:messages> and the controls have: <rich:message for="my-control-id" id="my-control-id-message"> ... </rich:message> I can switch the rich:messages to h:messages, and it behaves as it should. Also reverting back to the RichFaces 3.2.2.SR1 jars makes the problem go away, but I get the other older bugs back :( -- 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

12 years, 9 months

19
67
0 / 0

[JBoss JIRA] Created: (RF-7955) ExtendedDataTable : Only first column correctly resize

by Nicolas Gaudin (JIRA)

ExtendedDataTable : Only first column correctly resize ------------------------------------------------------ Key: RF-7955 URL: https://jira.jboss.org/jira/browse/RF-7955 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.2.GA, 3.3.2.CR1 Environment: JSF RI 1.2_13 Facelets 1.1.14 (with .jspx files) Glassfish Jdk 1.6 Reporter: Nicolas Gaudin Fix For: 3.3.2.GA Hi, During my test to deliver, I discovered that the columns of all my EDTs would not resize correctly. More precisely, the first column resizes without any problem but the others resize WITHOUT resizing the header. I must mention that my EDT use value binding for dynamic column creation. My actions that generated this issue: - moved from jsp to facelets (with jspx extension) - upgraded to JSF 1.2_13 This affected 3.3.2.CR1, the version I was using. I then upgraded to 3.3.2.GA to check if this would fix but no luck Also, I thought that 3.3.2.GA would full scrolling support for EDT (horizontal mainly) Is that the case? Could you please confirm? May thanks in advance -- 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

12 years, 9 months

3
12
0 / 0

[JBoss JIRA] Created: (RF-5765) ExtendedDataTable: Drag and Drop for columns does not work if column id contain '-' symbol.

by Andrei Markavtsov (JIRA)

ExtendedDataTable: Drag and Drop for columns does not work if column id contain '-' symbol. ------------------------------------------------------------------------------------------- Key: RF-5765 URL: https://jira.jboss.org/jira/browse/RF-5765 Project: RichFaces Issue Type: Bug Environment: RF 3.3.0 Reporter: Andrei Markavtsov Assignee: Nick Belaevski <h:form id="form"> <rich:extendedDataTable value="#{test3.rows}" var="row" tableState="#{test3.tableState}"> <rich:columns sortBy="#{row[ind]}" sortOrder="#{column.ordering}" filterBy="#{row[ind]}" filterValue="#{column.filterValue}" id="column-#{column.name}" value="#{test3.columns}" label="#{column.name}" var="column" index="ind"> <f:facet name="header"> <h:outputText value="#{column.name}" /> </f:facet> <h:outputText value="#{row[ind]}" /> </rich:columns> </rich:extendedDataTable> </h:form> Erroneus code: AbstractExtendedTableRenderer.doDecode(1239). -- 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

12 years, 9 months

4
4
0 / 0

[JBoss JIRA] Created: (RF-7932) photoalbum: tree with albums collapses after drag&drop

by Pavol Pitonak (JIRA)

photoalbum: tree with albums collapses after drag&drop ------------------------------------------------------ Key: RF-7932 URL: https://jira.jboss.org/jira/browse/RF-7932 Project: RichFaces Issue Type: Bug Components: examples Affects Versions: 3.3.2.GA Environment: JBoss AS 5.1, IE 7, FF 3.5 Reporter: Pavol Pitonak Fix For: 3.3.3.CR1 When the user expands all albums and then d&d a picture from one album to another one, picture is moved and the tree is collapsed -- usability problem. -- 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

12 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (RF-7921) DropDownMenu: wrong vertical positioning of popup list on scrolling in Firefox

by rofl rofl (JIRA)

DropDownMenu: wrong vertical positioning of popup list on scrolling in Firefox ------------------------------------------------------------------------------ Key: RF-7921 URL: https://jira.jboss.org/jira/browse/RF-7921 Project: RichFaces Issue Type: Bug Components: component-menu Affects Versions: 3.3.2.CR1, 3.3.1 Environment: winXP, hibernate 3.2.4.sp1, seam 2.1.0.SP1, firefox 3.5.3 Reporter: rofl rofl Priority: Minor The popup list of the drop down menu is wrongly positioned when one scrolls the page. It is shown too far below it's anchor point (i.e. it is not directly connected to it's anchor point) - the offset changes on scrolling (i.e. the more one scrools down, the farer below it is shown) -- 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

12 years, 9 months

5
8
0 / 0

[JBoss JIRA] Created: (RF-7344) Add controls for where in the header loaded scripts are placed

by Jay Balunas (JIRA)

Add controls for where in the header loaded scripts are placed -------------------------------------------------------------- Key: RF-7344 URL: https://jira.jboss.org/jira/browse/RF-7344 Project: RichFaces Issue Type: Task Components: browser compatibility, core Affects Versions: 3.3.1 Environment: IE8 Reporter: Jay Balunas Fix For: 3.3.2.CR1 IE8 requires some header content be located at the very top of the header. Because RichFaces places some of the loaded scripts first this can break. For example "<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />" will be ignored if not the first element after the header. Although the work around can be to just place the value in the header directly "<header name="X-UA-Compatible">IE=EmulateIE7</header>", RichFaces should have a way to control the location of the scripts in the header. This could take the form of a new context param or perhaps a tag that RF can trigger off of for default script placement. If not there behavior is defaulted to current. -- 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

12 years, 10 months

7
8
0 / 0

[JBoss JIRA] Created: (RF-3566) Can't use messages with fileUpload

by Ilya Shaikovsky (JIRA)

Can't use messages with fileUpload ---------------------------------- Key: RF-3566 URL: http://jira.jboss.com/jira/browse/RF-3566 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.1 Reporter: Ilya Shaikovsky Assigned To: Nick Belaevski http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153840#4153840 Using his code in demosite listener I'm getting next behaviour. "Transfer error occuried" error in file upload status. But rich:messages which added to the page doesn't show anything. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

8
15
0 / 0

[JBoss JIRA] Created: (RF-8201) Print RichFaces module information at start up

by Jay Balunas (JIRA)

Print RichFaces module information at start up ---------------------------------------------- Key: RF-8201 URL: https://jira.jboss.org/jira/browse/RF-8201 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: build, core Reporter: Jay Balunas Fix For: 4.0.0.ALPHA2 During start up all RichFaces modules should printout meta data into the log. This would be for each module api, ui, impl, themes, etc.... This will be more important as we allow for module releases that may not always be 100% in sync. It will also help with debugging issues. -- 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

12 years, 11 months

4
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues December 2009