April 2012 - richfaces-issues - Jboss List Archives

[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-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] 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

[JBoss JIRA] (RF-11588) HeaderClass is ignored on ExtendedDataTable column

by Cody Lerum (Created) (JIRA)

HeaderClass is ignored on ExtendedDataTable column -------------------------------------------------- Key: RF-11588 URL: https://issues.jboss.org/browse/RF-11588 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.1.0.Milestone3 Reporter: Cody Lerum When a header class is defined on a rich:column inside an rich:extendedDataTable it is ignored Assume {code} <rich:column headerClass="left" styleClass="left"> <f:facet name="header">Foo</f:facet> <h:outputText value="Bar" /> </rich:column> {code} What is rendered is {code} <td> <div class="rf-edt-rsz-cntr rf-edt-c-j_idt384" style=""> <div class="rf-edt-rsz"></div> </div> <div class="rf-edt-hdr-c rf-edt-c-j_idt384 left" style="height: 21px; "> <div class="rf-edt-hdr-c-cnt">Foo</div> </div> </td> {code} My style left is applied but the header is one level lower and has rf-edt-hdr-c-cnt style which will always make it center -- 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

6
8
0 / 0

[JBoss JIRA] Created: (RF-8952) Add <cdk:function> element to template language.

by Alexander Smirnov (JIRA)

Add <cdk:function> element to template language. ------------------------------------------------ Key: RF-8952 URL: https://jira.jboss.org/browse/RF-8952 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: CDK Reporter: Alexander Smirnov Assignee: Alexander Smirnov Fix For: 4.0.0.Milestone2 It would be useful to generate html code snippets as Java functions that would be called anywhere from template or java code. For example, html table cells need sofisticated code for iteration while they should be generated inside row elements. The template like this: <table> <tbody> <cdk:call name="renderRows"/> <cdk:function name="renderRow" > <tr> <cdk:call name="renderCells"/> <cdk:function name="renderCell"> <td>....</td> </cdk:function> </tr> </cdk:function> </tbody> </table> lets to put row/cells rendering logic into Java code (renderRows/renderCells methods ) while template markup still follow desired html code. P.S. It would be even more convenient to union both calls into single element with name/call attributes. -- 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

5
9
0 / 0

[JBoss JIRA] Created: (RF-10957) Faces-config: message and message missing attributes style and styleClass

by Jan Jamrich (JIRA)

Faces-config: message and message missing attributes style and styleClass ------------------------------------------------------------------------- Key: RF-10957 URL: https://issues.jboss.org/browse/RF-10957 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: cdk, component Affects Versions: 4.1.0.Milestone1 Environment: RichFaces 4.1.0-SNAPSHOT r.22442 Metamer 4.1.0-SNAPSHOT r.22440 Mojarra 2.0.4-b09 Apache Tomcat 6.0.29 Java(TM) SE Runtime Environment 1.6.0_19-b04 @ Linux Chrome 12.0.718.0 @ Linux i686 Reporter: Jan Jamrich Attributes retrieved from faces-config (by Metamer) missing style and styleClass attribute -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

4
9
0 / 0

[JBoss JIRA] (RF-12092) a4j:poll : a4j:status never clears

by Robert Gary (JIRA)

Robert Gary created RF-12092: -------------------------------- Summary: a4j:poll : a4j:status never clears Key: RF-12092 URL: https://issues.jboss.org/browse/RF-12092 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-push/poll Affects Versions: 4.2.0.Final Reporter: Robert Gary When a4j:poll fires a4j:status correctly displays the request is in progress. However, it never shows it complete. Using any other a4j component will correctly update the a4j:status. So if the a4j:status is stuck showing its waiting because of an a4j:poll if you click on an a4j:commandButton the a4j:status will correctly show its now complete. <a4j:poll id="ajaxPoll" interval="5000" enabled="true" action="#{faces$DiscoveryStatus.poll}" render="#{faces$DiscoveryStatus.reRenderStr}"/> <a4j:status id="a4jstatus"> <f:facet name="start"> <img src='/images/ajax-loader.gif'/> </f:facet>    </a4j:status> This code works correctly in RF 3.3.3. -- 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

6
20
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues April 2012