August 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-11584) Un-ignore TestCaptureEL and ValueExpressionAnalayserTest tests

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

Un-ignore TestCaptureEL and ValueExpressionAnalayserTest tests -------------------------------------------------------------- Key: RF-11584 URL: https://issues.jboss.org/browse/RF-11584 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: tests - unit Affects Versions: 4.1.0.Milestone4 Reporter: Lukáš Fryč Priority: Critical Fix For: 4.1.0.CR1 When resolving RF-11544, it was necessary to ignore following tests in components module, because of changes in jsf-test to support org.jboss.spec.javax.faces:jboss-jsf-api_2.1_spec * validator/ui/src/test/java/org/richfaces/el/ValueExpressionAnalayserTest.java * validator/ui/src/test/java/org/richfaces/el/TestCaptureEL.java -- 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, 1 month

5
10
0 / 0

[JBoss JIRA] (RF-12257) CDK: generating listener tags

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12257: ------------------------------- Summary: CDK: generating listener tags Key: RF-12257 URL: https://issues.jboss.org/browse/RF-12257 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: cdk Affects Versions: 4.2.0.Final Reporter: Bernard Labno -- 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, 1 month

3
15
0 / 0

[JBoss JIRA] (RF-12309) CDK: naming conventions to avoid necessity write all the FQNs of classes in Renderer template and Component stub

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12309: ------------------------------- Summary: CDK: naming conventions to avoid necessity write all the FQNs of classes in Renderer template and Component stub Key: RF-12309 URL: https://issues.jboss.org/browse/RF-12309 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: cdk Affects Versions: 4.2.0.Final Reporter: Lukáš Fryč There are lot of bindings which needs to be manually hard-coded in order to make the component work: Look at sample of the calendar component: 1. [Renderer template|https://github.com/richfaces/components/blob/4.2.2.20120513-Fina...] 2. [Component interface|https://github.com/richfaces/components/blob/4.2.2.20120513-Fin...] ---- What could follow naming conventions? 1. *Renderer template* * {{<class>}} - use the package where the template resides in: {{calendar.template.xml}} -> {{CalendarRenderer}} * {{<superclass}} - use the {{<class> + Base}}: {{CalendarRenderer}} -> {{CalendarRendererBase}}, if not exists, use {{org.richfaces.renderkit.RendererBase}} 2. *component* {{org.richfaces.component.AbstractCalendar}} * component-type: {{org.richfaces.Calendar}} * component-family: {{org.richfaces.Calendar}} * generated class: {{org.richfaces.component.UICalendar}} * renderer: {{org.richfaces.CalendarRenderer}} * tag: {{@Tag(name = "calendar", handler = "org.richfaces.view.facelets.CalendarHandler")}} Some definitions what need to be configured per component library: e.g. prefix for component type/family/renderer, etc. Only classes which violates conventions would be necessary to configure specifically. -- 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, 1 month

2
8
0 / 0

[JBoss JIRA] (RF-12296) Improve CDK c:forEach typing

by Paul Dijou (JIRA)

Paul Dijou created RF-12296: ------------------------------- Summary: Improve CDK c:forEach typing Key: RF-12296 URL: https://issues.jboss.org/browse/RF-12296 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: cdk Affects Versions: 4.2.2.Final Environment: All Reporter: Paul Dijou As we can see on [this comment|https://issues.jboss.org/browse/RF-10037?focusedCommentId=1269671...], you currently need to assign a list/array to a var before using it inside a {{<c:forEach>}} or the CDK doesn't know its correct type. As suggested by Lukas, I agree to add a {{cdk:itemType}} (or {{cdk:type}} like in the {{<cdk:object>}} tag) to specify manually the type of the object inside the iteration. If this attribute is present in the {{<c:forEach>}}, then the CDK use it to cast the object, otherwise it does the same as currently, no regression. In addition, for Enum, I would also try to use the initial import : {code:xml} <cdk:import package="org.richfaces.component" names="MyEnum" /> {code} In order to know the type of each Enum and then be able to correctly cast the following code : {code:xml} <cc:implementation> <c:forEach items="#{MyEnum.values()}" var="item"> #{item} </c:forEach> </cc:implementation> {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, 1 month

3
10
0 / 0

[JBoss JIRA] (RF-12326) NPE if a cdk:fragment use another one before it has be defined

by Paul Dijou (JIRA)

12 years, 1 month

3
8
0 / 0

[JBoss JIRA] (RF-12308) CDK: format the generated sources according to JBoss community formatter

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12308: ------------------------------- Summary: CDK: format the generated sources according to JBoss community formatter Key: RF-12308 URL: https://issues.jboss.org/browse/RF-12308 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: cdk Affects Versions: 4.2.0.Final Reporter: Lukáš Fryč Right now, sources generated by CDK are quite unreadable, since they do not follow any formatting rules. The formatting of the sources could be configurable, but by default JBoss community formatter should be followed. -- 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, 1 month

2
8
0 / 0

[JBoss JIRA] (RF-12339) CDK: generate methods from interfaces

by Paul Dijou (JIRA)

12 years, 1 month

3
7
0 / 0

[JBoss JIRA] Created: (RF-11355) commandButton doesn't work at first click in popupPanel

by Loïc TALON (JIRA)

commandButton doesn't work at first click in popupPanel ------------------------------------------------------- Key: RF-11355 URL: https://issues.jboss.org/browse/RF-11355 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 4.0.0.Final Environment: OS : Windows Seven Virtual server : easy php Server JEE : Glassfish 3.1 JSF 2.0 Reporter: Loïc TALON Hi, Sorry i don't speak very well english. I have a problem with a4j:commandButton in popupPanel. The first click doesn't work for action to commandButton but the first clic work. That doesn't work only in popupPanel. <a4j:commandButton value="Valid" action="#{beanManaged.valid}" id="validButton" render="modalPanelInfo, formCreate" /> I think the problem is javax.faces.viewstate, beacause before the first clic doesn't have input hidden with javax.faces.viewstate but after the first clic i have input hidden with javax.faces.viewstate. How to solve this problem ? THX -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

8
18
0 / 0

[JBoss JIRA] Created: (RF-10835) File upload: progress bar doesn't show progress

by Pavol Pitonak (JIRA)

File upload: progress bar doesn't show progress ----------------------------------------------- Key: RF-10835 URL: https://issues.jboss.org/browse/RF-10835 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.0.0.Final Environment: RichFaces 4.1.0-SNAPSHOT r.22320 Metamer 4.1.0-SNAPSHOT r.22342 Mojarra 2.1.0-FCS GlassFish Server Open Source Edition 3.1-SNAPSHOT OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux Chrome 10.0.648.204 @ Linux x86_64 Reporter: Pavol Pitonak Attachments: fileUpload3.png When a file is uploaded using rich:fileUpload, progress bar doesn't show progress (see screenshot from Chrome). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

6
9
0 / 0

[JBoss JIRA] (RF-12030) rich:dataScroller doesn't work if a rich:message exists inside of a collapsed rich:collapsiblePanel with switchType='ajax'

by Rene O (JIRA)

Rene O created RF-12030: --------------------------- Summary: rich:dataScroller doesn't work if a rich:message exists inside of a collapsed rich:collapsiblePanel with switchType='ajax' Key: RF-12030 URL: https://issues.jboss.org/browse/RF-12030 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.0.Final Environment: tomcat 7, richfaces-4.2.0.Final, myfaces-2.1.6 Reporter: Rene O rich:dataScroller doesn't work if a rich:message exists inside of a collapsed rich:collapsiblePanel with switchType='ajax' Steps to reproduce this issue: 1. use dataScroller to switch table-pages. you can see, that this works. 2. collaps collapsiblePanel 3. if collapsiblePanel is collapsed, the dataScroller doesn't react anymore. 4. if you use switchType='client' everything works correct {code:title=examplepage.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> <h:form id="myForm"> <rich:collapsiblePanel header="collapsPanel" id="collapsPanel" expanded="true" switchType="ajax"> <h:inputText id="test" value="" /> if rich:message doesn't exists, everything works... <rich:message id="testMessage" for="test"/> </rich:collapsiblePanel> <rich:dataTable id="tableA" var="item" value="#{model.tableList}" rows="5" style="width:350px;"> <f:facet name="header"> <h:outputText value="HeaderA" /> </f:facet> <rich:column id="colA" > <f:facet name="header"> ColA </f:facet> #{item.itemA} </rich:column> <f:facet name="footer"> <rich:dataScroller for="tableA" id="ds"/> </f:facet> </rich:dataTable> </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, 1 month

5
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues August 2012