June 2010 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Commented: (RF-8697) a4j:ajax: for immediate behavior "bypassUpdates" has no action

by Damien Gouyette (JIRA)

[ https://jira.jboss.org/browse/RF-8697?page=com.atlassian.jira.plugin.syst... ] Damien Gouyette commented on RF-8697: ------------------------------------- I tried /examples/core-demo/tags/richfaces-core-demo-4.0.0.Alpha2/src/main/webapp/ajax.xhtml . Inside this page, there is a sample testing good working of byPassUpdates. And it's working well. Do you have more information about this problem ? > a4j:ajax: for immediate behavior "bypassUpdates" has no action > -------------------------------------------------------------- > > Key: RF-8697 > URL: https://jira.jboss.org/browse/RF-8697 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.0.0.Alpha2 > Reporter: Nick Belaevski > Assignee: Nick Belaevski > Fix For: 4.0.0.Milestone1 > > -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (RF-8767) Disable Maven-cdk-plugin for pom projects.

by Alexander Smirnov (JIRA)

Disable Maven-cdk-plugin for pom projects. ------------------------------------------ Key: RF-8767 URL: https://jira.jboss.org/browse/RF-8767 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: CDK Reporter: Alexander Smirnov Assignee: Alexander Smirnov Fix For: 4.0.0.Milestone1 CDK plugin takes a lot of time and creates additional source folders even for non-component projects. Tasks: - do not run generator for project with 'pom' packaging. - create output folders on demand. Do not append empty source folders to maven. - bypass generation phase for empty model. -- 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

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (RF-3051) Demo site: Background image is not applied if page content is wider then browser window.

by Sergey Halipov (JIRA)

Demo site: Background image is not applied if page content is wider then browser window. ---------------------------------------------------------------------------------------- Key: RF-3051 URL: http://jira.jboss.com/jira/browse/RF-3051 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.5, 3.2.1 Environment: Firefox Reporter: Sergey Halipov Attachments: firefox.png -- 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

15 years, 9 months

4
9
0 / 0

[JBoss JIRA] Created: (RF-5733) extendedTable: Allow to be used without vertical scroller.

by Ilya Shaikovsky (JIRA)

extendedTable: Allow to be used without vertical scroller. ---------------------------------------------------------- Key: RF-5733 URL: https://jira.jboss.org/jira/browse/RF-5733 Project: RichFaces Issue Type: Feature Request Affects Versions: 3.3.0 Reporter: Ilya Shaikovsky Assignee: Nick Belaevski lets allow the table optionally to produce simplier markup analogous to dataTable one. Some forum guys wanna use extendedTable features but without this one. -- 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

15 years, 9 months

5
9
0 / 0

[JBoss JIRA] Created: (RF-8763) a4j:ajax is not added on page in JBoss

by Pavol Pitonak (JIRA)

a4j:ajax is not added on page in JBoss -------------------------------------- Key: RF-8763 URL: https://jira.jboss.org/browse/RF-8763 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 4.0.0.Alpha2 Environment: JBoss 6 snapshot (June 8, 2010), RichFaces 4.0.0.Alpha2 & 4.0.0-SNAPSHOT Reporter: Pavol Pitonak The following code doesn't work in JBoss 6 (snapshot from June 8) but works in Tomcat 6.0.26. It generates <input id="form:nameInput" type="text" name="form:nameInput" /> <h:form id="form"> <h:outputLabel value="Name:" for="nameInput" /> <h:inputText id="nameInput" value="#{richBean.name}"> <a4j:ajax event="keyup" execute="@form" render="output" /> </h:inputText> <h:panelGroup id="output"> <h:outputText value="Hello #{richBean.name}!" rendered="#{not empty richBean.name}" /> </h:panelGroup> </h:form> -- 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

15 years, 9 months

5
8
0 / 0

[JBoss JIRA] Created: (RF-8336) UIDataAdaptor: events broadcasting is happening with wrong client id

by Nick Belaevski (JIRA)

UIDataAdaptor: events broadcasting is happening with wrong client id -------------------------------------------------------------------- Key: RF-8336 URL: https://jira.jboss.org/jira/browse/RF-8336 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 3.3.2.SR1 Reporter: Nick Belaevski Assignee: Nick Belaevski Fix For: 4.0.0.BETA1 The following code: <rich:dataTable var="top" value="#{forum5Bean.data}" rowKeyVar="row"> <rich:column> <h:outputText value="#{top}" /> <a4j:commandButton value="Delete"> <a4j:actionparam value="#{row}" assignTo="#{forum5Bean.itemValue}" /> </a4j:commandButton> </rich:column> </rich:dataTable> doesn't work because parameter is submitted with name=clientId (i.e. including row number), but in the time of event broadcast, clientId of a4j:actionparam component doesn't include row index. -- 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

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (RF-8197) Optimize AjaxChildrenRenderer render component check algorithm

by Jan Ziegler (JIRA)

Optimize AjaxChildrenRenderer render component check algorithm -------------------------------------------------------------- Key: RF-8197 URL: https://jira.jboss.org/jira/browse/RF-8197 Project: RichFaces Issue Type: Patch Security Level: Public (Everyone can see) Affects Versions: 3.3.2.SR1 Environment: Myfaces 1.2.8, Facelets 1.1.15, Tomcat 6.0.20 Reporter: Jan Ziegler I just realized some possible "lifecycle processing overhead" when doing ajax actions: In render response phase each ajax component is checked for rendering by the method AjaxChildrenRenderer.encodeAjaxComponent(). That - what I could see - is the case when: # the component´s rendered-attribute is true # the component is ajaxRendered # the componentId is defined in the reRenderId-List This also reflects the order of checking, so the first thing to be done is check if the component´s rendered-attribute is true. But this might also lead to additional lifecycle processings when rendered-conditions are bound to managed beans by el expressions. To evaluate the rendered condition, request scoped managed beans must be created. to my opion this is suboptimal, like in my case the managed bean performs some (time intensive?) actions in its constructor or the rendered conditions relies on a list which must be fetched from the database - and this also happens even if the componentId is not in den reRenderId-List. So why not first evaluate if the componentId is in the reRenderId-List or the component is ajaxRendered and then (if one of this conditions is true) additionally check the rendered-condition? This might be accomplished with a small change AjaxChildrenRenderer.encodeAjaxComponent(): {code} public void encodeAjaxComponent(FacesContext context, UIComponent component, String currentPath, Set<String> ids, Set<String> renderedAreas) throws IOException { if (component.isRendered()) { // skip not-rendered components. boolean found = false; boolean limitToList = AjaxContext.getCurrentInstance(context).isLimitToList(); String elementId = component.getId(); String absoluteId = currentPath + elementId; if (!ids.isEmpty()) { // list for rendering may contains absolute id ( best ), // component Id or client ID // String clientId = element.getClientId(context); if (ids.contains(absoluteId) || ids.contains(elementId)) { if (log.isDebugEnabled()) { log.debug(Messages.getMessage( Messages.RENDER_AJAX_AREA_INFO, absoluteId)); } // renderChild(context, element); found = true; } } // if (!found && limitToList && component instanceof NamingContainer && noIdUnderPath(absoluteId + NamingContainer.SEPARATOR_CHAR, ids)) { return; } if (!found && !limitToList && component instanceof AjaxOutput) { if (((AjaxOutput) component).isAjaxRendered()) { // renderChild(context, element); found = true; } } if (!found) { if (component instanceof AjaxChildrenEncoder) { ((AjaxChildrenEncoder) component).encodeAjaxChild(context, currentPath, ids, renderedAreas); } else { // Special case - for control components, not produced // html code - such as message bundles loaders, // MyFaces aliases etc. we call encodeBegin/end methods // even if components not in rendered areas. boolean special = isSpecialElement(context, component); if (special) { component.encodeBegin(context); } encodeAjaxChildren(context, component, currentPath, ids, renderedAreas); if (special) { component.encodeEnd(context); } } } else { renderedAreas.add(component.getClientId(context)); renderChild(context, component); } } } {code} Patched version (the isRendered()-condition is moved the the last else-Block before the component will be rendered): public void encodeAjaxComponent(FacesContext context, UIComponent component, String currentPath, Set<String> ids, Set<String> renderedAreas) throws IOException { boolean found = false; boolean limitToList = AjaxContext.getCurrentInstance(context).isLimitToList(); String elementId = component.getId(); String absoluteId = currentPath + elementId; if (!ids.isEmpty()) { // list for rendering may contains absolute id ( best ), // component Id or client ID // String clientId = element.getClientId(context); if (ids.contains(absoluteId) || ids.contains(elementId)) { if (log.isDebugEnabled()) { log.debug(Messages.getMessage( Messages.RENDER_AJAX_AREA_INFO, absoluteId)); } // renderChild(context, element); found = true; } } // if (!found && limitToList && component instanceof NamingContainer && noIdUnderPath(absoluteId + NamingContainer.SEPARATOR_CHAR, ids)) { return; } if (!found && !limitToList && component instanceof AjaxOutput) { if (((AjaxOutput) component).isAjaxRendered()) { // renderChild(context, element); found = true; } } if (!found) { if (component instanceof AjaxChildrenEncoder) { ((AjaxChildrenEncoder) component).encodeAjaxChild(context, currentPath, ids, renderedAreas); } else { // Special case - for control components, not produced // html code - such as message bundles loaders, // MyFaces aliases etc. we call encodeBegin/end methods // even if components not in rendered areas. boolean special = isSpecialElement(context, component); if (special) { component.encodeBegin(context); } encodeAjaxChildren(context, component, currentPath, ids, renderedAreas); if (special) { component.encodeEnd(context); } } } else if (component.isRendered()) { // skip not-rendered components. renderedAreas.add(component.getClientId(context)); renderChild(context, component); } } {code} -- 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

15 years, 10 months

2
7
0 / 0

[JBoss JIRA] Updated: (RF-8701) dataScroller: add facets support for customizations

by Nick Belaevski (JIRA)

[ https://jira.jboss.org/browse/RF-8701?page=com.atlassian.jira.plugin.syst... ] Nick Belaevski updated RF-8701: ------------------------------- Fix Version/s: 4.0.0.Milestone2 (was: 4.0.0.Milestone1) > dataScroller: add facets support for customizations > --------------------------------------------------- > > Key: RF-8701 > URL: https://jira.jboss.org/browse/RF-8701 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.0.0.ALPHA1 > Reporter: Ilya Shaikovsky > Assignee: Nick Belaevski > Fix For: 4.0.0.Milestone2 > > > Important Note: I do not see how some block components could be inserted into datascroller currently. That could potentially add lot of confusion and usage problems in future - so we have to discuss markup again. Many guys using "pages" facet redefinition and place some block controls/div based markup there. > And, I prefer to sacrifice the "semantic" principles there again in order to avoid problems. -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (RF-8665) Dynamic resources handling improvements

by Nick Belaevski (JIRA)

[ https://jira.jboss.org/browse/RF-8665?page=com.atlassian.jira.plugin.syst... ] Nick Belaevski resolved RF-8665. -------------------------------- Resolution: Done > Dynamic resources handling improvements > --------------------------------------- > > Key: RF-8665 > URL: https://jira.jboss.org/browse/RF-8665 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.0.0.Alpha2 > Reporter: Nick Belaevski > Assignee: Nick Belaevski > Fix For: 4.0.0.Milestone1 > > > 1. Add @DynamicResource annotation as replacement for classpath marker file > 2. Resource data & version are encoded as query parameters, not requestPath part > 3. Need to review parameters passing mechanism (e.g. via injections) -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Reopened: (RF-8665) Dynamic resources handling improvements

by Nick Belaevski (JIRA)

[ https://jira.jboss.org/browse/RF-8665?page=com.atlassian.jira.plugin.syst... ] Nick Belaevski reopened RF-8665: -------------------------------- > Dynamic resources handling improvements > --------------------------------------- > > Key: RF-8665 > URL: https://jira.jboss.org/browse/RF-8665 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.0.0.Alpha2 > Reporter: Nick Belaevski > Assignee: Nick Belaevski > Fix For: 4.0.0.Milestone1 > > > 1. Add @DynamicResource annotation as replacement for classpath marker file > 2. Resource data & version are encoded as query parameters, not requestPath part > 3. Need to review parameters passing mechanism (e.g. via injections) -- 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

15 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues June 2010