November 2013 - richfaces-issues - Jboss List Archives

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-13355?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak commented on RF-13355: ------------------------------------ My bad... should i create a new issue for upgrading RF 4.3 to Mojarra 2.1.26? > Upgrade Mojarra > --------------- > > Key: RF-13355 > URL: https://issues.jboss.org/browse/RF-13355 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 5.0.0.Alpha2 > Reporter: Pavol Pitonak > Fix For: 5.0.0.Alpha3 > > > RichFaces 5 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26. > [1] https://github.com/richfaces/richfaces/blob/master/build/pom.xml -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12813) rich:panelMenuItem executes action even if disabled attribute evaluates to true

by Pavel Slegr (JIRA)

[ https://issues.jboss.org/browse/RF-12813?page=com.atlassian.jira.plugin.s... ] Pavel Slegr reassigned RF-12813: -------------------------------- Assignee: Pavel Slegr > rich:panelMenuItem executes action even if disabled attribute evaluates to true > ------------------------------------------------------------------------------- > > Key: RF-12813 > URL: https://issues.jboss.org/browse/RF-12813 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.3.0.Final > Reporter: Andrey Zhemoytuk > Assignee: Pavel Slegr > Fix For: 4.3.5 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > org.richfaces.renderkit.html.PanelMenuItemRenderer#doDecode does not check 'disabled' attribute (how usually do other components before executing action) which may cause security issues. > Initially reported on: > http://stackoverflow.com/questions/15130807/richfaces-panelmenuitem-reeva... -- 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, 10 months

1
0
0 / 0

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

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.s... ] Jiří Štefek commented on RF-13323: ---------------------------------- Sorry, even with yours JVM I can't reproduce it. > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-13357) Switch RichFaces to use dist branch of RichWidgets to avoid a need for compiling own version

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-13357: ------------------------------- Summary: Switch RichFaces to use dist branch of RichWidgets to avoid a need for compiling own version Key: RF-13357 URL: https://issues.jboss.org/browse/RF-13357 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component Reporter: Lukáš Fryč Fix For: 5.0.0.Alpha2 -- 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, 10 months

1
0
0 / 0

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

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12682?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12682: ------------------------------------ [~salvois] would you please file a new issue (referencing this one) with appropriate re-producer code attached? > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-13340) orderingList - setting of some attributes does not have any effect on the component

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13340?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-13340. -------------------------------- Assignee: (was: Brian Leathem) Fix Version/s: (was: 5.0.0.Alpha2) Resolution: Out of Date > orderingList - setting of some attributes does not have any effect on the component > ----------------------------------------------------------------------------------- > > Key: RF-13340 > URL: https://issues.jboss.org/browse/RF-13340 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Jiří Štefek > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Setting of these attributes on a {{orderingList}} has no effect on the rendered component > * style > * valueChangeListener -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-13353) Javascript callbacks on global queue are not called

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13353?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-13353. -------------------------------- Resolution: Duplicate Issue > Javascript callbacks on global queue are not called > --------------------------------------------------- > > Key: RF-13353 > URL: https://issues.jboss.org/browse/RF-13353 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Labels: a:queue > > Only two of the javascript callbacks on a:queue are actually functional: > {code} > <a:queue name="org.richfaces.queue.global" requestDelay="300" ignoreDupResponce="true" onrequestqueue="log('onrequestqueue')" onsubmit="log('onsubmit')" oncomplete="log('oncomplete')" onrequestdequeue="log('onrequestdequeue')" onbeforedomupdate="log('onbeforedom')"/> > {code} > When doing an ajax request only onrequestqueue and onrequestdequeue are called. onsubmit, oncomplete and onbeforedomupdate are not called. > Please note: log('xx') is a wrapper around console.log() -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-13354) Autocomplete: suggestions stay visible after input is cleared

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13354?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13354: ------------------------------- Fix Version/s: 5.0.0.Alpha2 > Autocomplete: suggestions stay visible after input is cleared > ------------------------------------------------------------- > > Key: RF-13354 > URL: https://issues.jboss.org/browse/RF-13354 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, regression > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > EAP 6.1.1 > Mojarra 2.1.19 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 31.0.1650.57 @ Linux x86_64 > Reporter: Pavol Pitonak > Fix For: 5.0.0.Alpha2 > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl... > # type "ala" into input (several suggestions will appear) > # clear input, e.g. by using backspace key > result: > * the list with all available suggestions is displayed > * in 4.3.4.Final, the suggestions are *not* displayed when input is empty -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-13355) Upgrade Mojarra

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13355?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13355: ------------------------------- Summary: Upgrade Mojarra (was: Upgrade Mojarra to 2.1.26) RichFaces 5 Alphas should track WildFly, and hence update to JSF 2.2. > Upgrade Mojarra > --------------- > > Key: RF-13355 > URL: https://issues.jboss.org/browse/RF-13355 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 5.0.0.Alpha2 > Reporter: Pavol Pitonak > > RichFaces 5 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26. > [1] https://github.com/richfaces/richfaces/blob/master/build/pom.xml -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-13355) Upgrade Mojarra

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13355?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13355: ------------------------------- Fix Version/s: 5.0.0.Alpha3 > Upgrade Mojarra > --------------- > > Key: RF-13355 > URL: https://issues.jboss.org/browse/RF-13355 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 5.0.0.Alpha2 > Reporter: Pavol Pitonak > Fix For: 5.0.0.Alpha3 > > > RichFaces 5 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26. > [1] https://github.com/richfaces/richfaces/blob/master/build/pom.xml -- 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, 10 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