July 2011 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-8943) SyntaxHighlighter JavaScript-based component

by Nick Belaevski (JIRA)

SyntaxHighlighter JavaScript-based component -------------------------------------------- Key: RF-8943 URL: https://jira.jboss.org/browse/RF-8943 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0.0.Milestone1 Reporter: Nick Belaevski Assignee: Nick Belaevski Fix For: Future_4.X See related forum thread -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (RF-11047) Mock-up the Editor component

by Lukáš Fryč (JIRA)

Mock-up the Editor component ---------------------------- Key: RF-11047 URL: https://issues.jboss.org/browse/RF-11047 Project: RichFaces Issue Type: Sub-task Security Level: Public (Everyone can see) Components: component-input Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 4.1.0.Milestone1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (RF-11043) Collect requirements on Editor component in community

by Lukáš Fryč (JIRA)

Collect requirements on Editor component in community ----------------------------------------------------- Key: RF-11043 URL: https://issues.jboss.org/browse/RF-11043 Project: RichFaces Issue Type: Sub-task Security Level: Public (Everyone can see) Components: component-input Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 4.1.0.Milestone1 Search through forums and collect requirements. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
8
0 / 0

[JBoss JIRA] Created: (RF-11128) Publish JSF 2.0 ExceptionQueuedEvent (instead of log.error)

by Martin Kočí (JIRA)

Publish JSF 2.0 ExceptionQueuedEvent (instead of log.error) ----------------------------------------------------------- Key: RF-11128 URL: https://issues.jboss.org/browse/RF-11128 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: core Environment: RF 4.1 develop Reporter: Martin Kočí use JSF 2.0 ExceptionQueuedEvent try { // } catch (Exception e) { ExceptionQueuedEventContext exceptionQueuedEventContext = new ExceptionQueuedEventContext(context, e, this, PhaseId.XYZ); context.getApplication().publishEvent(context, ExceptionQueuedEvent.class, exceptionQueuedEventContext); } instead of logging. Example: ExtendedPartialViewContextImpl logs exception as severe and that prevents (custom) exception handler to handle that error. Related issues from MyFaces: # https://issues.apache.org/jira/browse/MYFACES-3053 # https://issues.apache.org/jira/browse/MYFACES-3198 # https://issues.apache.org/jira/browse/MYFACES-3201 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (RF-11124) Atmosphere is opening new thread for each request

by Lukáš Fryč (JIRA)

Atmosphere is opening new thread for each request ------------------------------------------------- Key: RF-11124 URL: https://issues.jboss.org/browse/RF-11124 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 4.1.0.Milestone1 Reporter: Lukáš Fryč Assignee: Lukáš Fryč Priority: Critical Fix For: 4.1.0.Milestone1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (RF-11135) Push: make use of JMS configurable

by Lukáš Fryč (JIRA)

Push: make use of JMS configurable ---------------------------------- Key: RF-11135 URL: https://issues.jboss.org/browse/RF-11135 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: core Affects Versions: 4.1.0.Milestone1 Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 4.1.0.Milestone1 Since JMS usage is pretty decoupled from Push messaging (it uses internal message queue now), it should be possible to turn it off completely. JMS should be enabled by default because of backward compatibility, but could be turned off by following web.xml snippet: {code:XML} <context-param> <param-name>org.richfaces.push.jms.disable</param-name> <param-value>true</param-value> </context-param> {code} This is one step closer to RF-11110. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
9
0 / 0

[JBoss JIRA] Created: (RF-11126) Improvement on filtering entries for rich:comboBox

by Martin Dames (JIRA)

Improvement on filtering entries for rich:comboBox -------------------------------------------------- Key: RF-11126 URL: https://issues.jboss.org/browse/RF-11126 Project: RichFaces Issue Type: Patch Security Level: Public (Everyone can see) Components: component-input Affects Versions: 3.3.3.Final Environment: Win7, Firefox 3.6.x, JBoss AS 4.2.3, Seam 2.1.2 Reporter: Martin Dames Priority: Minor I have an improvement patch for the rich:comboBox. My use case was to filter entries with an input string no matter where it occurs in the entries text. Your component implementation can only search for the string at the beginning of the entries text. Example: Entries in comboBox: Seam in Action, Seam with Richfaces, Seam 3, Exadel Richfaces Old: Input filter text: Seam; Filter output: Seam in Action, Seam with Richfaces, Seam 3, Exadel Richfaces Input filter text: Exadel; Filter output: Exadel Richfaces Input filter text: Richfaces; Filter output: nothing found Input filter text: in; Filter output: nothing found New: Input filter text: Seam; Filter output: Seam in Action, Seam with Richfaces, Seam 3, Exadel Richfaces Input filter text: Exadel; Filter output: Exadel Richfaces Input filter text: Richfaces; Filter output: Seam with Richfaces, Exadel Richfaces Input filter text: in; Filter output: Seam in Action The patch occurs in combolist.js Javascript found in /org/richfaces/renderkit/html/scripts/combolist.js: getFilteredItems : function(text) { var items = new Array(); for (var i = 0; i < this.itemsText.length; i++) { var itText = this.itemsText[i].toLowerCase(); // New: if (itText.search(text.toLowerCase()) != -1) { items.push(this.createItem(itText, this.classes.item.normal)); } // Old: //if (itText.substr(0, text.length).toLowerCase() == text.toLowerCase()) { //FIXME: to optimaize //items.push(this.createItem(itText, this.classes.item.normal)); //} } return items; }, Hope it could be helpful. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (RF-11093) UIDataAdaptor context variable backup broken (reentrance problem)

by Yannick Valot (JIRA)

UIDataAdaptor context variable backup broken (reentrance problem) ----------------------------------------------------------------- Key: RF-11093 URL: https://issues.jboss.org/browse/RF-11093 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.0.0.Final Environment: Windows XP, Java 6, Tomcat 6.0.24, Mojarra 2.0.2. Reporter: Yannick Valot I am encountering a reentrance problem with org.richfaces.component.UIDataAdaptor (using it as a dataTable). I need to perform a visit of the component tree while executing an action on a command link in one row of the same table. <rich:dataTable value="#{listOfItems}" var="myItem" > ... some stuff here ... <commandLink here> ... some stuff here ... </rich:dataTable> After the action on the command link has visited the component tree, myItem is no longer available in context. When the UIDataAdaptor sets or resets the "myItem" context variable, it backs up any previous value by calling captureOrigValue(FacesContext), and later restores it by calling restoreOrigValue(FacesContext), but it looks as if the visit backs the variable up twice (in a nested fashion), and it erases myItem between the two backups : - backup variable (old value is correctly backed up) (in visitTree(VisitContext visitContext, VisitCallback callback)) - erase variable (setRowKey(facesContext, null) in same function) - erase variable (doVisitChildren(VisitContext context, boolean visitRows)) - erase variable (visitTree(VisitContext visitContext, VisitCallback callback)) - backup variable (erases backed up value) (walk(FacesContext faces, DataVisitor visitor, Object argument)) - ... - restore value (restores null) (walk(FacesContext faces, DataVisitor visitor, Object argument)) - restore value (restores null) (in visitTree(VisitContext visitContext, VisitCallback callback)) etc. The problem can be solved by *stacking* backed up variables, instead of storing them in a simple attribute, to allow for any kind of reentrance. (I do not say that this is the best possible patch, but it has solved the problem for me). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (RF-11082) rich:graphValidator doesn't work with iterable object graph field inside nested composite components

by Joshua Brookes (JIRA)

rich:graphValidator doesn't work with iterable object graph field inside nested composite components ---------------------------------------------------------------------------------------------------- Key: RF-11082 URL: https://issues.jboss.org/browse/RF-11082 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-validators Affects Versions: 4.0.0.Final Reporter: Joshua Brookes There is a known issue with Graph Validator where it can only resolve a cloned object itself, but not variables derived from it ( uidata variables, c:set, alias etc ). If you need to validate variables in the iterator, a loop variable is needed to explicitly reference fields. This workaround does not work when used in nested composite components. Validation will not use the values input into the form when the bug occurs. This only happens when a class-level constraint exists on the class used int he iterable field. This JIRA is for the latter issue, but an issue should also be created for the original variant of the problem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (RF-11078) javax.faces.FacesException: Error send image

by Alessandro Arrigo (JIRA)

javax.faces.FacesException: Error send image -------------------------------------------- Key: RF-11078 URL: https://issues.jboss.org/browse/RF-11078 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tree Affects Versions: 3.3.3.Final Environment: firefox , chrome , ie Reporter: Alessandro Arrigo I have this errore when i used ie 7.6 java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0 at org.ajax4jsf.util.Zipper.unzip(Zipper.java:30) at org.richfaces.renderkit.html.images.TreeImageBase$TreeImageData.<init>(TreeImageBase.java:109) at org.richfaces.renderkit.html.images.TreeImageBase.getTreeImageData(TreeImageBase.java:94) at org.richfaces.renderkit.html.images.TreeLineNodeImage.paint(TreeLineNodeImage.java:47) at org.ajax4jsf.resource.Java2Dresource.getImage(Java2Dresource.java:116) at org.ajax4jsf.resource.Java2Dresource.send(Java2Dresource.java:89) My code is it: <rich:tree id="treeGaranzie" switchType="client" adviseNodeOpened="#{definizioneProdotto.isNodeOpenedGaranzie}" rowKeyVar="index"> <rich:treeNodesAdaptor id="sezioneTreeAdaptor" var="sezione" nodes="#{definizioneProdotto.beneCorrente.istanzaBene.sezioni}"> <rich:treeNode id="sezioneTreeNode"> <h:outputText value="#{sezione.descrizione}" /> <a4j:support event="onexpand" ajaxSingle="true"> <f:setPropertyActionListener value="${ext:treeRowKeyToIndex(index)}" target="#{definizioneProdotto.currentNodeIndex}" /> <f:actionListener binding="#{definizioneProdotto.actionListenerExpand}" /> </a4j:support> <a4j:support event="oncollapse" ajaxSingle="true"> <f:setPropertyActionListener value="${ext:treeRowKeyToIndex(index)}" target="#{definizioneProdotto.currentNodeIndex}" /> <f:actionListener binding="#{definizioneProdotto.actionListenerCollapse}" /> </a4j:support> </rich:treeNode> <rich:treeNodesAdaptor id="unitTreeAdaptor" var="unit" nodes="#{sezione.units}"> <rich:treeNode id="unitTreeNode" iconLeaf="/images/Blank.png"> <h:panelGrid columns="2" style="margin-right:0px;"> <h:panelGroup style="width:300px; display:block; text-align:left;"> <h:outputText value="#{unit.descrizione}" id="descrizioneGaranzia"> <rich:toolTip for="descrizioneGaranzia">#{unit.descrizioneEstesa}</rich:toolTip> </h:outputText> </h:panelGroup> <h:panelGroup style="width:70px; display:block; text-align:left;"> <h:selectBooleanCheckbox id="garanzia#{unit.codice}" value="#{unit.selezionata}" disabled="#{!unit.abilitata}"> <a4j:support ajaxSingle="true" id="selectUnit" event="onclick" disableDefault="true" action="processSelezioneUnit" reRender="treeGaranzie" status="commonStatus"> <f:param name="codiceSezione" value="#{sezione.codice}" /> <f:param name="codiceUnit" value="#{unit.codice}" /> <f:param name="pacchetto" value="#{unit.pacchetto}" /> </a4j:support> </h:selectBooleanCheckbox> <a4j:commandLink action="addGaranzieNext" rendered="#{unit.abilitata and unit.istanziabile and unit.multiIstanziabile}"> <f:param name="codiceBene" value="#{definizioneProdotto.beneCorrente.istanzaBene.codice}" /> <f:param name="codiceSezione" value="#{sezione.codice}" /> <f:param name="codiceUnit" value="#{unit.codice}" /> <f:param name="pacchetto" value="#{unit.pacchetto}" /> <h:graphicImage style="border:0;" title="#{pf.aggiungiGaranzia}" url="/images/Add.png" width="16px" height="16px" /> </a4j:commandLink> </h:panelGroup> </h:panelGrid> </rich:treeNode> </rich:treeNodesAdaptor> </rich:treeNodesAdaptor> </rich:tree> --------------- END ------------- This error is caused when i click on selectBooleanCheckbox but only when i used ie 7.6 meanwhile i used ie 8 or another browser this error not appear -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues July 2011