April 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-11776) rich:extendedDataTable columnsOrder attribute is not working

by Dmitry Volkov (Created) (JIRA)

rich:extendedDataTable columnsOrder attribute is not working ------------------------------------------------------------ Key: RF-11776 URL: https://issues.jboss.org/browse/RF-11776 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.0.0.Final Environment: Websphere AS 8, MyFaces Reporter: Dmitry Volkov I am not sure if columnsOrder attribute may be used or it is deprecated, but there is definitely an error in SortingFilteringRowsRenderer.updateAttribute method. This line: {code:java} component.getAttributes().put(attribute, null); {code} always throws NullPointerException which is shallowed by try .. finally in UIDataAdaptor.visitTree method. -- 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

11 years, 12 months

5
13
0 / 0

[JBoss JIRA] (RF-12175) jquery.atmosphere.js - implement/adapt connection error handling code

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12175: ------------------------------- Summary: jquery.atmosphere.js - implement/adapt connection error handling code Key: RF-12175 URL: https://issues.jboss.org/browse/RF-12175 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 4.2.0.Final Reporter: Lukáš Fryč We have discussed implementing and donating error handling code to the Atmosphere/jQuery integration. The upstream issue: https://github.com/Atmosphere/atmosphere/issues/285 Discussion: http://groups.google.com/group/atmosphere-framework/browse_thread/thread/... -- 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

11 years, 12 months

2
7
0 / 0

[JBoss JIRA] (RF-12189) Risk of duplicate ID on Tab header with facet ?

by Jean ANDRE (JIRA)

Jean ANDRE created RF-12189: ------------------------------- Summary: Risk of duplicate ID on Tab header with facet ? Key: RF-12189 URL: https://issues.jboss.org/browse/RF-12189 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.0.Final Environment: GlasshFish 3.1.2 - JSF Mojorra 2.1.7 - Spring 3.0.6 Final - CDI Annotation- Firefox 10 - Windows 7 (6.1 sp1) Reporter: Jean ANDRE Attachments: Duplicate_ID_html_output.txt Please, evaluate the risk of duplicate ID. We have check the HTML ouptup with w3c validator and we got following error message: Line 81, Column 19: ID "desktopForm:TAB_ITEM-02-2-tabTitle" already defined <span id="desktopForm:TAB_ITEM-02-2-tabTitle" title="Liste # (2)">Liste Line 79, Column 19: ID "desktopForm:TAB_ITEM-02-2-tabTitle" first defined here <span id="desktopForm:TAB_ITEM-02-2-tabTitle" title="Liste # (2)">Liste... Line 82, Column 18: ID "desktopForm:TAB_ITEM-02-2-closeTabButton" already defined <img id="desktopForm:TAB_ITEM-02-2-closeTabButton" src="/NestedWeb/imag... Line 80, Column 18: ID "desktopForm:TAB_ITEM-02-2-closeTabButton" first defined here <img id="desktopForm:TAB_ITEM-02-2-closeTabButton" src="/NestedWeb/imag... For the following dynamic tab fragment. {code} <rich:tab id="#{tab.id}" onenter="enterTab('#{tab.id}');" headerClass="tab-header">    <f:facet name="header">  <h:outputText id="#{tab.id}-tabTitle" value="#{desktopController.getTabHeader(tab.id)}" title="#{desktopController.getTabHeader(tab.id)}" />  <h:graphicImage id="#{tab.id}-closeTabButton" value="/images/closeButton.png" styleClass="closeButton" onclick="closeTab('#{tab.id}');stopPropagation(event);" alt="" /> </f:facet> {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

11 years, 12 months

2
6
0 / 0

[JBoss JIRA] (RF-12212) Accordion - Javascript error - "this.getTogglePanel() is undefined" with ui:repeat

by Jean ANDRE (JIRA)

Jean ANDRE created RF-12212: ------------------------------- Summary: Accordion - Javascript error - "this.getTogglePanel() is undefined" with ui:repeat Key: RF-12212 URL: https://issues.jboss.org/browse/RF-12212 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Environment: WAS/RAD - Firefox 12 - JSF 2.1.7 - commons-lang-2.4 - commons-logging-1.1.1 - cssparser-0.9.6 - guava-11.0.1 - hibernate-validator-4.2.0.Final - junit-4.10 - log4j-1.2.16 - org.springframework 3.0.6 - sac-1.3 Reporter: Jean ANDRE Fix For: 4.2.1.Final, 4.2.0.Final When we use accordion inside an ui:repeat we got a javascript exception - The accordion does not work at all. Error is : togglePanelItem.js.jsf?ln=org.richfaces (ligne 43) {code} this.getTogglePanel() is undefined [Stopper sur une erreur] >>>>>>> this.getTogglePanel().getItems()[this.index] = this; this.disabled = this.options.disabled || false; this.index = options["index"]; this.getTogglePanel().getItems()[this.index] = this; this.__addUserEventHandler("enter"); {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

11 years, 12 months

3
8
0 / 0

[JBoss JIRA] Created: (RF-8125) Development: built-in sorting/filtering

by Anton Belevich (JIRA)

Development: built-in sorting/filtering --------------------------------------- Key: RF-8125 URL: https://jira.jboss.org/jira/browse/RF-8125 Project: RichFaces Issue Type: Sub-task Reporter: Anton Belevich Assignee: Anton Belevich Fix For: 4.0.0.ALPHA2 -- 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

11 years, 12 months

10
25
0 / 0

[JBoss JIRA] (RF-12160) rich:validator does not validate on the client side the @Pattern constraint

by Juraj Huska (JIRA)

Juraj Huska created RF-12160: -------------------------------- Summary: rich:validator does not validate on the client side the @Pattern constraint Key: RF-12160 URL: https://issues.jboss.org/browse/RF-12160 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-validators Affects Versions: 4.2.1.Final Environment: application: generated project from richfaces-kitchensink-archetype 4.2.1-SNAPSHOT browser: Chrome, Firefox Reporter: Juraj Huska When trying to validate input which has annotation based constraint @Pattern, validation for this constraint is triggered only after the submitting of the form. The other constraints (@NotNull, @Size) are triggered as expected, after the BLUR event fired on that input. The issue is noticeable on the project generated by the kitchensink archetype with RichFaces 4.2.1-SNAPSHOT libraries. The facelet for the input validation with pattern annotation-based constraints looks like: {code:xml} <h:panelGrid columns="3" columnClasses="titleCell"> <h:outputLabel for="name" value="Name:"/> <h:inputText id="name" value="#{cc.attrs.member.name}"> <rich:validator/> </h:inputText> <rich:message for="name" errorClass="invalid"/> </h:panelGrid> {code} The model entity field which is validated in the above mentioned input: {code} @NotNull @Size(min = 1, max = 25) @Pattern(regexp = "[A-Za-z ]*", message = "must contain only letters and spaces") private String name; {code} Note that I have tried to reproduce this issue on metamer and I was not successful. -- 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

11 years, 12 months

3
22
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

11 years, 12 months

3
15
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

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

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

7
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues April 2012