May 2008 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-3217) Add missing sections for the rich:toolBarGroup component

by Catherine Luts (JIRA)

Add missing sections for the rich:toolBarGroup component --------------------------------------------------------- Key: RF-3217 URL: http://jira.jboss.com/jira/browse/RF-3217 Project: RichFaces Issue Type: Task Components: doc Reporter: Catherine Luts Assigned To: Catherine Luts Fix For: 3.2.1 Add missing information and sections for toolBarGroup component (Relevant Resources Links, Definition of Custom Style Classes) -- 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

16 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (RF-3542) AjaxStateManager restores state after redirect (breaks JSF Spec)

by Mathias Werlitz (JIRA)

AjaxStateManager restores state after redirect (breaks JSF Spec) ---------------------------------------------------------------- Key: RF-3542 URL: http://jira.jboss.com/jira/browse/RF-3542 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.5, 3.1.0, 3.1.x Environment: JSF 1.1 RI / Myfaces 1.1.5, Tomcat 5.5, server-side state-saving Reporter: Mathias Werlitz Priority: Critical Attachments: faces-config.xml, testCase.jsp The implementation of AjaxStateManager changes the general behaviour of JSF and breaks the JSF spec. If Richfaces 3.1.x is deployed with an JSF 1.1 webapp a previous state of a view is (wrongly) restored after a redirect. If Richfaces is not deployed with the same application a new fresh view is created in this case. I provided a small test case that does not use any Richfaces components. Set up a very simple JSF webapp with the Sun RI or Myfaces - it doesn't matter. Now the test case WITHOUT Richfaces: 1. open testCase.jsf in your browser 2. enter something different into the first input field 3. click "validate" You should see some error messages. 4. now click "navigate" Now the validation will be skipped and the simple navigation rule of the faces-config will kick in: redirecting to the same page. You will see "test" in the first input field. Everything worked fine. Now the ERROR: Install Richfaces 3.1.x into the app and do the same as described above. After you clicked "navigate" you will see, that the first input field does not read "test" - instead it still shows the input entered before navigating to the page. It seems that Richfaces always does restore an previous version of the viewstate if a navigation rule that uses a redirect was used. This is wrong. After a navigation with or without a redirect always a new fresh view/viewsate should be created. By the way: If you use Ajax4jsf 1.1.x or remove the "redirect" tag from the navigation rule the test case works fine as the version without Richfaces. I traced down the problem to AjaxStateManager line 292 (Richfaces 3.1.5). It seems that if a viewstate was saved for a view than this viewstate will be restored except there is a newer version or no state. Seems to be a fall-back solution. If a redirect was used no newer version was saved, thus an inappropriate old state will be restored although after a navigation a completly new state should be created for the target view (JSF spec). -- 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

16 years, 3 months

4
6
0 / 0

[JBoss JIRA] Created: (RF-2134) RichFaces Architecture requires clearer explanation

by Svetlana mukhina (JIRA)

RichFaces Architecture requires clearer explanation --------------------------------------------------- Key: RF-2134 URL: http://jira.jboss.com/jira/browse/RF-2134 Project: RichFaces Issue Type: Task Components: doc Affects Versions: 3.1.0 Reporter: Svetlana mukhina Assigned To: Gleb Galkin Fix For: 3.2.0 It seems that some topics should be described or contain more details, have a look at this http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4124909#4124909 , add necessary information to the guide -- 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

16 years, 3 months

2
8
0 / 0

[JBoss JIRA] Created: (RF-3153) <a4j:portlet> not needed anymore with JBossPortletBridge => tell it in the doc.

by Antoine Herzog (JIRA)

<a4j:portlet> not needed anymore with JBossPortletBridge => tell it in the doc. -------------------------------------------------------------------------------- Key: RF-3153 URL: http://jira.jboss.com/jira/browse/RF-3153 Project: RichFaces Issue Type: Task Components: doc Affects Versions: 3.2.0 Environment: JBoss PortletBridge B2 / RichFaces 3.2.0 / JBoss Portal Reporter: Antoine Herzog Priority: Minor Fix For: 3.2.1 In another jira, Wesley says that : "The configurations used in this issue are old - like a4j:portlet is not needed. You should now be using JBoss Portlet Bridge (http://www.jboss.org/portletbridge/). the Beta2 demo application proves that this is working." JIRA is : http://jira.jboss.com/jira/browse/PBR-20 (at the end of the comments) if the a4j:portlet is not needed : - not needed only with the JBoss PortletBridge, but needed with other bridges ? - not needed never ? It would be great to have something explained about that in the documentation of RichFaces. Or a "Deprecated" put on it. And in the doc or wiki of JBoss PortalBridge. Now, the component is described, nothing to prevent using it... -- 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

16 years, 3 months

3
11
0 / 0

[JBoss JIRA] Created: (RF-3210) Filtering: provide rich classes to generated via filterBy input

by Ilya Shaikovsky (JIRA)

Filtering: provide rich classes to generated via filterBy input ---------------------------------------------------------------- Key: RF-3210 URL: http://jira.jboss.com/jira/browse/RF-3210 Project: RichFaces Issue Type: Feature Request Affects Versions: 3.2.1 Reporter: Ilya Shaikovsky Assigned To: Nick Belaevski Fix For: 3.2.1 -- 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

16 years, 3 months

5
8
0 / 0

[JBoss JIRA] Created: (RF-3138) dataOrderedList: columnClasses doesn't work

by Tsikhon Kuprevich (JIRA)

dataOrderedList: columnClasses doesn't work ------------------------------------------- Key: RF-3138 URL: http://jira.jboss.com/jira/browse/RF-3138 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.5 Environment: 3.1.5.CR2 Reporter: Tsikhon Kuprevich Assigned To: Nick Belaevski columnClasses: css classes aren't encoded in the html rendered. -- 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

16 years, 3 months

4
7
0 / 0

[JBoss JIRA] Created: (RF-2923) for attribute in datascroller not handled when using datascroller in custom tags

by Alan Stewart (JIRA)

for attribute in datascroller not handled when using datascroller in custom tags -------------------------------------------------------------------------------- Key: RF-2923 URL: http://jira.jboss.com/jira/browse/RF-2923 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.0 Reporter: Alan Stewart Have writtem custom JSF tags that incorporate the rich:datascroller. We pass in the id of the rich:dataTable in our custom tag and the datascroller has working using this in versions up until 3.1.4.SR1. Changed to 3.2.0.GA and now without any other code changes, I get an error: could not find dataTable for datascroller j_id171. When we hard-code the id of the dataTable in the "for" attribute of the rich:datascoller, it all works OK. -- 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

16 years, 3 months

5
15
0 / 0

[JBoss JIRA] Created: (RF-2917) Validity of all xml files

by Gleb Galkin (JIRA)

Validity of all xml files ------------------------- Key: RF-2917 URL: http://jira.jboss.com/jira/browse/RF-2917 Project: RichFaces Issue Type: Task Components: doc Affects Versions: 3.2.1 Reporter: Gleb Galkin Assigned To: Gleb Galkin Fix For: 3.2.1 All xml files should be validated according to DTD specified in master.xml. Just open master.xml in Oxygen and press Ctrl+Shift+V or go "Document->Validate->Validate Document" -- 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

16 years, 3 months

3
12
0 / 0

[JBoss JIRA] Created: (RF-2908) Typo in section 5.4.1 in the Reference Manual

by Joao Paulo Viragine (JIRA)

Typo in section 5.4.1 in the Reference Manual --------------------------------------------- Key: RF-2908 URL: http://jira.jboss.com/jira/browse/RF-2908 Project: RichFaces Issue Type: Task Components: doc Affects Versions: 3.2.0 Reporter: Joao Paulo Viragine In section 5.4.1 of the Reference Manual (http://labs.jboss.com/file-access/default/members/jbossrichfaces/freezone...) the phrase: "Most common problem with using reRender is pointing it to the component that has a "reRender" attribute" Should be: "Most common problem with using reRender is pointing it to the component that has a "rendered" attribute" Substitute: "reRender" attribute by: "rendered" attribute -- 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

16 years, 3 months

4
10
0 / 0

[JBoss JIRA] Created: (RF-2775) Rearrange skin parameters table

by Nick Belaevski (JIRA)

Rearrange skin parameters table ------------------------------- Key: RF-2775 URL: http://jira.jboss.com/jira/browse/RF-2775 Project: RichFaces Issue Type: Task Affects Versions: 3.2.0 Reporter: Nick Belaevski Assigned To: Svetlana mukhina Fix For: 3.2.0 Swap skin parameters table - CSS styles should be to the left, and corresponding skin parametrs to the right -- 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

16 years, 3 months

3
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues May 2008