November 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13349) a4j:queue must be first child for rich:autocomplete

by alexey plotnikov (JIRA)

[ https://issues.jboss.org/browse/RF-13349?page=com.atlassian.jira.plugin.s... ] alexey plotnikov commented on RF-13349: --------------------------------------- Hmmm, i can not reproduce too :(. But this bug was produced on some page(i don't remember page name). I'll try find this page. > a4j:queue must be first child for rich:autocomplete > --------------------------------------------------- > > Key: RF-13349 > URL: https://issues.jboss.org/browse/RF-13349 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: alexey plotnikov > Assignee: Pavol Pitonak > Labels: waiting_on_user > > All described here https://community.jboss.org/message/845845 but i'll repeat. > In this example: > {code} > <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteLegals}" > minChars="0" var="s" fetchValue="#{s.realName}" id="legal-suggestion" > autofill="false" > onselectitem="autocompleteChangeLegal(event.target)" style="display: inline;" > layout="table" value="#{autocomplete.legalName}" > required="true"> > <h:column> > <h:outputText style="display:none;" value="#{s.id}"/> > <h:outputText style="display:none;" value="#{s.realName}"/> > </h:column> > <h:column> > <h:outputText value="#{s.name}" escape="false"/> > </h:column> > <a4j:queue requestDelay="500" ignoreDupResponses="true" /> > </rich:autocomplete> > {code} > a4j:queue - is *ignored!* > But here > {code} > <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteLegals}" > minChars="0" var="s" fetchValue="#{s.realName}" id="legal-suggestion" > autofill="false" > onselectitem="autocompleteChangeLegal(event.target)" style="display: inline;" > layout="table" value="#{autocomplete.legalName}" > required="true"> > <a4j:queue requestDelay="500" ignoreDupResponses="true" /> > <h:column> > <h:outputText style="display:none;" value="#{s.id}"/> > <h:outputText style="display:none;" value="#{s.realName}"/> > </h:column> > <h:column> > <h:outputText value="#{s.name}" escape="false"/> > </h:column> > </rich:autocomplete> > {code} > a4j:queue *not ignored*. So a4j:queue must be first child for autocomplete. > For another components a4j:queue can be any child(first or last). > For example this code: > {code} > <h:selectOneMenu value="#{agentMenuMassList.menuProfile}"> > <s:selectItems noSelectionLabel="#{messages['pages.noSelect']}" value="#{agentMenuMassList.menuProfiles}" var="m" label="#{m.name}"/> > <s:convertEntity/> > <a4j:ajax event="change" render="editPanel,menuPanel" listener="#{agentMenuMassList.change}"/> > <a4j:queue requestDelay="5000" /> > </h:selectOneMenu> > {code} > *not* ignoring a4j:queue -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12193) rich:extendedDataTable is blank on show

by Salvo Isaja (JIRA)

[ https://issues.jboss.org/browse/RF-12193?page=com.atlassian.jira.plugin.s... ] Salvo Isaja commented on RF-12193: ---------------------------------- Seems to be still present as of 4.3.4, please see my comment on issue 12682. Thanks. > rich:extendedDataTable is blank on show > --------------------------------------- > > Key: RF-12193 > URL: https://issues.jboss.org/browse/RF-12193 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.1.Final > Environment: Firefox 11, Internet Explorer 8 > Reporter: Nick Dev > Assignee: Brian Leathem > Fix For: 4.3.2, 5.0.0.Alpha1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > rich:extendedDataTable is blank when shown after it was hidden. > Firefox: complete table is blank. > IE: table header is not displayed. > Table is shown after resizing the window. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12682) extendedDataTable render issue with rich:tabPanel

by Salvo Isaja (JIRA)

[ https://issues.jboss.org/browse/RF-12682?page=com.atlassian.jira.plugin.s... ] Salvo Isaja commented on RF-12682: ---------------------------------- Hello Brian, unfortunately I'm hitting this issue with 4.3.4. I'm using the tab panel of Bootstrap 3, though, not RichFaces'. When switching tabs, the height of the extendedDataTable seems to drop to zero (the headers are not visible too, everything is grayed out in Firebug) and the table is blank. This even happens without switching tabs, but just opening Firebug (but not just resizing the browser window). Tested on Firefox 25. Any help is appreciated. Thanks, Salvo > extendedDataTable render issue with rich:tabPanel > ------------------------------------------------- > > Key: RF-12682 > URL: https://issues.jboss.org/browse/RF-12682 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.3.Final, 4.3.0.M3, 4.3.0.CR1, 4.3.0.Final > Reporter: Kaveh A. > Labels: extendedDataTable, render, richfaces, tabpanel, testcase_provided > Attachments: richfacesBug2.zip, RichFacesBugEclipseProject.zip > > > This issue is not just specific to tabPanel. Anytime the extendedDataTable is hidden (when the page loads) and then it is made visible later the table can not display the data (table is empty at the load time). > In this particular case if we load a page with two tabs. Furthermore if we have one extendedDataTable in each tab (the first tab shows and the second tab is not shown at first). In this case once the user clicks on the second tab and tries to populate the extendedDataTable (via any action). Then the table is not rendered properly. A sample project has been provided at the following link that further describe this issue. You can download the eclipse project attached at the end of the following message to reproduce this issue. > https://community.jboss.org/message/783787 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13323) FileUploadEvent listener reset the list value with Viewscope

by Mohammad Weshah (JIRA)

[ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.s... ] Mohammad Weshah commented on RF-13323: -------------------------------------- Hello Jiří Štefek Any update ? Regards Wish79 > FileUploadEvent listener reset the list value with Viewscope > ------------------------------------------------------------ > > Key: RF-13323 > URL: https://issues.jboss.org/browse/RF-13323 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4 > Environment: Jboss 7.1 > Richfaces 4.3.4 > JSF 2.1.9 > > Reporter: Mohammad Weshah > Assignee: Jiří Štefek > Labels: rich:fileUpload > Attachments: RF-13323-2.zip, RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.rar, TestRichFacesWebProject.war > > > Hello All, > i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow : > > {code} > protected List<UploadedImage> files = new ArrayList<UploadedImage>(); > > public void FileUploadlistener(FileUploadEvent event) throws Exception { > UploadedFile item = event.getUploadedFile(); > UploadedImage file = new UploadedImage(); > file.setLength(item.getData().length); > file.setName(item.getName()); > file.setData(item.getData()); > > files.add(file); > } > {code} > > but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ? > > Regards > Wish79 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-4308) rich:pickList: keep sort order of source list after add/remove operations

by Val Blant (JIRA)

[ https://issues.jboss.org/browse/RF-4308?page=com.atlassian.jira.plugin.sy... ] Val Blant commented on RF-4308: ------------------------------- I have an easy fix for this problem that seems to work pretty well. Just include this _orderedPickListFix.js_ in your app, and the pickLists should start behaving. {code:javascript|title=orderedPickListFix.js|borderStyle=solid} /** * This is an extension to the RichFaces PickList that preserves the original order of items in the source list * * @author Val Blant */ if ( typeof window.RichFaces.ui.List != 'undefined' && !window.PickListExtension ) { window.PickListExtension = {}; if ( typeof window.RichFaces.ui.PickList != 'undefined' ) { /** * Overriding original constructor found in "org.richfaces/pickList.js" resource */ window.RichFaces.ui.PickList = function(oldPickListConstructor) { return function(id, options) { // Instantiate the original PickList // var pickList = new oldPickListConstructor(id, options); // Assign item indecies to each item in the source list to preserve original order // pickList.sourceList.items.each(function( index ) { this.itemIndex = index; }); return pickList; }; }(window.RichFaces.ui.PickList); } /** * Original code taken from "org.richfaces/list.js" resource */ (function($, rf, list) { /** * Insert items into a pick list according to their original order stored in 'itemIndex' attribute */ list.prototype.addItems = function(items) { var parentContainer = this.scrollContainer; items.each(function() { if ( parentContainer.children().length < this.itemIndex ) { parentContainer.append(this); } else { itemAtOurIndex = parentContainer.children()[this.itemIndex]; jQuery(this).insertBefore( itemAtOurIndex ); } }); this.__updateItemsList(); rf.Event.fire(this, "additems", items); }; }(jQuery, window.RichFaces, window.RichFaces.ui.List)); } {code} > rich:pickList: keep sort order of source list after add/remove operations > ------------------------------------------------------------------------- > > Key: RF-4308 > URL: https://issues.jboss.org/browse/RF-4308 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 3.2.2 > Reporter: Martin Höller > Labels: order, picklist, sort > Fix For: 3.Future > > > When adding items from the source list to the target list and removing this items again, the original order of the source list is not preserved. This makes it hard to find items in a list that is longer than just a fest items. A good example is the second example on the livedemo at http://livedemo.exadel.com/richfaces-demo/richfaces/pickList.jsf. Add the first state (Alabama) and remove it. It can now be found at the very end of the otherwise alphabetical list of states. This can be rather unintuitive for a user. > My suggestion is either remember the original sort order of the source list, or add some attribute that enables automatic sorting. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-11284) rich:autocomplete on Mojarra doesn't handle suggestions/selection correctly

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-11284?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-11284: ------------------------------- Assignee: (was: Brian Leathem) > rich:autocomplete on Mojarra doesn't handle suggestions/selection correctly > --------------------------------------------------------------------------- > > Key: RF-11284 > URL: https://issues.jboss.org/browse/RF-11284 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.1.0.Milestone1 > Environment: RichFaces 4.1.0.20110805-M1 r.10246d45dddd1d2aa2034317d5a832394cc919f9 > Metamer 4.1.0.20110805-M1 r.22604 > Mojarra 2.0.3- > JBoss AS 6.0.0.Final > Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux > Chrome 12.0.742.112 @ Linux i686, IE7, > Reporter: Ján Jamrich > Fix For: 5-Tracking > > > In the contrary with rich:autocomplete with MyFaces, there is not working suggestions or suggestion selection for autocomplete. > Common case is type some keys into autocomplete input, e.g. "al" and wait for display suggestions, in this case "Alabama, Alaska". Then pick one of them, and this item should appear in autocomplete input instead of typed characters (so that value start with upper case and so on), and this value appears in output element. > It is working correctly with autocomplete example without any changes (just open page faces/components/richAutocomplete/autocomplete.xhtml). > But when set any attribute value (such as layout to div, or minChars to 2 or something else), selection from autocomplete suggestions stop work. > Then is not possible to select item from suggestion, but when click (or select by narrovs and press enter) on an item, then suggestions disappears, but autocomplete input remain empty not the output is updated by selected value. > The workaround is invalidate session, but it causes clean attribute value (so then is not minChars or layout attribute set to any value). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-13350) pickList: styleClass attribute is rendered wrongly as styleclass instead of class attribute

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13350?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-13350. -------------------------------- Resolution: Done > pickList: styleClass attribute is rendered wrongly as styleclass instead of class attribute > ------------------------------------------------------------------------------------------- > > Key: RF-13350 > URL: https://issues.jboss.org/browse/RF-13350 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj Húska > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Setting of {{styleClass}} attribute to the {{pickList}} component makes generated markup to contain {{styleclass}} attribute - instead of just adjusted {{class}} attribute. > The {{styleClass}} is included just in {{passThrough}} attributes - [here|https://github.com/richfaces/richfaces/blob/master/framework/src/mai...]. > Should not be it done as it is for example [here|https://github.com/richfaces/richfaces/blob/master/framework/src/mai...] in autocomplate render base ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-13350) pickList: styleClass attribute is rendered wrongly as styleclass instead of class attribute

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13350?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-13350: ---------------------------------- Assignee: Brian Leathem > pickList: styleClass attribute is rendered wrongly as styleclass instead of class attribute > ------------------------------------------------------------------------------------------- > > Key: RF-13350 > URL: https://issues.jboss.org/browse/RF-13350 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj Húska > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Setting of {{styleClass}} attribute to the {{pickList}} component makes generated markup to contain {{styleclass}} attribute - instead of just adjusted {{class}} attribute. > The {{styleClass}} is included just in {{passThrough}} attributes - [here|https://github.com/richfaces/richfaces/blob/master/framework/src/mai...]. > Should not be it done as it is for example [here|https://github.com/richfaces/richfaces/blob/master/framework/src/mai...] in autocomplate render base ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-13210) Move RichFaces resources from META-INF/resources/ to org.richfaces library

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13210?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13210: ------------------------------- Sprint: 5.0.0.Alpha2 - Sprint 6 > Move RichFaces resources from META-INF/resources/ to org.richfaces library > -------------------------------------------------------------------------- > > Key: RF-13210 > URL: https://issues.jboss.org/browse/RF-13210 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-13350) pickList: styleClass attribute is rendered wrongly as styleclass instead of class attribute

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13350?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13350: ------------------------------- Sprint: 5.0.0.Alpha2 - Sprint 6 > pickList: styleClass attribute is rendered wrongly as styleclass instead of class attribute > ------------------------------------------------------------------------------------------- > > Key: RF-13350 > URL: https://issues.jboss.org/browse/RF-13350 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj Húska > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Setting of {{styleClass}} attribute to the {{pickList}} component makes generated markup to contain {{styleclass}} attribute - instead of just adjusted {{class}} attribute. > The {{styleClass}} is included just in {{passThrough}} attributes - [here|https://github.com/richfaces/richfaces/blob/master/framework/src/mai...]. > Should not be it done as it is for example [here|https://github.com/richfaces/richfaces/blob/master/framework/src/mai...] in autocomplate render base ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues November 2013