March 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12110) [rich:contextMenu] contextmenu doesn't work anymore if an ajax request is fired while contextmenu is visible

by Rene O (JIRA)

Rene O created RF-12110: --------------------------- Summary: [rich:contextMenu] contextmenu doesn't work anymore if an ajax request is fired while contextmenu is visible Key: RF-12110 URL: https://issues.jboss.org/browse/RF-12110 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.0.Final Environment: Tomcat 7, myfaces-2.1.6, richfaces-4.2.0.Final and 4.2.1-SNAPSHOT Reporter: Rene O The example shows the problem: {code:title=example.xhtml} <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:a4j="http://richfaces.org/a4j" xmlns:rich="http://richfaces.org/rich"> <h:head> <title>JSF Test</title> </h:head> <h:body> Steps to reproduce the issue: 1. right click to show context menu 2. wait till context menu hides 3. click button 'click me' 4. right click to show context menu 5. context menu is visible Now do the following 1. right click to show context menu 2. click button 'click me' before context menu hides 3. right click to show context menu 4. context menu doesn't work anymore... <h:form id="formA"> <a4j:commandButton id="but" value="click me" execute="@this" render="formA"/> <h:panelGroup id="panel" layout="block" style="width:200px;height:50px;background-color:#CCCCCC"> right click for context-menu </h:panelGroup> <rich:contextMenu id="myContext" attached="true" target="panel" mode="client" hideDelay="3000"> <rich:menuItem id="contextTest"> Test </rich:menuItem> </rich:contextMenu> </h:form> </h:body> </html> {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

12 years, 9 months

2
1
0 / 0

[JBoss JIRA] (RF-12105) panelToggleListener attribute @listener does not work

by Jiří Štefek (JIRA)

Jiří Štefek created RF-12105: -------------------------------- Summary: panelToggleListener attribute @listener does not work Key: RF-12105 URL: https://issues.jboss.org/browse/RF-12105 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-misc Affects Versions: 4.2.0.Final Environment: RichFaces 4.2.1-SNAPSHOT Metamer 4.2.1-SNAPSHOT Mojarra 2.1.5-SNAPSHOT JBoss AS 7.1.0.Final OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux Firefox 11.0 @ Linux x86_64 Reporter: Jiří Štefek # Deploy Metamer. # Open http://localhost:8080/metamer/faces/components/richPanelToggleListener/co... # Click on chevron to collapse a panel. # Messages with "* pannelToggleListenerBean panel collapsed" should appear in phases list. -- 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

12 years, 9 months

2
1
0 / 0

[JBoss JIRA] (RF-12098) PickList doesn't accept comma in string value

by Stefan Risto (JIRA)

Stefan Risto created RF-12098: --------------------------------- Summary: PickList doesn't accept comma in string value Key: RF-12098 URL: https://issues.jboss.org/browse/RF-12098 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-selects Affects Versions: 4.2.0.Final Reporter: Stefan Risto The rich:pickList Component does not handle values containing commas. I used a converter and in the getAsString - Method a String containing a comma was returned, such as "You,Me". After selecting this value in the pick list the converters getAsObject method is called twice, once for "You" and once for "Me". I would expect to get the same value in getAsObject as the converters getAsString returned. Maybe the comma should be escaped by the component and/or the javascript code. This Bug seems to be related to RF-6766, but that bug is not targeted for RF 4.X -- 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

12 years, 9 months

2
2
0 / 0

[JBoss JIRA] (RF-12097) Richfaces 4.2.0 invalid css entry for *.rf-insl-tt

by Stephan Meisinger (JIRA)

Stephan Meisinger created RF-12097: -------------------------------------- Summary: Richfaces 4.2.0 invalid css entry for *.rf-insl-tt Key: RF-12097 URL: https://issues.jboss.org/browse/RF-12097 Project: RichFaces Issue Type: Bug Components: skinning Affects Versions: 4.2.0.Final Environment: Tomcat 6.0.35 Richfaces 4.2.0 Windows 7 Reporter: Stephan Meisinger a invalid css syntax for *.rf-insl-tt for PackedCompressed/DEFAULT/packed/packed.css *.rf-insl-tt{position:absolute;display:none;padding:2px;border:1px solid "#E5973E ";background-color:#FAE6B0;} should be *.rf-insl-tt{position:absolute;display:none;padding:2px;border:1px solid #E5973E;background-color:#FAE6B0;} see http://www.w3.org/TR/CSS1/#border and http://www.w3.org/TR/CSS1/#color-units -- 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

12 years, 9 months

2
1
0 / 0

[JBoss JIRA] (RF-12094) Provide a feature to rich:dataTable that reflects the default sort order on a column (according to the JPQL statement that produced the list items)

by Karsten Wutzke (JIRA)

Karsten Wutzke created RF-12094: ----------------------------------- Summary: Provide a feature to rich:dataTable that reflects the default sort order on a column (according to the JPQL statement that produced the list items) Key: RF-12094 URL: https://issues.jboss.org/browse/RF-12094 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Karsten Wutzke A rich:dataTable list is usually sorted by one or several columns according to the JPQL or other statement that produced the list. I would be worthwhile to have the rich:dataTable reflect the default ordering state by providing an attribute to rich:column that would set the respective up or down sort arrow instead of the default up-down arrow. By default, e.g. on page reload, if nothing was remembered by the browser, rich:dataTable defaults to the dual up-down arrow for all rich:column's. -- 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

12 years, 9 months

2
2
0 / 0

[JBoss JIRA] (RF-12096) Push: there is delay between repeated subscribtion

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12096: ------------------------------- Summary: Push: there is delay between repeated subscribtion Key: RF-12096 URL: https://issues.jboss.org/browse/RF-12096 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-push/poll Affects Versions: 4.2.0.Final Reporter: Lukáš Fryč When you have conditionally rendered {{a4j:push}} component and you disable it, then it stops to receive push events. Once you enable it, there is delay before it will start to receive events again. Sample code for reproduction: {code:xml} <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core" xmlns:a4j="http://richfaces.org/a4j"> <f:view> <h:head> </h:head> <h:body> <h:form>  <a4j:commandButton value="Push 1!" action="#{richBean.push}" /> <a4j:outputPanel id="pushPanel"> <a4j:push id="push" rendered="#{not pushDisabled}" address="sampleAddress" ondataavailable="$('*[id$=outputDate]').text(event.rf.data)" onsubscribed="alert('subscribed')" /> </a4j:outputPanel> <a4j:outputPanel id="pushDisablementPanel"> <h:selectBooleanCheckbox value="#{pushDisabled}"> <a4j:ajax render="pushPanel pushDisablementPanel" /> </h:selectBooleanCheckbox> <h:outputText value="#{pushDisabled ? 'disabled' : 'enabled'}" /> </a4j:outputPanel> <a4j:outputPanel id="outputDate"> #{richBean.date} </a4j:outputPanel> </h:form> </h:body> </f:view> </html> {code} {code:java} package demo; import java.util.Date; import javax.faces.bean.ManagedBean; import org.richfaces.application.push.MessageException; import org.richfaces.application.push.TopicKey; import org.richfaces.application.push.TopicsContext; @ManagedBean public class RichBean { public Date getDate() { return new Date(); } public void push() throws MessageException { TopicKey topicKey = new TopicKey("sampleAddress"); TopicsContext topicsContext = TopicsContext.lookup(); topicsContext.publish(topicKey, new Date().toString()); System.out.println("push event"); } } {code} Steps to reproduce: 1. open the sample page (the "subscribed" message appears) 2. click on Push! button (the date is changed) 3. check the checkbox 4. click on Push! button (the date is not changed anymore) 5. uncheck the checkbox (the "subscribed" message appears again) 6. click on Push! EXPECTED: the date should be changed ACTUAL: the date is not changed If you will wait for some seconds, the Push! button will cause change of the date, but in this delay, client can lose data updates (since "subscribed" event does not show that the client is starting to receive data). -- 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

12 years, 9 months

2
1
0 / 0

[JBoss JIRA] (RF-12040) Multi-form document - command button (submit) does not work after rendering

by Jean ANDRE (JIRA)

Jean ANDRE created RF-12040: ------------------------------- Summary: Multi-form document - command button (submit) does not work after rendering Key: RF-12040 URL: https://issues.jboss.org/browse/RF-12040 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Environment: cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - JSF/Mojarra 2.1.6 - springframework-3.0.6.RELEASE - sac-1.3 - Windows 7 - FireFox 10 - RichFaces 4.2 Final Reporter: Jean ANDRE We have one page that contains two forms. The first form contain a menus bar (ajax switchType) while the second contains a tabPanel (also in ajax switchType). When a user select a menu, we select the corresponding tab that contains a submit button. Once the tab is selected, the submit button does not work. We have to click twice for submitting. 1) If we move the menu bar inside the second forms, it is working. 2) If we set the menu bar in client switchType, selecting the menu doesn't do anything. 3) If we set the menu bar in server switchType it's working. As the rendering is well executed, the submit button should works but is not whatever we set as render="@all, or any valid id". We have prepared a small application that demonstrates the case. This is a simple but realistic application. Edit the index.xhtml to play with the menu. Let us know if we doing something wrong. -- 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

12 years, 9 months

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

12 years, 9 months

6
14
0 / 0

[JBoss JIRA] (RF-12104) BeanValidator: label not handled using MessageFactory

by Markus Staab (JIRA)

Markus Staab created RF-12104: --------------------------------- Summary: BeanValidator: label not handled using MessageFactory Key: RF-12104 URL: https://issues.jboss.org/browse/RF-12104 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.3.3.Final Environment: Liferay 5.2.4, Portlet 2.0, JSF 1.2 Reporter: Markus Staab The BeanValidator, in contrast to most JSF validators e.g. LongRangeValidator, does not use the MessageFactory to handle validation error message. see LongRangeValidators' validate-method: {code} .... throw new ValidatorException(MessageFactory.getMessage (context, NOT_IN_RANGE_MESSAGE_ID, stringValue(component, minimum, context), stringValue(component, maximum, context), MessageFactory.getLabel(context, component))); ... {code} Therefore error-message of a BeanValidator will neither prepand the String which is provided from the components' label-attribute nor the components' client id. see BeanValidator's validate & extractMessages-method {code} .... private Collection<String> extractMessages(Set<ConstraintViolation<Object>> violations) { Collection<String> messages = null; if (null != violations && violations.size() > 0) { messages = new ArrayList<String>(violations.size()); for (ConstraintViolation<? extends Object> constraintViolation : violations) { messages.add(constraintViolation.getMessage()); } } return messages; } ... {code} All error messages are taken 1:1 from the BeanValidator. While e.g. the error-message of LongRangeValidtor looks like "Startdate: Value is greater than allowable maximum of ''{0}''." the error looks like "Value is greater than allowable maximum of ''{0}''.". -- 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

12 years, 9 months

2
2
0 / 0

[JBoss JIRA] (RF-12111) Threading/performance issues with DocumentBuilder/ResponseWriterContentHandler

by Nicholas Oxhøj (JIRA)

Nicholas Oxhøj created RF-12111: ----------------------------------- Summary: Threading/performance issues with DocumentBuilder/ResponseWriterContentHandler Key: RF-12111 URL: https://issues.jboss.org/browse/RF-12111 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.3.3.Final Reporter: Nicholas Oxhøj Hi We have recently encountered some threading/performance issues with the way DocumentBuilder is used in ResponseWriterContentHandler in RichFaces 3.3.3. Upon investigation, we discovered that this issue was apparently already reported in an "RF-10035 DocumentBuilder performance issue" and fixed in RichFaces 3.3.1.SP3 on Jan. 31, 2011. See https://issues.jboss.org/browse/JBPAPP-6166 The problem is that these bug fixes, were apparently NOT carried forward to the later branches (3.3.2 and 3.3.3). Was this just forgotten or is there a specific reason why these ServicePack fixes were left out? Regards, Nicholas Weise Oxhøj -- 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

12 years, 9 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues March 2012