November 2008 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-3849) rich:simpleTogglePanel bodyClass and headerClass attributes do not work in JBoss Portal environment.

by Tareq Nabeel (JIRA)

rich:simpleTogglePanel bodyClass and headerClass attributes do not work in JBoss Portal environment. ---------------------------------------------------------------------------------------------------- Key: RF-3849 URL: http://jira.jboss.com/jira/browse/RF-3849 Project: RichFaces Issue Type: Bug Components: portal Affects Versions: 3.2.1 Environment: RichFaces 3.2.1, JBoss Portal 2.6.5.SP1 Reporter: Tareq Nabeel CSS classes specified in bodyClass and headerClass attributes of <rich:simpleTogglePanel> do not override default skin settings in JBoss Portal environment. They do override correctly in JBoss 4.2.2. -- 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

13 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (RF-3729) State manager tags

by Nick Belaevski (JIRA)

State manager tags ------------------ Key: RF-3729 URL: http://jira.jboss.com/jira/browse/RF-3729 Project: RichFaces Issue Type: Feature Request Components: planning Affects Versions: 3.3.0 Reporter: Nick Belaevski Assigned To: Alexander Smirnov Fix For: 3.3.0 -- 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

13 years, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (RF-2505) wizard using a4j:include doesn't work in ie7 after you hit ie7 back button

by Pavel Savara (JIRA)

wizard using a4j:include doesn't work in ie7 after you hit ie7 back button -------------------------------------------------------------------------- Key: RF-2505 URL: http://jira.jboss.com/jira/browse/RF-2505 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.4, 3.1.3 Environment: Windows XP, Internet Explorer7 Reporter: Pavel Savara Steps which leads to expose the bug. 1. Go to http://livedemo.exadel.com/richfaces-demo/richfaces/include.jsf?c=include 2. fill the a4j:include wizard and click next 3. Click on Tag information tab 4. Hit Internet Explorer back button you should be back on the main page 5. <a4j:include> wizard is on first page again and if you click on next nothing happens!. This is tested in Internet Explorer 7. In Firefox everything works fine and after step 4. you see again second page of the wizard. I have the same problem in my own pages. -- 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

13 years, 10 months

4
11
0 / 0

[JBoss JIRA] Created: (RF-3273) Ajax response should not send <head> tag

by Dan Allen (JIRA)

Ajax response should not send <head> tag ---------------------------------------- Key: RF-3273 URL: http://jira.jboss.com/jira/browse/RF-3273 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.0 Reporter: Dan Allen There is an expectation that Ajax responses are reasonably small. However, RichFaces Ajax responses are unreasonably large because the BaseXMLFilter is mistakingly sending the entire <head> tag regardless of whether the response type is Ajax or not. The <head> tag contains many <script> and <link> tags that bloat the response. The BaseXMLFilter should only be sending the <head> tag on a normal response. Now you might think, "What if the region to be rendered has new components (that were not previously rendered) for which styles and scripts are necessary for proper behavior?" Well, RichFaces is already smart and incorporates these styles and scripts into the initial response even if the associated components are not rendered. So there is absolutely *no* reason to have them sent in the Ajax response. -- 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

13 years, 10 months

3
13
0 / 0

[JBoss JIRA] Created: (RF-2203) suggestionbox in Jboss portal gives err "AjaxRendererUtils - Failed to obtain Response#setHeader() method: java.lang.NoSuchMethodException: org.jboss.portlet.JBossRenderResponse.setHeader(java.lang.String, jave.lan.string)"

by prashant verma (JIRA)

suggestionbox in Jboss portal gives err "AjaxRendererUtils - Failed to obtain Response#setHeader() method: java.lang.NoSuchMethodException: org.jboss.portlet.JBossRenderResponse.setHeader(java.lang.String, jave.lan.string)" ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: RF-2203 URL: http://jira.jboss.com/jira/browse/RF-2203 Project: RichFaces Issue Type: Bug Environment: jboss portal 2.4.1 jdk1.5 RF3.1.4GA Reporter: prashant verma hi here is my code. <%@ taglib uri="http://richfaces.org/a4j" prefix="a4j"%> <%@ taglib uri="http://richfaces.org/rich" prefix="rich"%> <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%> <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f"%> <html> <head> <title>repeater</title> </head> <body> <f:view> <h:form id="RichFacesForm"> <rich:panel header="Simple Echo"> <h:inputText value="#{bean.text}" id="suggest" /> <rich:suggestionbox for="suggest" suggestionAction="#{bean.autocomplete}" var="suggest" height="50" width="100"> <h:column> <h:outputText value="#{suggest}" /> </h:column> </rich:suggestionbox> </rich:panel> </h:form> </f:view> </body> </html> bean is this :- public class Bean { private String text = ""; public Bean() { } public String getText() { return text; } public void setText(String text) { this.text = text; } public List autocomplete(Object event) { String pref = event.toString(); System.out.println("pref : "+pref); ArrayList a = new ArrayList(); for(int i =0 ;i<10;i++) a.add(i+""); System.out.println("a - "+a); return a; } }} i have made appropriate enteries in the faces-config.xml Everything is fine but when I try to access the page in the jbossportal then while rerendering this err occurs ..... 16:07:10,923 INFO [STDOUT] pref : 1 16:07:10,923 INFO [STDOUT] engineModelValues - [0, 1, 2, 3, 4, 5, 6, 7, 8, 9] 16:07:10,923 INFO [STDOUT] ERROR AjaxRendererUtils - Detecting request character encoding is disable. 16:07:10,923 INFO [STDOUT] ERROR AjaxRendererUtils - Failed to obtain Response#setHeader() method: java.lang.NoSuchMethodException: org.jboss.portlet.JBossRenderResponse.setHeader(java.lang.String, java.lang.String) ..... Please suggest. Thanks in Advance -- 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

13 years, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (RF-2177) two modal panel in two different portlets in one portal page: only one panel can be shown

by Martin Ratajczak (JIRA)

two modal panel in two different portlets in one portal page: only one panel can be shown ----------------------------------------------------------------------------------------- Key: RF-2177 URL: http://jira.jboss.com/jira/browse/RF-2177 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.3 Environment: Win XP, IE 7.0, JBoss Portal 2.6.2-GA, RichFaces 3.1.3.CR4 Reporter: Martin Ratajczak If you have two modal panel in two different portlets in one portal page you can only show one modal panel. -- 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

13 years, 10 months

4
14
0 / 0

[JBoss JIRA] Created: (RF-2135) javax.faces.application.ViewExpiredException is thrown in a Richfaces portlet

by Viggo Navarsete (JIRA)

javax.faces.application.ViewExpiredException is thrown in a Richfaces portlet ----------------------------------------------------------------------------- Key: RF-2135 URL: http://jira.jboss.com/jira/browse/RF-2135 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.4 Environment: jdk 1.5.0_08 JBoss AS 4.2.2 JBoss Portal 2.6.3 Richfaces 3.1.4.CR4 and 3.1.4.GA Reporter: Viggo Navarsete I have a Richfaces portlet that basically consists of one page (start.xhtml) where there is one input field and a button. When the user push the button my SearchBean's search method is executed. Right now I'm just returning the string "success" (to test it), and then the user is supposed to get the start.xhtml displayed once more, but now with a search result below the search input. I'm getting this ViewExpiredException when pushing the button. Please see the JBoss forum reference for more information about the actual implementation. I can also provide more information on request if necessary. -- 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

13 years, 10 months

7
18
0 / 0

[JBoss JIRA] Created: (RF-1433) Support rerendering inidividual rows of tables

by Pete Muir (JIRA)

Support rerendering inidividual rows of tables ---------------------------------------------- Key: RF-1433 URL: http://jira.jboss.com/jira/browse/RF-1433 Project: RichFaces Issue Type: Feature Request Affects Versions: 3.1.0 Reporter: Pete Muir Some links from a discussion with Alex http://msdn2.microsoft.com/en-us/library/ms535901.aspx http://msdn2.microsoft.com/en-us/library/ms532998.aspx -- 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

13 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (RF-1257) Ability for a user to interruput (stop) Ajax request on a4j:status

by Mikhail Grushinskiy (JIRA)

Ability for a user to interruput (stop) Ajax request on a4j:status ------------------------------------------------------------------ Key: RF-1257 URL: http://jira.jboss.com/jira/browse/RF-1257 Project: RichFaces Issue Type: Feature Request Reporter: Mikhail Grushinskiy Ability for a user to interruput (stop) Ajax request on a4j:status. Similarly to browser's stop buttun we need ability for a user to stop hanging Ajax requests. I think logical place would be in a4j:status tag. -- 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

13 years, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (RF-1060) Add possibility to select a row in rich:dataTable, same the rich:scrollableDataTable

by Rodrigo Assump￧￣o (JIRA)

Add possibility to select a row in rich:dataTable, same the rich:scrollableDataTable ------------------------------------------------------------------------------------ Key: RF-1060 URL: http://jira.jboss.com/jira/browse/RF-1060 Project: RichFaces Issue Type: Feature Request Affects Versions: 3.1.0 Environment: Windows XP Java 6 JBoss 4.20.GA Reporter: Rodrigo Assump￧￣o Priority: Critical The rich:dataTable component have a better look and feel than rich:scrollableDataTable, and no have scroll. In a various cases the dataTable is more apropriate than scrollableDataTable, but the dataTable don't have the select row feature. The new feature have a possibilty to choose switchType (same the simpleTogglePanel): server, ajax, client. -- 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

13 years, 10 months

5
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues November 2008