March 2012 - richfaces-issues - Jboss List Archives

[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

12 years, 3 months

8
33
0 / 0

[JBoss JIRA] (RF-11711) a4j:queue - attributes onsubmit, oncomplete, onevent does not work

by Lukáš Fryč (Created) (JIRA)

a4j:queue - attributes onsubmit, oncomplete, onevent does not work ------------------------------------------------------------------ Key: RF-11711 URL: https://issues.jboss.org/browse/RF-11711 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 4.1.0.CR1 Reporter: Lukáš Fryč -- 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, 3 months

9
14
0 / 0

[JBoss JIRA] Created: (RF-10620) Remove or externalize maven-javascript-plugin 3rd party software from RichFaces

by Jay Balunas (JIRA)

Remove or externalize maven-javascript-plugin 3rd party software from RichFaces ------------------------------------------------------------------------------- Key: RF-10620 URL: https://issues.jboss.org/browse/RF-10620 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: cdk Affects Versions: 4.0.0.CR1 Reporter: Jay Balunas Assignee: Jay Balunas Priority: Critical Fix For: 4.Next See source and details at maven-javascript-plugin. For these external sources we need to: * Verify why we are building and using these. ** Does not seem to be used in our source at all * Determine how to either only depend on external sources, or pull these out into their own project to be built separately. ** If a separate project with completely out of RichFaces, or in the /build/resources area. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

5
21
0 / 0

[JBoss JIRA] (RF-11453) Add autocomplete functinoality to the rich:select component

by Brian Leathem (Created) (JIRA)

Add autocomplete functinoality to the rich:select component ----------------------------------------------------------- Key: RF-11453 URL: https://issues.jboss.org/browse/RF-11453 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-selects Reporter: Brian Leathem Fix For: 4.2.0.Tracking Add an "autocompleteMethod" to rich:select -- 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, 3 months

4
7
0 / 0

[JBoss JIRA] Created: (RF-11365) onbeforedomupdate and oncomplete not working in Portlet environment

by Detlef Pleiss (JIRA)

onbeforedomupdate and oncomplete not working in Portlet environment ------------------------------------------------------------------- Key: RF-11365 URL: https://issues.jboss.org/browse/RF-11365 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.0.Final Reporter: Detlef Pleiss example page: <ui:composition 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" xmlns:rich="http://richfaces.org/rich"> <h:head/> <h:form> <h:panelGrid columns="2"> <h:outputText value="Text:" /> <h:inputText value="#{echoBean.text}" > <a4j:ajax event="keyup" onbeforesubmit="alert('beforesubmit')" onbegin="alert('begin')" onbeforedomupdate="alert('beforedomupdate')" oncomplete="alert('complete')" render="text,count" listener="#{echoBean.countListener}"/> </h:inputText> <h:outputText value="Echo:" /> <h:outputText id="text" value="#{echoBean.text}" /> <h:outputText value="Count:" /> <h:outputText id="count" value="#{echoBean.count}" /> </h:panelGrid> </h:form> </ui:composition> The alerts for onbeforedomupdate and oncomplete do not appear in a portal environment; they do in a non-portal web environment. The Ajax XML response in a non portal web environment contains the tag <extension id="org.richfaces.extension"> with the Javascript code from the named attributes. But, in a portal environment the id gets prefixed like i.e. <extension id="A3331org.richfaces.extension"> In fact Richfaces asks for this prefix in richfaces-core-api-4.0.0.Final-sources : org.richfaces.renderkit.util.CoreAjaxRendererUtils.java line 96 by calling facesContext.getExternalContext().encodeNamespace(EXTENSION_ID)) In a Servlet environment this leaves EXTENSION_ID = "org.richfaces.extension" unchanged, but in a Portlet environment its function is to "Return the specified name, after prefixing it with a namespace that ensures that it will be unique within the context of a particular page" (quoted from Javadoc). Only, the Javascript meant to react on the extension tag is hardcoded to react on the ID "org.richfaces.extension" only without any prefix: META-INF/resources/richfaces.js line 333 : var getExtensionResponseElement = function(responseXML) { return jQuery("partial-response extension#org\\.richfaces\\.extension", responseXML); }; So, in a Portlet environment the partial-response/extension is ignored due to the prefixed ID. A possible solution might be to have the Javascript accept any prefix in front of the ID, like: var getExtensionResponseElement = function(responseXML) { return jQuery("partial-response extension[id$='org\\.richfaces\\.extension']", responseXML); }; -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

5
7
0 / 0

[JBoss JIRA] Created: (RF-11359) using component control in rich:dataTable and rich:extendedDataTable doesn't work

by Brian Leathem (JIRA)

using component control in rich:dataTable and rich:extendedDataTable doesn't work --------------------------------------------------------------------------------- Key: RF-11359 URL: https://issues.jboss.org/browse/RF-11359 Project: RichFaces Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Leathem Problem with jQuery 1.6.2: sorting using component control in rich:dataTable and rich:extendedDataTable doesn't work, can be reproduced in Metamer on page http://localhost:8080/metamer/faces/components/richDataTable/sorting-usin... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
10
0 / 0

[JBoss JIRA] Created: (RF-11296) JSF command button: accesskey attribute ignored inside popup panel

by Pavol Pitonak (JIRA)

JSF command button: accesskey attribute ignored inside popup panel ------------------------------------------------------------------ Key: RF-11296 URL: https://issues.jboss.org/browse/RF-11296 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-output Affects Versions: 4.1.0.Milestone1 Environment: RichFaces 4.1.0-SNAPSHOT r.d0f9c11eb0dacc1444c0a3182b12567e28aef6bc Metamer 4.1.0-SNAPSHOT r.22616 Mojarra 2.1.2-FCS, Mojarra 2.0.4-b09 Apache Tomcat 6.0.32 OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux Chrome 13.0.782.112 @ Linux i686, Firefox 3.6 Reporter: Pavol Pitonak # deploy Metamer and open http://localhost:8080/metamer/faces/components/commandButton/simple.xhtml # set accesskey=x # verify that attribute is set on command button # select template "richPopupPanel" # verify that attribute is set on command button again result: h:commandButton inside rich:popupPanel does not have attribute accesskey set -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
3
0 / 0

[JBoss JIRA] (RF-11550) Tab panel: header alignment doesn't work in iteration components in Chrome

by Pavol Pitonak (Created) (JIRA)

Tab panel: header alignment doesn't work in iteration components in Chrome -------------------------------------------------------------------------- Key: RF-11550 URL: https://issues.jboss.org/browse/RF-11550 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.1.0.Milestone3 Environment: RichFaces 4.1.0-SNAPSHOT Metamer 4.1.0-SNAPSHOT r.22800 Mojarra 2.1.3-SNAPSHOT JBoss Web 7.0.1.Final OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux Chrome 14.0.835.202 @ Linux i686 Reporter: Pavol Pitonak # deploy Metamer # open in Chrome http://localhost:8080/metamer/faces/components/richTabPanel/simple.xhtml?... # set headerAlignment=right result: header is aligned to the left the bug can be reproduced in following templates: * rich:dataGrid * rich:dataTable * rich:collapsibleSubTable * h:dataTable -- 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, 3 months

4
4
0 / 0

[JBoss JIRA] (RF-11585) mediaOutput doesn't work in CDI @ConversationScoped

by Edilmar Alves (Created) (JIRA)

mediaOutput doesn't work in CDI @ConversationScoped --------------------------------------------------- Key: RF-11585 URL: https://issues.jboss.org/browse/RF-11585 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component Affects Versions: 4.0.0.Final Environment: NetBeans7.0.1 + GlassFish 3.1.1 + CDI 1.1 + JSF2.1 + RichFaces4.0.0-Final. Reporter: Edilmar Alves Priority: Critical When using a controller with @ConversationScoped (CDI scope), the following exception arises: GRAVE: org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.ConversationScoped -- 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, 3 months

5
7
0 / 0

[JBoss JIRA] Created: (RF-4308) rich:pickList: keep sort order of source list after add/remove operations

by Martin Höller (JIRA)

rich:pickList: keep sort order of source list after add/remove operations ------------------------------------------------------------------------- Key: RF-4308 URL: https://jira.jboss.org/jira/browse/RF-4308 Project: RichFaces Issue Type: Feature Request Reporter: Martin Höller When adding items from the source list to the target list and removing this items again, the original order of the source list is not preserved. This makes it hard to find items in a list that is longer than just a fest items. A good example is the second example on the livedemo at http://livedemo.exadel.com/richfaces-demo/richfaces/pickList.jsf. Add the first state (Alabama) and remove it. It can now be found at the very end of the otherwise alphabetical list of states. This can be rather unintuitive for a user. My suggestion is either remember the original sort order of the source list, or add some attribute that enables automatic sorting. -- 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, 3 months

4
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues March 2012