May 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12236) showcase - rich:extendedDataTable - re-sizing columns breaks horizontal scrolling

by Juraj Huska (JIRA)

Juraj Huska created RF-12236: -------------------------------- Summary: showcase - rich:extendedDataTable - re-sizing columns breaks horizontal scrolling Key: RF-12236 URL: https://issues.jboss.org/browse/RF-12236 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables, showcase Affects Versions: 4.2.2.Final Environment: richfaces showcase app container: JBoss AS 7.1.1.Final browsers: Chrome, Firefox Reporter: Juraj Huska Re-sizing columns on rich:extendedDataTable breaks horizontal scrolling. -- 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

7
30
0 / 0

[JBoss JIRA] (RF-12255) kitchensink archetype - error message from server side validation not rendered correctly

by Juraj Huska (JIRA)

Juraj Huska created RF-12255: -------------------------------- Summary: kitchensink archetype - error message from server side validation not rendered correctly Key: RF-12255 URL: https://issues.jboss.org/browse/RF-12255 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: archetype, component-validators Affects Versions: 4.2.2.Final Environment: project generated from kitchensink archetype Reporter: Juraj Huska Priority: Minor Validation error from server side validation is not rendered correctly, the image with red cross is overlapped with the text part. Please take a look at the attached screenshot. -- 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
12
0 / 0

[JBoss JIRA] (RF-12252) kitchensink archetype - creating already registered user throws server side error - it should be caught and user should be noticed

by Juraj Huska (JIRA)

Juraj Huska created RF-12252: -------------------------------- Summary: kitchensink archetype - creating already registered user throws server side error - it should be caught and user should be noticed Key: RF-12252 URL: https://issues.jboss.org/browse/RF-12252 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: archetype Environment: project generated from kitchensink archetype Reporter: Juraj Huska Priority: Minor When creating an already registered user there is server side error, because of the not unique email: {code} javax.ejb.EJBException: javax.persistence.PersistenceException: org.hibernate.exception.ConstraintViolationException: Unique index or primary key violation: "CONSTRAINT_INDEX_8 ON PUBLIC.MEMBER(EMAIL)"; SQL statement: {code} The is also no error message rendered to the user. There should be some notice that such a user have been already registered. -- 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

4
17
0 / 0

[JBoss JIRA] (RF-12254) kitchensink archetype - accessing wrong facelet is held in session and consequently accessing a correct one causes HTTP Status 500

by Juraj Huska (JIRA)

Juraj Huska created RF-12254: -------------------------------- Summary: kitchensink archetype - accessing wrong facelet is held in session and consequently accessing a correct one causes HTTP Status 500 Key: RF-12254 URL: https://issues.jboss.org/browse/RF-12254 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: archetype, mobile Affects Versions: 4.2.2.Final Environment: project generated from kitchensink archetype Reporter: Juraj Huska Priority: Minor When accessing wrong facelet on mobile device and consequently the right application context, then the HTTP Status 500 is returned with error message, which can be viewed in the attached screenshot. It is caused because the {{PageBean}} hold the wrong part of the URL in the session, {code} public void setLocation(String location) { this.location = location; this.page = String.format("/mobile/%s.xhtml", location); } {code} Note that I have tried to change the scope of the PageBean to RequestScoped, but then the list with members what not updated with the new created ones. -- 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
13
0 / 0

[JBoss JIRA] (RF-12076) Kitchensink archetype - back button does not back to the correct page state

by Juraj Huska (JIRA)

Juraj Huska created RF-12076: -------------------------------- Summary: Kitchensink archetype - back button does not back to the correct page state Key: RF-12076 URL: https://issues.jboss.org/browse/RF-12076 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: archetype Affects Versions: 4.2.0.Final Reporter: Juraj Huska Priority: Minor When clicking on the url of the freshly created new member (like /rest/members/0) and backing back from the xml viewing, results in removed freshly added member. After refresh, or AJAX update (clicking on accordion panel), the table is with all members again. This happens only for freshly added members. -- 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
15
0 / 0

[JBoss JIRA] (RF-12281) rich:tree is iterated multiple times when item is selected

by Alex Vb (JIRA)

Alex Vb created RF-12281: ---------------------------- Summary: rich:tree is iterated multiple times when item is selected Key: RF-12281 URL: https://issues.jboss.org/browse/RF-12281 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tree Affects Versions: 4.2.2.Final Reporter: Alex Vb I have a decently sized tree and I'm using the selectionChangeListener in combination with toggleType="client" selectionType="ajax" render="node" to trigger a selection event on the server. The panelGroup "node" is re-rendered afterwards but it takes 1-2 seconds for each request. After enabling some debug logging I noticed that the entire tree is iterated 4 times for each request. Note a small test-tree exhibiting the same behavior: 2012-05-22 08:39:29.287 DEBUG CustomPhaseListener - Before phase: APPLY_REQUEST_VALUES 2 2012-05-22 08:39:29.287 DEBUG TreeNodeBase - getChildrenKeysIterator(0) 2012-05-22 08:39:29.287 DEBUG TreeNodeBase - getChild(1) 2012-05-22 08:39:29.287 DEBUG TreeNodeBase - getChildrenKeysIterator(1) 2012-05-22 08:39:29.287 DEBUG TreeNodeBase - getChild(2) 2012-05-22 08:39:29.287 DEBUG TreeNodeBase - getChild(2) 2012-05-22 08:39:29.287 DEBUG TreeNodeBase - getChild(2) 2012-05-22 08:39:29.287 DEBUG Bean - selectionChanged() 2012-05-22 08:39:29.287 DEBUG CustomPhaseListener - After phase: APPLY_REQUEST_VALUES 2 2012-05-22 08:39:29.287 DEBUG CustomPhaseListener - Before phase: PROCESS_VALIDATIONS 3 2012-05-22 08:39:29.287 DEBUG TreeNodeBase - getChildrenKeysIterator(0) 2012-05-22 08:39:29.287 DEBUG TreeNodeBase - getChild(1) 2012-05-22 08:39:29.287 DEBUG TreeNodeBase - getChildrenKeysIterator(1) 2012-05-22 08:39:29.287 DEBUG TreeNodeBase - getChild(2) 2012-05-22 08:39:29.302 DEBUG TreeNodeBase - getChild(2) 2012-05-22 08:39:29.302 DEBUG CustomPhaseListener - After phase: PROCESS_VALIDATIONS 3 2012-05-22 08:39:29.302 DEBUG CustomPhaseListener - Before phase: UPDATE_MODEL_VALUES 4 2012-05-22 08:39:29.302 DEBUG TreeNodeBase - getChildrenKeysIterator(0) 2012-05-22 08:39:29.302 DEBUG TreeNodeBase - getChild(1) 2012-05-22 08:39:29.302 DEBUG TreeNodeBase - getChildrenKeysIterator(1) 2012-05-22 08:39:29.302 DEBUG TreeNodeBase - getChild(2) 2012-05-22 08:39:29.302 DEBUG TreeNodeBase - getChild(2) 2012-05-22 08:39:29.302 DEBUG CustomPhaseListener - After phase: UPDATE_MODEL_VALUES 4 2012-05-22 08:39:29.302 DEBUG CustomPhaseListener - Before phase: INVOKE_APPLICATION 5 2012-05-22 08:39:29.302 DEBUG CustomPhaseListener - After phase: INVOKE_APPLICATION 5 2012-05-22 08:39:29.302 DEBUG CustomPhaseListener - Before phase: RENDER_RESPONSE 6 2012-05-22 08:39:29.302 DEBUG TreeNodeBase - getChild(2) 2012-05-22 08:39:29.318 DEBUG TreeNodeBase - getChildrenKeysIterator(0) 2012-05-22 08:39:29.318 DEBUG TreeNodeBase - getChild(1) 2012-05-22 08:39:29.318 DEBUG TreeNodeBase - getChildrenKeysIterator(1) 2012-05-22 08:39:29.318 DEBUG TreeNodeBase - getChild(2) 2012-05-22 08:39:29.318 DEBUG TreeNodeBase - getChild(2) 2012-05-22 08:39:29.318 DEBUG CustomPhaseListener - After phase: RENDER_RESPONSE 6 On the rather large tree each iteration takes 300-500 ms which explains the slow behavior. I have played around with every setting I could find, if selectionType is set to "client" the tree is iterated only once (during the render response phase) but the selection event does not seem to be triggered. If toggleType is set to ajax, only the "expanded" parts of the tree are iterated. I have no idea why the iteration is necessary for all these phases but I "fixed" it in my implementation by recompiling the org.richfaces.component.TreeRange class with an updated method: public boolean shouldIterateChildren() { if (tree.isLeaf()) return false; else { char separatorChar = UINamingContainer.getSeparatorChar(FacesContext.getCurrentInstance()); String clientId = tree.getClientId(); boolean render = false; for (String idToRender : FacesContext.getCurrentInstance().getPartialViewContext().getRenderIds()) { // render the tree if you explicitly mention either the client id (e.g. "menuForm:tree") or the parent component client id (e.g. "menuForm") // note that when clicking on an object in the tree, the following render target is requested: menuForm:tree@selection if (clientId.equals(idToRender) || clientId.matches(idToRender + separatorChar + ".*")) { render = true; break; } } // always render if it's not a postback return render || !FacesContext.getCurrentInstance().isPostback(); } } -- 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
8
0 / 0

[JBoss JIRA] Created: (RF-8586) UIDataAdaptor: keepSaved attribute

by Nick Belaevski (JIRA)

UIDataAdaptor: keepSaved attribute ---------------------------------- Key: RF-8586 URL: https://jira.jboss.org/jira/browse/RF-8586 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component Affects Versions: 4.0.0.ALPHA2 Reporter: Nick Belaevski Assignee: Nick Belaevski Fix For: 4.0.0.ALPHA2 Boolean attribute that defines whether this iteration component will reset saved children's state before rendering. By default state is reset if there are no faces messages with severity error or higher. -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] (RF-11992) cache bug in portlet

by Ivan Ravin (JIRA)

Ivan Ravin created RF-11992: ------------------------------- Summary: cache bug in portlet Key: RF-11992 URL: https://issues.jboss.org/browse/RF-11992 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.0.CR1, 3.3.3.Final Environment: jboss portal 2.7.2; Gatein portal Reporter: Ivan Ravin On Jboss and Gatein portal richfaces cant be cached when user is logged in. Bug is found for richfaces 3.3.3 but i think can be reproduced for 4.x because org.richfaces.resource.AbstractCacheableResource has similar code. The steps for reproduce bug are: download portlet bridge 2.2 archive deploy richFacesPortlet.war from portlet bridge archive (i used jboss portal 2.7.2 bundle and GateIn-3.1.0-FINAL-jbossas) look at network activity (i did with firefox + firebug, the same result on any other browser). Just open page with richfaces portlet. When user is not logged in, all richfaces resources are caching well, and this is headers returned by server: |Cache-Control |max-age=86400| |Content-Type |text/javascript| |Date |Thu, 26 Jan 2012 17:57:39 GMT| |Expires |27 Jan 2012 17:57:39 GMT| |Last-Modified |26 Jan 2012 17:42:17 GMT| |Server |Apache-Coyote/1.1| |X-Powered-By |Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0| But when user is logged in all richfaces stuff come from network every time (more than 1.3 mb). This is headers returned by portal 2.7.2 when user logged in: |Cache-Control |{color:red}no-cache,{color} max-age=86400| |Content-Type |text/javascript| |Date |Thu, 26 Jan 2012 18:26:49 GMT| |Expires |{color:red}Thu, 01 Jan 1970 03:00:00 MSK,{color} 27 Jan 2012 18:26:49 GMT| |Last-Modified |26 Jan 2012 18:05:56 GMT| |{color:red}Pragma{color} |{color:red}No-cache{color}| |Server |Apache-Coyote/1.1| |Transfer-Encoding |chunked| |X-Powered-By |Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0| The same problem with GateIn-3.1.0-FINAL-jbossas bundle, but now only one wrong header: |Cache-Control |max-age=86400| |Content-Type |text/javascript;charset=UTF-8| |Date |Sat, 28 Jan 2012 08:54:14 GMT| |Expires |29 Jan 2012 08:54:14 GMT| |Last-Modified |28 Jan 2012 08:51:11 GMT| |{color:red}Pragma{color} |{color:red}No-cache{color}| |Server |Apache-Coyote/1.1| |Transfer-Encoding |chunked| |X-Powered-By |Servlet 2.5; JBoss-5.0/JBossWeb-2.1| This header (Pragma) appears only when user is logged in, and again, all richfaces resources come through network. I did some debug and found that bridge create good headers, but there is some code in portal which put wrong values into real response before richfaces. I cant find this code in portal sources, so maybe it is JBoss AS problem, or third party component. Gatein portal overwrite 2 wrong headers with values provided by richfaces, but "pragma" header is absent in richfaces response, and this way in secured portlets richfaces generate too much unnesessary traffic. -- 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
32
0 / 0

[JBoss JIRA] (RF-11565) Mobile Showcase: multiple selections in rich:autocomplete doesn't work

by Jan Papousek (Created) (JIRA)

Mobile Showcase: multiple selections in rich:autocomplete doesn't work ---------------------------------------------------------------------- Key: RF-11565 URL: https://issues.jboss.org/browse/RF-11565 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: mobile, showcase Affects Versions: 4.1.0.Milestone3 Environment: iPhone 4 (Safari) Nexus (Android 2.3.6) Reporter: Jan Papousek The second a third autocomplete input in Showcase demo http://10.0.2.2:8080/showcase/#autocomplete:modes doesn't work properly: # type "Al" # select "Alabama" -> input field is containing "Alabama" # type ", P" # select "Pennsylvania" -> input field is containing "Pennsylvania, P" (it should contain "Alabama, Pennsylvania") The Safari developer's console doesn't display any error. -- 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

7
9
0 / 0

[JBoss JIRA] Created: (RF-6573) Editor: scripts are not loading when appended by AJAX

by Nick Belaevski (JIRA)

Editor: scripts are not loading when appended by AJAX ----------------------------------------------------- Key: RF-6573 URL: https://jira.jboss.org/jira/browse/RF-6573 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.1 Reporter: Nick Belaevski Assignee: Pavel Yaschenko Priority: Minor Fix For: Future -- 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, 1 month

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues May 2012