July 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12295) Facelets exception since 4.2.1

by Nikolai Alexeev (JIRA)

Nikolai Alexeev created RF-12295: ------------------------------------ Summary: Facelets exception since 4.2.1 Key: RF-12295 URL: https://issues.jboss.org/browse/RF-12295 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core, component-output Affects Versions: 4.2.2.Final, 4.2.1.Final, 4.2.1.CR1 Reporter: Nikolai Alexeev Facelets exception occurs on postback phase if there's <a4j:outputPanel> on the page. -- 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

13 years, 4 months

3
22
0 / 0

[JBoss JIRA] (RF-12315) Portlet RenderURL invoked rather than a ResourceURL when toggleType="ajax" used with rich:tree

by Neil Griffin (JIRA)

Neil Griffin created RF-12315: --------------------------------- Summary: Portlet RenderURL invoked rather than a ResourceURL when toggleType="ajax" used with rich:tree Key: RF-12315 URL: https://issues.jboss.org/browse/RF-12315 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tree Affects Versions: 4.2.2.Final Environment: Portlet Environment Reporter: Neil Griffin This issue was first reported in the Liferay forums here: http://www.liferay.com/community/forums/-/message_boards/view_message/142... Similar to RF-12263, I think the problem is that RichFaces JS is not using the "javax.faces.encodedURL" for postback. -- 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

13 years, 4 months

3
8
0 / 0

[JBoss JIRA] (RF-12263) Portlet RenderURL invoked rather than a ResourceURL when rich:dragSource dropped on rich:dropTarget

by Neil Griffin (JIRA)

Neil Griffin created RF-12263: --------------------------------- Summary: Portlet RenderURL invoked rather than a ResourceURL when rich:dragSource dropped on rich:dropTarget Key: RF-12263 URL: https://issues.jboss.org/browse/RF-12263 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: portal Affects Versions: 4.2.0.Final Reporter: Neil Griffin This issue was first reported in the Liferay forums here: http://www.liferay.com/community/forums/-/message_boards/message/13941321 I was able to reproduce the error using the sample attached to the forum post by Michael Weber. I think the problem is that RichFaces JS is not using the "javax.faces.encodedURL" for postback when the drop occurs. -- 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

13 years, 4 months

3
7
0 / 0

[JBoss JIRA] (RF-12185) AJAX rendering is broken for h:commandLink

by Nick Dev (JIRA)

Nick Dev created RF-12185: ----------------------------- Summary: AJAX rendering is broken for h:commandLink Key: RF-12185 URL: https://issues.jboss.org/browse/RF-12185 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 4.2.1.Final Environment: JSF Mojarra 2.1.7 Reporter: Nick Dev Rendering of h:commandLink makes it to disappear from the page when done with a4j:commandLink or a4j:ajax. Notes: - rendering of h:commandButton works fine - rendering with f:ajax works fine -- 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

13 years, 4 months

4
5
0 / 0

[JBoss JIRA] (RF-12218) Using quotes in cdk:call expression generate a broken class

by Paul Dijou (JIRA)

Paul Dijou created RF-12218: ------------------------------- Summary: Using quotes in cdk:call expression generate a broken class Key: RF-12218 URL: https://issues.jboss.org/browse/RF-12218 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: cdk Affects Versions: 4.2.1.Final Environment: All Reporter: Paul Dijou Priority: Critical If I need to pass a String to a {{<cdk:call expression="..."}}, I'm forced to indicate that's it's a String and not a var. Since I can't use double-quote, the only solution I see is doing the same as in EL : single quote. But it looks like the CDK only copy/paste the expression in the Java code. Problem is single quote in Java class are not what I wanted (and crash the class). For example : {code:xml} <cdk:call expression="renderFacet('brand', facesContext, component)" /> {code} will generate {code:java} renderFacet('brand', facesContext, component); {code} but it should generate {code:java} renderFacet("brand", facesContext, component); {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

13 years, 4 months

3
9
0 / 0

[JBoss JIRA] (RF-11881) Rich Faces 4 can't change jQuery selector

by Nicola Nick (JIRA)

Nicola Nick created RF-11881: -------------------------------- Summary: Rich Faces 4 can't change jQuery selector Key: RF-11881 URL: https://issues.jboss.org/browse/RF-11881 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Nicola Nick I used Rich Faces 4 in my project. Morover i have to use prototype functionality. In the last version of rich faces is used only jQuery. The my problem is that i have to reserve $ selector to prototype but i can't do it because i don't know how to change the selector inside richfaces library. -- 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

13 years, 4 months

2
9
0 / 0

[JBoss JIRA] Created: (RF-11072) File Upload immediateUpload has no effect in Richfaces 4.0

by Jesse Bowes (JIRA)

File Upload immediateUpload has no effect in Richfaces 4.0 ---------------------------------------------------------- Key: RF-11072 URL: https://issues.jboss.org/browse/RF-11072 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Jesse Bowes Richfaces 4.0 does not seem to support immediateUpload. Setting this value to true still requires the user to manually upload the files -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

6
11
0 / 0

[JBoss JIRA] (RF-11551) [rich:tabPanel] [rich:extendedDataTable] The scrollbar of rich:extendedDataTable disappears inside rich:tabPanel (switchType=ajax) and problems with switchType=client

by Rene O (Created) (JIRA)

[rich:tabPanel] [rich:extendedDataTable] The scrollbar of rich:extendedDataTable disappears inside rich:tabPanel (switchType=ajax) and problems with switchType=client ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: RF-11551 URL: https://issues.jboss.org/browse/RF-11551 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.1.0.Milestone2 Environment: Tomcat6, Firefox 7, IE 8, myfaces 2.1.3 Reporter: Rene O A testcase to reproduce this issue is attached. Steps to reproduce this issue: 1. http://localhost:8080/jsftest/tabandtable.jsf 2. switch to tab "Tab with Table" -> table has scrollbar 3. switch to tab "Tab with Table2" -> table has no scrollbar, which is not the expected behaviour 4. switch again to tab "Tab with Table" -> table has now also no scrollbar, which is not the expected behaviour If you use switchType=server everything works as expected. If you use switchType=client there is another problem: The content of the tables is not visible. It is visible after you use the dataScroller. But there is also no scrollbar visible. -- 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

13 years, 4 months

5
8
0 / 0

[JBoss JIRA] (RF-12033) ExtendedDataTable doesn't show up in tabpanel with switchType="client"

by Josh Hill (JIRA)

Josh Hill created RF-12033: ------------------------------ Summary: ExtendedDataTable doesn't show up in tabpanel with switchType="client" Key: RF-12033 URL: https://issues.jboss.org/browse/RF-12033 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.2.0.Final Environment: FireFox 10.0.2 (works in IE7) GlassFish 3.1 Reporter: Josh Hill Attachments: richfaces-test.zip testcase attached 1. Open test1.xhtml 2. Switch to Tab Two Expected Result: ExtendedDataTable shows up Actual Result: Grey bar shows up Workaround is to set switchType to "ajax" instead of "client" -- 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

13 years, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (RF-8287) Make build incremental

by Alexander Smirnov (JIRA)

Make build incremental ---------------------- Key: RF-8287 URL: https://jira.jboss.org/jira/browse/RF-8287 Project: RichFaces Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Alexander Smirnov Fix For: 4.0.0.ALPHA2 To speed-up development builds, CDK should record "last modified" time of source files in the model. Generated file should be written only if target does not exist or its modification time is less then recorded for source files. -- 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

13 years, 4 months

8
33
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues July 2012