May 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12220) EDT: column width is reset after ajax request

by Pavol Pitonak (JIRA)

Pavol Pitonak created RF-12220: ---------------------------------- Summary: EDT: column width is reset after ajax request Key: RF-12220 URL: https://issues.jboss.org/browse/RF-12220 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.2.1.Final Environment: RichFaces 4.2.1-SNAPSHOT Metamer 4.2.1-SNAPSHOT Mojarra 2.1.7-jbossorg-1 JBoss AS 7.1.1.Final Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux Chrome 18.0.1025.162 @ Linux i686 Reporter: Pavol Pitonak # deploy Metamer and open http://localhost:8080/metamer/faces/components/richExtendedDataTable/scro... # change the width of the first column # scroll to the second page result: table's first column has original width -- 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

2
1
0 / 0

[JBoss JIRA] (RF-12213) Plain skin is not packaged with rest of skins

by Jeevendran Mahibalan (JIRA)

Jeevendran Mahibalan created RF-12213: ----------------------------------------- Summary: Plain skin is not packaged with rest of skins Key: RF-12213 URL: https://issues.jboss.org/browse/RF-12213 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component Reporter: Jeevendran Mahibalan Plain skin is not packaged with rest of skins, so resource optimization has some issues with components like autosuggest. -- 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

2
2
0 / 0

[JBoss JIRA] (RF-12159) Richfaces Kitchensink Archetype adds atmosphere-compat-weblogic-0.8.4.jar to the WEB-INF\lib

by Burr Sutter (JIRA)

Burr Sutter created RF-12159: -------------------------------- Summary: Richfaces Kitchensink Archetype adds atmosphere-compat-weblogic-0.8.4.jar to the WEB-INF\lib Key: RF-12159 URL: https://issues.jboss.org/browse/RF-12159 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: archetype Affects Versions: 4.2.0.Final Reporter: Burr Sutter Attachments: Screen Shot 2012-04-11 at 9.42.28 AM.png The currently deployed archetype in JBoss Central includes atmosphere-compat-weblogic-0.8.4.jar in the WEB-INF\lib of the deployed .war - it also includes Jetty, Tomcat. -- 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
11
0 / 0

[JBoss JIRA] (RF-12170) Implement a4j:include in Richfaces 4.0

by Grigoras Cristinel (JIRA)

Grigoras Cristinel created RF-12170: --------------------------------------- Summary: Implement a4j:include in Richfaces 4.0 Key: RF-12170 URL: https://issues.jboss.org/browse/RF-12170 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.2.1.CR1 Reporter: Grigoras Cristinel I want to upgrade my application but i need a4j:include to work. The page is to heavy to use something like rendered , or src change. -- 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
6
0 / 0

[JBoss JIRA] (RF-12264) richfaces 3.3.3 final sometime not working with IE9.

by Asim Satti (JIRA)

Asim Satti created RF-12264: ------------------------------- Summary: richfaces 3.3.3 final sometime not working with IE9. Key: RF-12264 URL: https://issues.jboss.org/browse/RF-12264 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: compatibility Affects Versions: 3.3.3.Final Environment: window Reporter: Asim Satti richfaces 3.3.3 final sometime not working with IE9. when i run the project it sometime not load the richfaces stylesheet but if i run it in IE9 compatibility mode it works ok. -- 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

2
1
0 / 0

[JBoss JIRA] (RF-12215) Javascript files included several times when using Portlets and RF

by Markus Staab (JIRA)

Markus Staab created RF-12215: --------------------------------- Summary: Javascript files included several times when using Portlets and RF Key: RF-12215 URL: https://issues.jboss.org/browse/RF-12215 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.3.3.Final Environment: Liferay 5.2.4, JSF 1.2, RF 3.3.3 Reporter: Markus Staab we use RF in a liferay portal env. on our startpage are several portlets deployed. most of theese portlets use rich:modalpanel and therefore include the modalpanel.js, each on it's own. Since the browser loads each portlet after another (and renders their javascript files inside the portlets div-container) the javascript files override each other. -- 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

2
2
0 / 0

[JBoss JIRA] (RF-12194) Support conditionnal resource dependency

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12194?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12194: ------------------------------------ While supporting conditional resources for a component, we can also consider support conditional components. ie. including resources for components added during an ajax update that were not present in the initial request. For a use case, see this forum thread: https://community.jboss.org/thread/199788 > Support conditionnal resource dependency > ---------------------------------------- > > Key: RF-12194 > URL: https://issues.jboss.org/browse/RF-12194 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: cdk > Affects Versions: 4.2.1.Final > Environment: All > Reporter: Paul Dijou > Labels: cdk, dependency, performance, resource, richfaces > Fix For: 4.3-Tracking > > > Sometimes, when developping a component, you will need some resources only in particular case. For example, Bootstrap navbar only need Bootstrap CSS by default. But if you want to enable a collapse effect on smartphone in order to save space, you will also need bootstrap-collapse.js file. > I'm fine with always having the JS file imported, but it would be more perfect if the resource dependency was resolved only if the collapse effect has been enabled in the navbar. So having a way to condition the import of some resource dependency. -- 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
0
0 / 0

[JBoss JIRA] (RF-12194) Support conditionnal resource dependency

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12194?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12194: ---------------------------- Labels: cdk dependency performance resource richfaces (was: cdk dependency resource richfaces) Fix Version/s: 4.3-Tracking (was: 4.3.0.Milestone1) > Support conditionnal resource dependency > ---------------------------------------- > > Key: RF-12194 > URL: https://issues.jboss.org/browse/RF-12194 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: cdk > Affects Versions: 4.2.1.Final > Environment: All > Reporter: Paul Dijou > Labels: cdk, dependency, performance, resource, richfaces > Fix For: 4.3-Tracking > > > Sometimes, when developping a component, you will need some resources only in particular case. For example, Bootstrap navbar only need Bootstrap CSS by default. But if you want to enable a collapse effect on smartphone in order to save space, you will also need bootstrap-collapse.js file. > I'm fine with always having the JS file imported, but it would be more perfect if the resource dependency was resolved only if the collapse effect has been enabled in the navbar. So having a way to condition the import of some resource dependency. -- 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
0
0 / 0

[JBoss JIRA] Created: (RF-11144) Add the possibility to configure which jquery version RF will use.

by José Freitas (JIRA)

Add the possibility to configure which jquery version RF will use. ------------------------------------------------------------------ Key: RF-11144 URL: https://issues.jboss.org/browse/RF-11144 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: José Freitas This feature would be awesome cause it could easy integration with others components suites like primefaces. if we could say to richfaces where it could find its jquery reference, we could config it to use jquery from primefaces for example. <h:outputScript library="primefaces" name="jquery/jquery.js" /> avoiding jquery double loading and conflicts between libs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

4
3
0 / 0

[JBoss JIRA] (RF-12177) "data-*" attributes in JSF components

by Paul Dijou (JIRA)

Paul Dijou created RF-12177: ------------------------------- Summary: "data-*" attributes in JSF components Key: RF-12177 URL: https://issues.jboss.org/browse/RF-12177 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component Affects Versions: 4.2.0.Final Environment: Any Reporter: Paul Dijou Hi there, First of all, sorry for all native English speakers, maybe your eyes will suffer from my grammar... A few days ago, I tried to use Bootstrap with JSF and faced quite an issue by not having any "data-*" attributes in JSF composents. Since Bootstrap, and more generally HTML5, relies a lot on this type of attribute, I was thinking it would be great to have them in JSF. My first tought was to propose the idea to RichFaces but then I aimed directly to JSF spec and here we are : http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-1089 Still, if you are okay for it, it would be great to discuss about this issue (maybe during a RichFaces meeting) in order to propose something more documented than just an idea to JSF spec. I could try to do that alone, but having feedback from JSF experts would be really better and result in more precise and clever proposal. So far, here are my toughts about the problem : 1) Only one new attribute "data" in JSF tags but it will create several "data-*" attributs in the HTML tag rendered depending on its value. 2) Using JSON format to provide all key => value pairs. For example : data="{key1:'value1', key2:'value2'}" will generate data-key1="value1" data-key2="value2" in the HTML tag. 3) Nesting attributes is allowed : data="{key1:{sub1:'value11',sub2:'value12'}, key2:'value2'}" will generate data-key1-sub1="value11" data-key1-sub2="value12" data-key2="value2" 4) Wait, that means there is no way to have both data-key1="value1" and data-key1-sub1="value11" since "key1" key can only have one value : a real value (like "value1") or an array for nesting purpose (like "{sub1:'value11',sub2:'value12'}"). I think the best way to solve this is to have a specific key that will add no suffix even in a nested array. Let's call this key 'nil' or 'null' or wathever. So data="{key1:{nil:'value1', sub1:'value11', sub2:'value12'}} would generate data-key1="value1" data-key1-sub1="value11" data-key1-sub2="value12" Warning : this special key should no accept an array as value. Or conflicts would appears really quickly. Like having : data="{key1:{nil:{sub1:'value1'}, sub1:'value2'}}" would generate data-key1-sub1="value1" data-key1-sub1="value2"... Error ! 5) Of course, EL are allowed inside the JSON format. So, this is correct : data="{key1:{sub1:'#{bean.subvalue1}',sub2:'value12'}, key2:'#{bean.value2}'}". The return type of the EL must be String. But it can be plain String for a real value or an array in JSON format for nesting purpose. If bean.subvalue1 = "value11" and bean.value2 = "{sub1:'value21'}", then the precedent example will generate : data-key1-sub1="value11" data-key1-sub2="value12" data-key2-sub1="value21" 6) That was the first part. Next, what about a more Java centric approach ? "data" attribut could also accept a Map<String, Object> as value. For each Entry<String,Object>, it would add the String key as a suffix of "data" and calling Object#toString() method for the value. Only exception : if Object is an instance of Map, then it will nest the Map. The special key for non-suffix adding could be null value or an empty String. 7) Perhaps, also, try to do combos ! Like having data="{key1:#{bean.value}}" where bean.value is a Map<String,Object> that should be interpreted as a JSON array for nesting purpose. 8) Or combo fusion ! Having the possibility to add several entry point on the "data" attribute, separated by whitespace, before merging them all. For exemple, having : data="#{bean.jsonArray} #{bean.firstMap} #{bean.secondMap}", where bean.jsonArray is a String with JSON format, and bean.firstMap and bean.secondMap are Map<String,Object>. But it would be open door to unique attribute name conflicts. That's all. I'm really looking forward to any feedback or brainstorming in Irc. Maybe, just another idea, if I have time (or anyone else), try to submit some code doing that to RichFaces. It could help people who are using RichFaces 4 but won't be able to migrate to JSF 2.2 yet and still need "data-*" attributes. Thanks for reading. -- 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
18
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues May 2012