February 2009 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Resolved: (RF-227) DataFilterSlider: slider dissapeares in right end position in IE6

by Nick Belaevski (JIRA)

[ https://jira.jboss.org/jira/browse/RF-227?page=com.atlassian.jira.plugin.... ] Nick Belaevski resolved RF-227. ------------------------------- Fix Version/s: (was: Future) Resolution: Out of Date Assignee: Tsikhon Kuprevich (was: Nick Belaevski) > DataFilterSlider: slider dissapeares in right end position in IE6 > ----------------------------------------------------------------- > > Key: RF-227 > URL: https://jira.jboss.org/jira/browse/RF-227 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.1.0 > Environment: Build 3.1.4 Sr1 > JDK 1.6 > IE6 only > Reporter: Viktor Volkov > Assignee: Tsikhon Kuprevich > Priority: Minor > Attachments: DataFilterSlider_slider_disapeares.avi > > > 1. Open DataFilterSlider > 2. Move Slider to right end position > --->>> Slider disapeares -- 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

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (RF-2774) rich:suggestionbox and a4j:support problem in Safari 3.1

by Nils Eckert (JIRA)

rich:suggestionbox and a4j:support problem in Safari 3.1 -------------------------------------------------------- Key: RF-2774 URL: http://jira.jboss.com/jira/browse/RF-2774 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.4 Environment: Mac OS 10.5.2, Safari 3.1 (5525.13), RichFaces 3.1.4SR1 Reporter: Nils Eckert Hello together, I noticed the following behavior. In my form i got a rich:suggestionBox with a <a4j:support event="onchange" ... /> Children. The onchange event calls an action and reRenders the hole form including the rich:suggestionBox. This works in most Browsers (Firefox Mac + Windows, IE7). But in Safari 3.1 I get the problem that the suggestionBox is not autocompleting after a onchange event was fired. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (RF-2601) Insert: the text being inserted is cut when not using highlight attribute

by Tsikhon Kuprevich (JIRA)

Insert: the text being inserted is cut when not using highlight attribute ------------------------------------------------------------------------- Key: RF-2601 URL: http://jira.jboss.com/jira/browse/RF-2601 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.0 Environment: 2.3.0.CR3 Reporter: Tsikhon Kuprevich Assigned To: Nick Belaevski Insert: the text being inserted is cut when not using highlight attribute -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (RF-2446) Bug in UIDataAdaptor(some data doesn't get updated)

by Ilya Shaikovsky (JIRA)

Bug in UIDataAdaptor(some data doesn't get updated) --------------------------------------------------- Key: RF-2446 URL: http://jira.jboss.com/jira/browse/RF-2446 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.0 Reporter: Ilya Shaikovsky Assigned To: Nick Belaevski Fix For: 3.2.0 All info at forum. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (RF-2811) a4j:repeat doesn't support java.util.Set

by Sergey Halipov (JIRA)

a4j:repeat doesn't support java.util.Set ---------------------------------------- Key: RF-2811 URL: http://jira.jboss.com/jira/browse/RF-2811 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.0 Environment: JDK 1.5 Reporter: Sergey Halipov a4j:repeat interprets Sets as simple type not a collection. Example bellow doesn't work correctly. But it would work if we replaced HashSet with ArrayList. JSP code: <a4j:repeat value="#{bean.testLists}" var="list" id="repeat"> <h:outputText value="#{list}"></h:outputText><br /> </a4j:repeat> Java bean: public class Bean { private Collection<String> testLists = new HashSet<String>(); public Bean() { for (int i = 0; i < 30; i++) { testLists.add(new Integer(i).toString()); } } public Collection<String> getTestLists() { return testLists; } public void setTestLists(Collection<String> testLists) { this.testLists = testLists; } } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (RF-6020) skinning the ajax-status of rich:extendedDatatable

by nimo stephan (JIRA)

skinning the ajax-status of rich:extendedDatatable -------------------------------------------------- Key: RF-6020 URL: https://jira.jboss.org/jira/browse/RF-6020 Project: RichFaces Issue Type: Feature Request Affects Versions: 3.3.0 Reporter: nimo stephan Priority: Minor It would be nice to have skinning-support for the wait-screen of rich:extendedDatatable. For example, changing the group-order or the column-order results in waiting a while, having a white screen with a a4j:status in the middle, which should have skinnable support. For example, intead of the icon, it can declared such as for a4j:status: <a4j:status startText="Please wait..." /> Background-color would be also nice.. -- 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

15 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (RF-5955) a4j push fails(sometimes) to rerender target component

by Atul Kshirsagar (JIRA)

a4j push fails(sometimes) to rerender target component ------------------------------------------------------ Key: RF-5955 URL: https://jira.jboss.org/jira/browse/RF-5955 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.0 Environment: JBoss AS: 4.2.2 GA JBoss Seam: 2.1.1GA JBoss RichFaces: 3.3.0 GA OS: Windows XP Browser: Firefox 3.0.5 and IE 7 Reporter: Atul Kshirsagar a4j push tag fails to reRender the target component (specified in reRender attribute) sometimes. In our project we are using a4j:push tag to dynamically refresh certain portions of our web page depending upon events generated on server side. The problem that I am seeing is that some times (not always) a4j push does not reRender the target id specified even though PushEventListener is notified of an Event. Note that I have 8 a4j push tags refreshing different components on our web page and we can see burst of events (approx 200 events in less than 1 min). Below given is the example code: xhtml that uses a4j:push tag: <a4j:push reRender="myTableId" eventProducer="#{myBean.addListener}" interval="10000" ignoreDupResponses="true" action="#{mybean.populateViewModel}"/> <rich:dataTable id="myTableId" value="#{myBean.data}" var="_data"> <rich:column> <h:outputText value="#{_data.name}" /> </rich:column> </rich:dataTable> Backing bean definition is as follows: @Stateful @Local( { MyBeanLocal.class }) @Name("myBean") @Scope(ScopeType.SESSION) @Restrict("#{identity.loggedIn}") public class MyBean implements MyBeanLocal, Serializable { @EJB private MyEJB ejb; private MyBeanListener eventListener; /** * DataModel */ private List<Data> data; public List<Data> getData() { return this.data; } @Create public void create() { this.data = new ArrayList<Data>(); populateViewModel(); } // destroy method de-registers the listener from DataModel @Remove @Destroy public void destroy() { DataModel dataModel = ejb.getDataModel(); if (dataModel != null) { dataModel.removeChangeListener(eventListener); } } /** * Adds listener for conveying AJAX events. * * @param listener */ public void addListener(EventListener listener) { DataModel dataModel = ejb.getDataModel(); eventListener = new MyBeanListener(); eventListener.addListener(listener); dataModel.addChangeListener(eventListener); } /** * Constructs the view data model required for the link utilization widget on dashboard */ public void populateViewModel() { data.clear(); DataModel dataModel = ejb.getDataModel(); data = dataModel.getData(); } } public class MyBeanListener implements Serializable { private PushEventListener listener; public void addListener(EventListener l) { this.listener = (PushEventListener)l; } public void dataChanged() { listener.onEvent(new EventObject(this)); } } public class DataModel implements MessageListener { private List<MyBeanListener> listeners; public void addChangeListener(MyBeanListener l) { listeners.add(l); } public void removeChangeListener(MyBeanListener l) { listeners.remove(l); } public void fireEvent() { for (MyBeanListener l: listeners) { l.dataChanged(); } } // This method is called on JMS message public void onMessage(Message message) { // update internal data structure and then notify listeners fireEvent(); } } So what is happening here is that class MyBean is SFSB and registers MyBeanListener with DataModel when addListener is called (by virtue of eventProducer attribute of a4j:push). DataModel is a JMS listener and upon receiving JMS message it notifies the registered listener of change in data. What I am seeing here is that all the above described flow happens and a4j:push gets notified of the event (I verified this by checking that populateViewData method of MyBean gets called) but the reRender of 'myTableId' component does not happen (this happens only intermittently...e.g If I repeat the test for about 4 to 5 times I will see it happening once). I debugged it using a4j:log component and found that sometimes the ajax response does not contain the component with id 'myTableId'. -- 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

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (RF-4129) Expanding/collapsing a rich:tree nodes from model

by Francisco Jose Peredo Noguez (JIRA)

Expanding/collapsing a rich:tree nodes from model ------------------------------------------------- Key: RF-4129 URL: https://jira.jboss.org/jira/browse/RF-4129 Project: RichFaces Issue Type: Feature Request Reporter: Francisco Jose Peredo Noguez Lets say I bind my Rich Tree to a list of object using the recursiveTreeNodesAdaptor: Code: <rich:recursiveTreeNodesAdaptor roots="#{rootNodes}" var="node" nodes="#{node.childNodes}"> <rich:treeNode rendered="#{node.visible}"> #{node.name} </rich:treeNode> with this code: rendered="#{node.visible}" I can control if it is visible or not... I would like something similar to control if it is collapsed or not, something like: Code: collapsed="#{node.collapsed}" It would look like this: <rich:recursiveTreeNodesAdaptor roots="#{rootNodes}" var="node" nodes="#{node.childNodes}"> <rich:treeNode rendered="#{node.visible}" collapsed="#{node.collapsed}"> #{node.name} </rich:treeNode> It would be extra-nice if it could propagate back automatically (if a leaf node has collapsed = false, all its parent nodes would be expandend) -- 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

15 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (RF-6014) Technical requirements: more information on dependencies is required

by Svetlana mukhina (JIRA)

Technical requirements: more information on dependencies is required --------------------------------------------------------------------- Key: RF-6014 URL: https://jira.jboss.org/jira/browse/RF-6014 Project: RichFaces Issue Type: Task Components: doc Affects Versions: 3.3.0 Reporter: Svetlana mukhina Assignee: Gleb Galkin Fix For: 3.3.1-doc Give complete information on RF dependencies. see the post http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203982#4203982 -- 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

15 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (RF-5166) fileUpload: fileUploadListener isn't call under myfaces.

by Mikhail Vitenkov (JIRA)

fileUpload: fileUploadListener isn't call under myfaces. -------------------------------------------------------- Key: RF-5166 URL: https://jira.jboss.org/jira/browse/RF-5166 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.0 Environment: myfaces 1.2.5, IE6, IE7, FF 3.1.3, Safari 3.1, Opera 9.62(3.3.0.BETA1) Reporter: Mikhail Vitenkov Assignee: Nick Belaevski #1. Set org.apache.myfaces.CHECK_EXTENSIONS_FILTER context parameter to "false" in web.xml; #2. Set fileUploadListener="#{fileUpload.fileUploadListener}", where listener defined following way: public void fileUploadListener(UploadEvent event) throws Exception{ UploadItem upload = event.getUploadItem(); if (upload.isTempFile()) { File file = upload.getFile(); System.out.println("FileUpload.fileUploadListener()"); } else { ByteArrayOutputStream b = new ByteArrayOutputStream(); b.write(upload.getData()); } System.out.println("FileUpload.fileUploadListener()"); } #3. Navigate to page with component & try to upload any valid file(satisfied with maxFilesQuantity, size restriction and so on). #4. Verify "FileUpload.fileUploadListener()" message in console. Actual behavior: fileUploadListener was not fired. -- 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

15 years, 2 months

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues February 2009