March 2009 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-2393) Tree nested inside node of an outer tree has strange behaviour on ajax submit when there are validation errors

by Mike Hanafey (JIRA)

Tree nested inside node of an outer tree has strange behaviour on ajax submit when there are validation errors -------------------------------------------------------------------------------------------------------------- Key: RF-2393 URL: http://jira.jboss.com/jira/browse/RF-2393 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.4 Environment: Glassfish v2, JSF RI 1.2 Reporter: Mike Hanafey Attachments: NestedTree.war I have situation where there is an outer tree whose nodes have an inner tree. Specifically, the outer tree is over DNA sequences, and each DNA sequence may have a tree of comments attached to it. Both the inner and outer trees have a couple of faces, one is used when a node is in display mode, and the other when it is in edit mode. If the inner tree is put into edit mode at a node (via an ajax request) and a validation error occurs on a second ajax request to submit the edits, the whole inner tree for that node disappears. It can be recovered by doing a browser redisplay. If there is no validation error, the edit works as expected Looking at the XmlHttpRequest response when there is a validation error shows that the response does not contain the expected tree nodes. When this same comment tree code (both the backing beans and the facelets views) is applied on an unnested tree this problem does not occur. A test war is attached (the war is big only because it includes the library dependencies -- the test code itself is small). To demonstrate, deploy the war and look at the top page. Click on the + next to "Comments" (this is the un-nested tree). Click "Ajax Save". Observe the "Value is required" messages. Enter something into the first textfield, and do the "Ajax Save". Now a custom validation message appears. Now for the first strangeness. Enter something in both the textfield and the textarea. The custom validation message appears on both inputs, but now the inputs just made are erased. When only one of these fields have data, the data entered in the other field is preserved, and I believe the clearing of input data is another error, but not the one in the title of this this issue. To see the main issue, open the tree labeled "Sequences". This has a comments tree just like the one above nested inside the sequence node. Click on the + next the "Comments" under "Sequences". Click on "Ajax Save". Now instead of seeing the "Value is required" error, the inner tree node collapses. Click on the "Submit" button, an reopen the "Sequences" tree to see that the inner tree is in fact still intact. Click on "Ajax Immediate". Now the tree does not collapse. The only difference is this button is immediate, so the validation steps are not done. Finally, clicking on "Plain Save" shows the expected validation errors (now the Sequence tree collapses after the submit so it must be manually opened, but I guess this is expected behavior because the open / close state is not maintained across the request). The problem where the inputs that fail validation are erased remains even with this non-ajax update mode). -- 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

16 years, 10 months

3
16
0 / 0

[JBoss JIRA] Created: (RF-5120) Unused files

by Svetlana mukhina (JIRA)

Unused files ------------- Key: RF-5120 URL: https://jira.jboss.org/jira/browse/RF-5120 Project: RichFaces Issue Type: Task Components: doc Affects Versions: 3.2.2 Reporter: Svetlana mukhina Assignee: Catherine Luts Priority: Minor Fix For: Future delete all files from docs that are not used (images, files for components that are not exists or were renamed, etc.) -- 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

16 years, 10 months

2
10
0 / 0

[JBoss JIRA] Created: (RF-5117) code samples format

by Svetlana mukhina (JIRA)

code samples format -------------------- Key: RF-5117 URL: https://jira.jboss.org/jira/browse/RF-5117 Project: RichFaces Issue Type: Task Components: doc Affects Versions: 3.2.2 Reporter: Svetlana mukhina Assignee: Catherine Luts Priority: Minor Fix For: Future check that all code samples are highlighted and are formated in the same way, no empty lines, no ".." instead of "..." ,and etc. -- 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

16 years, 10 months

4
19
0 / 0

[JBoss JIRA] Created: (RF-5380) dropSupport: "disableDefault" attribute doesn't work.

by Mikhail Vitenkov (JIRA)

dropSupport: "disableDefault" attribute doesn't work. ----------------------------------------------------- Key: RF-5380 URL: https://jira.jboss.org/jira/browse/RF-5380 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.0 Environment: IE6, IE7, FF 3.1.3, Safari 3.1, Opera 9.62(3.3.0.BETA3) Reporter: Mikhail Vitenkov Assignee: Nick Belaevski #1. Add dragSupport and dropSupport zones following way: <h:panelGrid columns="1" id="panel1"> <h:panelGroup id="column1"> <a4j:outputPanel> <rich:dragSupport dragType="dragType1"></rich:dragSupport> <h:outputText value="Drag it 1" /> </a4j:outputPanel> </h:panelGroup> </h:panelGrid> <h:panelGrid columns="1" id="panel3"> <h:panelGroup id="column3"> <a4j:outputPanel> <rich:dropSupport acceptedTypes="dragType1"></rich:dropSupport> <h:outputText value="Drop from 1" /> </a4j:outputPanel> </h:panelGroup> </h:panelGrid> #2. For dropSupport set action="main", where "main" is action navigation to the main page, defined in faces-config.xml #3. Set ondrop="window.open('http://www.jboss.org/','_blank','width=200,height=200');" #4. Set disableDefault="true". #5. Navigate to page and make drag'n'drop content from "panel1" panelGrid to "panel3" panelGrid.(acceptedTypes="dragType1") Actual behavior: www.jboss.org opens in new window, then "main" navigation action works. Try to append by hands "return false;" to the ondrop handler's content and repeat Step #5 - works fine: www.jboss.org opens in new window, current page remains. -- 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

16 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (RF-5945) Script expression for attributes

by Svetlana mukhina (JIRA)

Script expression for attributes --------------------------------- Key: RF-5945 URL: https://jira.jboss.org/jira/browse/RF-5945 Project: RichFaces Issue Type: Task Components: doc Affects Versions: 3.3.0 Reporter: Svetlana mukhina Assignee: Catherine Luts Fix For: 3.3.1-doc Add script expression for all attributes descriptions where it is required. the issue is related to http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201504#4201504 -- 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

16 years, 10 months

3
15
0 / 0

[JBoss JIRA] Created: (RF-6281) "header" and "footer" facets data cannot be exported to excel for rich dataTable, scrollableDataTable and extendedDataTable components.

by Mikhail Vitenkov (JIRA)

"header" and "footer" facets data cannot be exported to excel for rich dataTable, scrollableDataTable and extendedDataTable components. --------------------------------------------------------------------------------------------------------------------------------------- Key: RF-6281 URL: https://jira.jboss.org/jira/browse/RF-6281 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.0 Environment: IE6, IE7, FF 3.0.6, Safari 3.1, Opera 9.62, Chrome 1.0.154.43(3.3.0.GA, seam 2.0.2.GA) Reporter: Mikhail Vitenkov Assignee: Nick Belaevski #1. Put jboss-seam-excel.jar and jxl.jar in your project lib folder. #2. Configure web.xml following way: <servlet> <servlet-name>Document Store Servlet Excel</servlet-name> <servlet-class>org.jboss.seam.excel.DocumentStoreServlet</servlet-class> </servlet> <servlet-mapping> <servlet-name>Document Store Servlet Excel</servlet-name> <url-pattern>*.xls</url-pattern> </servlet-mapping> <context-param> <param-name>webAppRootKey</param-name> <param-value>seam-excel</param-value> </context-param> #3. Configure components.xml. Add following string: In taglib: xmlns:excel="http://jboss.com/products/seam/excel" <excel:document-store use-extensions="true"/> #4. Add following code on the page: <h:form id="theForm"> <rich:dataTable value="#{excel.dataModel}" var="dat" id="theDataTable"> <f:facet name="header"><h:outputText value="header"/></f:facet> <f:facet name="footer"><h:outputText value="footer"/></f:facet> <rich:column> <h:outputText value="#{dat}" /> </rich:column> </rich:dataTable> <h:commandLink value="Export" action="#{org.jboss.seam.excel.excelExporter.export('theForm:theDataTable')}" /> </h:form> #5. Navigate to the page, click "Export" and verify facets data presence in excel. Actual behavior: facets don't display in excel. The same situation occur with rich scrollableDataTable and extendedDataTable. But, when facets is placed inside <rich:column tag - data export works well. -- 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

16 years, 10 months

4
4
0 / 0

[JBoss JIRA] Created: (RF-5748) ExtendedDataTable inside tabPanel buzzes after rerender tabPanel.

by Alexander Dubovsky (JIRA)

ExtendedDataTable inside tabPanel buzzes after rerender tabPanel. ----------------------------------------------------------------- Key: RF-5748 URL: https://jira.jboss.org/jira/browse/RF-5748 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.0 Environment: 3.3.0.GA Reporter: Alexander Dubovsky Assignee: Nick Belaevski Attachments: extendedDataTable.jsp Source code see in attachment. # Open page and select any row Result: extendedDataTable's rerender is put in an infinite loop -- 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

16 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (RF-5734) <a4j:outputPanel> produces javax.servlet.ServletException: duplicate Id for a component form:j_id6

by Bjoern Sonntag (JIRA)

<a4j:outputPanel> produces javax.servlet.ServletException: duplicate Id for a component form:j_id6 -------------------------------------------------------------------------------------------------- Key: RF-5734 URL: https://jira.jboss.org/jira/browse/RF-5734 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.0, 3.2.2 Environment: java 1.6.11, Glassfish V2, Windows XP Prof Reporter: Bjoern Sonntag we've found one bug in the a4j:outputPanel - tag... szenario : In our project we have severals subprojects which have 2 webpages with simple navigation rule. Side A leads to side B and you can get from side B to side A, but when we go from side B to side A we got an exception : javax.servlet.ServletException: duplicate Id for a component form:j_id6 We have following interesseting code in our jsps <a4j:outputPanel layout="none" id="mainContentPanel"> <!-- here are some widgets, like outputLabel, inputText, rich:calendar etc. --!> </a4j:outputPanel> which we use like a tag to render several widgets, or not. But when we replace the <a4j:outputPanel> with a <rich:panel> and navigate from side B to side A its works fine but our markup looks like a slap with a golf club. This behaviour is repeatable ! So we think there is a bug in the <a4j:outputPanel> or the Richfaces Framework have a problem with that. When you google for ""duplicate id" Richfaces a4j" you can see many many posting, that have <a4j:outputPanel> as common ground. with best regards Bjoern -- 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

16 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (RF-5645) ComboBox: request is sent twice if use onblur ajaxsupport.

by Alexander Dubovsky (JIRA)

ComboBox: request is sent twice if use onblur ajaxsupport. ---------------------------------------------------------- Key: RF-5645 URL: https://jira.jboss.org/jira/browse/RF-5645 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.0 Environment: 3.3.0.CR3 Reporter: Alexander Dubovsky Assignee: Nick Belaevski Source: <h:panelGrid columns="4"> <h:outputText value="Model:" /> <rich:comboBox id="model" value="#{comboBox.modelSelected}"> <a4j:support event="onblur" reRender="snBox" /> <f:selectItems value="#{comboBox.selectItemListModel}" /> </rich:comboBox> <h:outputText value="Serialnumber:" /> <rich:comboBox id="snBox" value="#{comboBox.snSelected}"> <a4j:support event="onblur" reRender="result" /> <f:selectItems id="sn" value="#{comboBox.selectItemListSn}" /> </rich:comboBox> <h:inputText id="input" /> <h:commandButton value="Add a new SN" /> </h:panelGrid> The 1th request is sent after selection of item in combo (using mouse), the 2th after onblur event. -- 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

16 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (RF-5624) fileUpload: transfer error take place in flash mode under https.

by Mikhail Vitenkov (JIRA)

fileUpload: transfer error take place in flash mode under https. ---------------------------------------------------------------- Key: RF-5624 URL: https://jira.jboss.org/jira/browse/RF-5624 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.0 Environment: IE6, IE7, FF 3.1.3, Safari 3.1, Opera 9.62(3.3.0.CR3) Reporter: Mikhail Vitenkov Assignee: Nick Belaevski Priority: Critical #1. Deploy richfaces-demo under tomcat 6.0.16 #2. Modify server.xml(define ssl connector): <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS"/> #3. Run tomcat. #4. Navigate to Rich Input->File Upload page. #5. Check "Turn using flash on:" checkbox. #6. Try to upload file with valid size(less than 1000000 bytes). Actual behavior: Trnasfer error occured. See screenshot. -- 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

16 years, 10 months

4
9
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues March 2009