February 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-9345) Richfaces HTTP Header Cache-Control settings, need 'public'

by igor regis (JIRA)

Richfaces HTTP Header Cache-Control settings, need 'public' ----------------------------------------------------------- Key: RF-9345 URL: https://jira.jboss.org/browse/RF-9345 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: performance Affects Versions: 3.3.3.Final, 3.3.3.CR1, 3.3.3.BETA1, 3.3.2.SR1, 3.3.2.GA, 3.3.2.CR1, 3.3.1 Environment: This issue affect any web browser according to w3c specification Reporter: igor regis If an application is running over https the web browser will only cache on disk, the Richfaces resources, if and only if, the Cache-control header (present on http header) has the value "public" on it. Otherwise the web browser will perform in memory cache, so when user restarts the browser the application will need to request all the resources again. For applications running on corporative network, manipulating sensitive information, it's mandatory the use of a secure connection through https protocol, and form better performance is necessary for Richfaces to provide it's resources with this "public" mark on cache-control tag. According the w3c specs (http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.1) Richfaces resources may be classified as public content with non individual information. Here (https://community.jboss.org/thread/150732?tstart=0) there is a discussion about this issue, as well as the point on Richfaces source code that need to be changed. -- 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

12 years, 9 months

5
7
0 / 0

[JBoss JIRA] Created: (RF-7955) ExtendedDataTable : Only first column correctly resize

by Nicolas Gaudin (JIRA)

ExtendedDataTable : Only first column correctly resize ------------------------------------------------------ Key: RF-7955 URL: https://jira.jboss.org/jira/browse/RF-7955 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.2.GA, 3.3.2.CR1 Environment: JSF RI 1.2_13 Facelets 1.1.14 (with .jspx files) Glassfish Jdk 1.6 Reporter: Nicolas Gaudin Fix For: 3.3.2.GA Hi, During my test to deliver, I discovered that the columns of all my EDTs would not resize correctly. More precisely, the first column resizes without any problem but the others resize WITHOUT resizing the header. I must mention that my EDT use value binding for dynamic column creation. My actions that generated this issue: - moved from jsp to facelets (with jspx extension) - upgraded to JSF 1.2_13 This affected 3.3.2.CR1, the version I was using. I then upgraded to 3.3.2.GA to check if this would fix but no luck Also, I thought that 3.3.2.GA would full scrolling support for EDT (horizontal mainly) Is that the case? Could you please confirm? May thanks in advance -- 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, 9 months

3
12
0 / 0

[JBoss JIRA] (RF-11645) Mobile Showcase and rich:orderingList

by Jan Papousek (Created) (JIRA)

Mobile Showcase and rich:orderingList ------------------------------------- Key: RF-11645 URL: https://issues.jboss.org/browse/RF-11645 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-selects, mobile, showcase Affects Versions: 4.1.0.Milestone4 Environment: iPhone Reporter: Jan Papousek After selecting an item from ordering list, the moving buttons next to the list should be enabled. This doesn't work on iPhone. It works on Android. -- 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, 9 months

13
25
0 / 0

[JBoss JIRA] (RF-12011) Gradient configuration in ecss

by Dupont Dupont (JIRA)

Dupont Dupont created RF-12011: ---------------------------------- Summary: Gradient configuration in ecss Key: RF-12011 URL: https://issues.jboss.org/browse/RF-12011 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Dupont Dupont For the moment, gradients are : # configured in resource-mappings.properties (i.e. https://github.com/richfaces/components/blob/develop/input/ui/src/main/re...) {noformat} org.richfaces.images\:autocompleteButtonGradient.png=org.richfaces.renderkit.html.images.AutocompleteGradient\ {topColorParam=headerGradientColor ,bottomColorParam=headerBackgroundColor} {noformat} # and then used in ecss files (i.e. https://github.com/richfaces/components/blob/develop/input/ui/src/main/re...). {noformat} background-image: "url(#{resource['org.richfaces.images:autocompleteButtonGradient.png']})"; {noformat} A simpler solution could be allowing gradient configuration directly in the ecss file, e.g. {noformat} background-image:"url(#{resource['org.richfaces.dynamic:org.richfaces.renderkit.html.images.AutocompleteGradient?topColorParam=headerGradientColor&bottomColorParam=headerBackgroundColor']})"; {noformat} org.richfaces.dynamic being a special library name telling Richfaces to instantiate AutocompleteGradient and configure it on the fly. This would enable to get rid of resource-mappings.properties for simple use cases. N.B. : a control must be implemented to control which classes can be dynamically instantiated (i.e. only allow classes implementing Java2DUserResource). -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] (RF-12016) Support for component dynamically choosing skin

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12016: ------------------------------- Summary: Support for component dynamically choosing skin Key: RF-12016 URL: https://issues.jboss.org/browse/RF-12016 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-misc Reporter: Dupont Dupont -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] (RF-12017) Template handling

by Dupont Dupont (JIRA)

Dupont Dupont created RF-12017: ---------------------------------- Summary: Template handling Key: RF-12017 URL: https://issues.jboss.org/browse/RF-12017 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Dupont Dupont This functionnality will enable easily import a theme into it's own application. It's quite related to template handling in JSF 2.2 [1]. A template / theme will consist of : * 1..n : the necessary xhtml file for the site layout. * 0..n : images. * 0..n : css files or ecss files. * 0..n : js files. * 0..1 : resource-mapping.property * 1 : skin.properties Requirements : * easy installation adding a template / theme must be just a matter of drag & drop (so all the resources must be a stand alone directory). * easy modification the developer must be able to customize the template / theme. Implies : ** template/theme resources must be expanded (not zipped or jarred) ** hot reloading all common theme related resource modification must be hot reloaded. Proposed organization : * src/main/webapp/resources/templates/theme1/template.xhtml * src/main/webapp/resources/templates/theme1/img * src/main/webapp/resources/templates/theme1/css * src/main/webapp/resources/templates/theme1/js * src/main/webapp/resources/templates/theme1/theme1.skin.properties * src/main/webapp/resources/templates/theme1/resource-mapping.properties TBD : * this JIRA must define common names for template parts (i.e. menu, title, content) in order to be able to use different themes with the same jsf files. Sample usage (jsf file using a template) : {code:xml} <ui:composition template="#{theme.template}" xmlns="http://www.w3.org/1999/xhtml" xmlns:h="http://java.sun.com/jsf/html" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:f="http://java.sun.com/jsf/core"> <ui:define name="title">Gallery</ui:define> <ui:define name="content"> My custom content </ui:define> </ui:composition> {code} [1] http://weblogs.java.net/blog/lamineba/archive/2011/11/12/multi-templating... http://weblogs.java.net/blog/lamineba/archive/2011/10/03/conventional-ui-... https://svn.java.net/svn/jsf-extensions~svn/branches/SPEC_532_MODULAR_JSF -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] (RF-12015) Support for EL-evaluated Less-to-CSS compiler

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12015: ------------------------------- Summary: Support for EL-evaluated Less-to-CSS compiler Key: RF-12015 URL: https://issues.jboss.org/browse/RF-12015 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: core Reporter: Dupont Dupont -- 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, 9 months

3
2
0 / 0

[JBoss JIRA] (RF-12014) Support for loading skin.properties and resource-mapping.properties from webapp/resources

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12014: ------------------------------- Summary: Support for loading skin.properties and resource-mapping.properties from webapp/resources Key: RF-12014 URL: https://issues.jboss.org/browse/RF-12014 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: core Reporter: Dupont Dupont -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] (RF-12012) rich:contextMenu re-render problem

by Philip Maes (JIRA)

Philip Maes created RF-12012: -------------------------------- Summary: rich:contextMenu re-render problem Key: RF-12012 URL: https://issues.jboss.org/browse/RF-12012 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu Affects Versions: 4.2.0.Final Environment: Apache Tomcat/7.0.23 , Mojarra 2.1.5, RichFaces 4.2.0.Final Reporter: Philip Maes Priority: Critical I have a extendedDataTable with a contextMenu attached to it. When the selection changes on the extendedDataTable, a a4j:jsFunction is called. This jsFunction renders the contextMenu. {quote} <rich:extendedDataTable id="dtLivingCosts" onselectionchange="selChange('dtLivingCosts')" ... </rich:extendedDataTable> ... <a4j:jsFunction name="selChange" execute="@form" action="#{fhIndBean.selectionListener()}" status="none" render="dtLivingCosts, contextMenu_dtLivingCosts"> <a4j:param name="comp" assignTo="#{fhIndBean.tableId}" /> </a4j:jsFunction> ... <rich:contextMenu id="contextMenu_dtLivingCosts" target="dtLivingCosts" attached="true" mode="ajax" > ... </rich:contextMenu> {quote} The problem is that as soon as I right-click, the contextMenu appears, the ajax request is sent and received, the view is partially updated (dtLivingCosts, contextMenu_dtLivingCosts) and then the contextMenu disappears and won't appear anymore. I noticed that the javascript code generated by RichFaces for the contextMenu is not rerendered as you can see on these two screenshots. The first one shows the code when the page is generated for the first time. The second one, when a right-click has been done on a row in the extendedDataTable: http://img848.imageshack.us/img848/8876/cm1j.png http://img19.imageshack.us/img19/5170/cm2c.png A possible workaround is to refresh only menuItems of the contextMenu (https://issues.jboss.org/browse/RF-11973). -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] (RF-11801) ClientValidatorImpl ClssCastException in restoreState (StateHolderSaver not an Object[])

by Giovanni Pelosi (Created) (JIRA)

ClientValidatorImpl ClssCastException in restoreState (StateHolderSaver not an Object[]) ---------------------------------------------------------------------------------------- Key: RF-11801 URL: https://issues.jboss.org/browse/RF-11801 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.1.0.CR1 Reporter: Giovanni Pelosi when i do an ajax submit on a form with <rich:validator /> inputs fields (h:inputText) (defined in a composite component), i got this exception: ClassCastException in org.richfaces.component.behavior.ClientValidatorImpl.restoreState at line 357 @Override public void restoreState(FacesContext context, Object state) { if (context == null) { throw new NullPointerException(); } if (state != null) { ==> Object[] values = (Object[]) state; super.restoreState(context, values[0]); if (values.length != 1) { groups = (Class<?>[]) values[1]; // If we saved state last time, save state again next time. clearInitialState(); } } } because state is an instance of javax.faces.component.StateHolderSaver RF 4.1CR1 MOJARRA 2.1.3 JBoss 7.0.2 -- 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, 9 months

8
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues February 2012