April 2011 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-10949) UIAutocomplete <rich:validator> Event attribute could not be determined: null

by u j (JIRA)

UIAutocomplete <rich:validator> Event attribute could not be determined: null ----------------------------------------------------------------------------- Key: RF-10949 URL: https://issues.jboss.org/browse/RF-10949 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.0.0.Final Reporter: u j Priority: Minor On a autocomplete component with a rich:validator I get javax.faces.view.facelets.TagException: /search.xhtml @17,21 <rich:validator> Event attribute could not be determined: null at org.richfaces.view.facelets.html.AjaxHandler.resolveEventName(AjaxHandler.java:205) at org.richfaces.view.facelets.html.AjaxHandler.applyNested(AjaxHandler.java:192) at org.richfaces.view.facelets.html.AjaxHandler.apply(AjaxHandler.java:132) at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:131) at org.richfaces.view.facelets.html.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:55) at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:162) at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:114) at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:94) at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:131) at org.richfaces.view.facelets.html.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:55) at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:162) It seems to be the same issue as: https://issues.jboss.org/browse/RF-10573 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (RF-10937) Push: exception if address does not use sub-topic

by Nick Belaevski (JIRA)

Push: exception if address does not use sub-topic ------------------------------------------------- Key: RF-10937 URL: https://issues.jboss.org/browse/RF-10937 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-push/poll Reporter: Nick Belaevski When address does not include sub-topic, push fails with: Invalid filter: OR false AND __HQ_CID<>'ba97ff8b-6a0c-11e0-b8c4-005056c00008': org.hornetq.core.filter.impl.ParseException: Encountered "OR" at line 1, column 2. Was expecting one of: "TRUE" ... "FALSE" ... "NOT" ... "(" ... "-" ... "+" ... <INTEGER_LITERAL> ... <FLOATING_POINT_LITERAL> ... <SIMPLE_STRING> ... <IDENTIFIER> ... at org.hornetq.core.filter.impl.FilterParser.generateParseException(FilterParser.java:1472) [:6.0.0.Final] at org.hornetq.core.filter.impl.FilterParser.jj_consume_token(FilterParser.java:1352) [:6.0.0.Final] at org.hornetq.core.filter.impl.FilterParser.selectorFactor(FilterParser.java:179) [:6.0.0.Final] at org.hornetq.core.filter.impl.FilterParser.selectorTerm(FilterParser.java:137) [:6.0.0.Final] at org.hornetq.core.filter.impl.FilterParser.selectorExpression(FilterParser.java:115) [:6.0.0.Final] at org.hornetq.core.filter.impl.FilterParser.expression(FilterParser.java:106) [:6.0.0.Final] at org.hornetq.core.filter.impl.FilterParser.parse(FilterParser.java:59) [:6.0.0.Final] at org.hornetq.core.filter.impl.FilterParser.parse(FilterParser.java:39) [:6.0.0.Final] at org.hornetq.core.filter.impl.FilterImpl.<init>(FilterImpl.java:109) [:6.0.0.Final] at org.hornetq.core.filter.impl.FilterImpl.createFilter(FilterImpl.java:97) [:6.0.0.Final] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1325) [:6.0.0.Final] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:688) [:6.0.0.Final] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:354) [:6.0.0.Final] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:251) [:6.0.0.Final] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:471) [:6.0.0.Final] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:451) [:6.0.0.Final] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:412) [:6.0.0.Final] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:459) [:6.0.0.Final] at org.hornetq.core.remoting.impl.netty.HornetQChannelHandler.messageReceived(HornetQChannelHandler.java:67) [:6.0.0.Final] at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:100) [:6.0.0.Final] at org.jboss.netty.channel.StaticChannelPipeline.sendUpstream(StaticChannelPipeline.java:362) [:6.0.0.Final] at org.jboss.netty.channel.StaticChannelPipeline$StaticChannelHandlerContext.sendUpstream(StaticChannelPipeline.java:514) [:6.0.0.Final] at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:287) [:6.0.0.Final] at org.hornetq.core.remoting.impl.netty.HornetQFrameDecoder2.decode(HornetQFrameDecoder2.java:169) [:6.0.0.Final] at org.hornetq.core.remoting.impl.netty.HornetQFrameDecoder2.messageReceived(HornetQFrameDecoder2.java:134) [:6.0.0.Final] at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80) [:6.0.0.Final] at org.jboss.netty.channel.StaticChannelPipeline.sendUpstream(StaticChannelPipeline.java:362) [:6.0.0.Final] at org.jboss.netty.channel.StaticChannelPipeline.sendUpstream(StaticChannelPipeline.java:357) [:6.0.0.Final] at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274) [:6.0.0.Final] at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261) [:6.0.0.Final] at org.jboss.netty.channel.socket.oio.OioWorker.run(OioWorker.java:90) [:6.0.0.Final] at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [:6.0.0.Final] at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46) [:6.0.0.Final] at org.jboss.netty.util.VirtualExecutorService$ChildExecutorRunnable.run(VirtualExecutorService.java:181) [:6.0.0.Final] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24] at java.lang.Thread.run(Thread.java:680) [:1.6.0_24] 18:39:55,851 SEVERE [org.richfaces.log.Application] Invalid filter: OR false AND __HQ_CID<>'ba97ff8b-6a0c-11e0-b8c4-005056c00008' Encountered "OR" at line 1, column 2. Was expecting one of: "TRUE" ... "FALSE" ... "NOT" ... "(" ... "-" ... "+" ... <INTEGER_LITERAL> ... <FLOATING_POINT_LITERAL> ... <SIMPLE_STRING> ... <IDENTIFIER> ... : javax.jms.InvalidSelectorException: Invalid filter: OR false AND __HQ_CID<>'ba97ff8b-6a0c-11e0-b8c4-005056c00008' Encountered "OR" at line 1, column 2. Was expecting one of: "TRUE" ... "FALSE" ... "NOT" ... "(" ... "-" ... "+" ... <INTEGER_LITERAL> ... <FLOATING_POINT_LITERAL> ... <SIMPLE_STRING> ... <IDENTIFIER> ... at org.hornetq.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:287) [:6.0.0.Final] at org.hornetq.core.client.impl.ClientSessionImpl.internalCreateQueue(ClientSessionImpl.java:1627) [:6.0.0.Final] at org.hornetq.core.client.impl.ClientSessionImpl.createQueue(ClientSessionImpl.java:290) [:6.0.0.Final] at org.hornetq.core.client.impl.DelegatingSession.createQueue(DelegatingSession.java:283) [:6.0.0.Final] at org.hornetq.jms.client.HornetQSession.createConsumer(HornetQSession.java:577) [:6.0.0.Final] at org.hornetq.jms.client.HornetQSession.createDurableSubscriber(HornetQSession.java:481) [:6.0.0.Final] at org.richfaces.application.push.impl.jms.MessagingContext.createTopicSubscriber(MessagingContext.java:175) [:4.0.0.Final] at org.richfaces.application.push.impl.jms.SessionImpl.createSubscriptions(SessionImpl.java:119) [:4.0.0.Final] at org.richfaces.application.push.impl.jms.SessionImpl.subscribe(SessionImpl.java:235) [:4.0.0.Final] at org.richfaces.resource.PushResource.encode(PushResource.java:90) [:4.0.0.Final] at org.richfaces.resource.Use -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (RF-4222) Nice to have multiple events in a4j:support tag

by Jan Hoeve (JIRA)

Nice to have multiple events in a4j:support tag ----------------------------------------------- Key: RF-4222 URL: https://jira.jboss.org/jira/browse/RF-4222 Project: RichFaces Issue Type: Feature Request Reporter: Jan Hoeve Priority: Minor in the a4j:support tag, it is now possible enter an event for which you want to occur something (e.g. reRender): <a4j:support event="onblur" reRender="usernameDecorate"/> Sometimes it would be very userful if reRenders occur for multiple events. For example there are two events in which you are interesed: onblur and onkeyup. The onblur should check where a username containts valid characters (by using a regexp) The onkeyup should display the current length of the username (in an <h:outputText />) So, based on above example it would me nice if the support tag supported (hehe) more than one event). For example: <a4j:support event="onblur,onkeyup" reRender="usernameDecorate"/> I already tried to create a separate a4j:support for each event, but then only the first one is executed. -- 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

13 years, 9 months

5
5
0 / 0

[JBoss JIRA] Commented: (RF-7882) Tables: dynamic columns component

by Ilya Shaikovsky (JIRA)

[ https://issues.jboss.org/browse/RF-7882?page=com.atlassian.jira.plugin.sy... ] Ilya Shaikovsky commented on RF-7882: ------------------------------------- I have attached a simple RichFaces project(dataTable.zip) with the workaround inside. > Tables: dynamic columns component > --------------------------------- > > Key: RF-7882 > URL: https://issues.jboss.org/browse/RF-7882 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-tables > Reporter: Nick Belaevski > Assignee: Ilya Shaikovsky > Priority: Critical > Labels: design, tran > Fix For: 4.Future > > Attachments: dataTable.zip > > > Port of rich:columns from 3.x -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Assigned: (RF-7882) Tables: dynamic columns component

by Ilya Shaikovsky (JIRA)

[ https://issues.jboss.org/browse/RF-7882?page=com.atlassian.jira.plugin.sy... ] Ilya Shaikovsky reassigned RF-7882: ----------------------------------- Assignee: Jay Balunas (was: Ilya Shaikovsky) > Tables: dynamic columns component > --------------------------------- > > Key: RF-7882 > URL: https://issues.jboss.org/browse/RF-7882 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-tables > Reporter: Nick Belaevski > Assignee: Jay Balunas > Priority: Critical > Labels: design, tran > Fix For: 4.Future > > Attachments: dataTable.zip > > > Port of rich:columns from 3.x -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (RF-7882) Tables: dynamic columns component

by Ilya Shaikovsky (JIRA)

[ https://issues.jboss.org/browse/RF-7882?page=com.atlassian.jira.plugin.sy... ] Ilya Shaikovsky updated RF-7882: -------------------------------- Attachment: dataTable.zip > Tables: dynamic columns component > --------------------------------- > > Key: RF-7882 > URL: https://issues.jboss.org/browse/RF-7882 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-tables > Reporter: Nick Belaevski > Assignee: Ilya Shaikovsky > Priority: Critical > Labels: design, tran > Fix For: 4.Future > > Attachments: dataTable.zip > > > Port of rich:columns from 3.x -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (RF-10845) richfaces-showcase: implement Arrangeable model sample

by Ilya Shaikovsky (JIRA)

richfaces-showcase: implement Arrangeable model sample ------------------------------------------------------ Key: RF-10845 URL: https://issues.jboss.org/browse/RF-10845 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: examples Affects Versions: 4.0.0.Final Reporter: Ilya Shaikovsky Assignee: Ilya Shaikovsky Should not take long but that sample is critically important to learn our models. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
8
0 / 0

[JBoss JIRA] Created: (RF-8570) CDK code cleanup

by Alexander Smirnov (JIRA)

CDK code cleanup ---------------- Key: RF-8570 URL: https://jira.jboss.org/jira/browse/RF-8570 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: CDK Reporter: Alexander Smirnov Assignee: Alexander Smirnov Fix For: 4.0.0.ALPHA2 Review class and interface names, method names. Make all possible methods as final. Create Dependency Injection report using http://code.google.com/p/google-guice/wiki/Grapher Review logging, append log messages to the all critical points. JavaDoc comments. code style review. -- 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

13 years, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (RF-10950) richfaces 4 should be jdk 5 compatible.

by Ilya Shaikovsky (JIRA)

richfaces 4 should be jdk 5 compatible. --------------------------------------- Key: RF-10950 URL: https://issues.jboss.org/browse/RF-10950 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: compatibility Affects Versions: 4.0.0.Final Reporter: Ilya Shaikovsky Assignee: Nick Belaevski Priority: Critical -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (RF-10944) treeNode: expanded attribute evaluated fine only using EL

by Ilya Shaikovsky (JIRA)

treeNode: expanded attribute evaluated fine only using EL --------------------------------------------------------- Key: RF-10944 URL: https://issues.jboss.org/browse/RF-10944 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tree Affects Versions: 4.0.0.Final Reporter: Ilya Shaikovsky Priority: Minor http://community.jboss.org/message/601321#601321 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues April 2011