April 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12922) rich:validator: only first message from multiple validation will appear

by Jiří Štefek (JIRA)

Jiří Štefek created RF-12922: -------------------------------- Summary: rich:validator: only first message from multiple validation will appear Key: RF-12922 URL: https://issues.jboss.org/browse/RF-12922 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-validators Environment: RichFaces 4.3.2-SNAPSHOT Metamer 5.0.0-SNAPSHOT JBoss AS 7.1.1.Final Java(TM) SE Runtime Environment 1.7.0_09-b05 @ Linux Firefox 18.0 @ Linux x86_64 Reporter: Jiří Štefek When an input is validated by e.g. 2 rules and the value put in it does not pass both validations, only one message is displayed to the client. Is it intention? Message components: rich:messages and rich:notifyMessages -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12921) rich:validator: created message is escaped, even if the message component should not be escaped

by Jiří Štefek (JIRA)

Jiří Štefek created RF-12921: -------------------------------- Summary: rich:validator: created message is escaped, even if the message component should not be escaped Key: RF-12921 URL: https://issues.jboss.org/browse/RF-12921 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-validators Environment: RichFaces 4.3.2-SNAPSHOT Metamer 5.0.0-SNAPSHOT JBoss AS 7.1.1.Final Java(TM) SE Runtime Environment 1.7.0_09-b05 @ Linux Firefox 18.0 @ Linux x86_64 Reporter: Jiří Štefek Priority: Minor On client side. The created message is always escaped, even if the message component has its attribute @escape=false. Message components: rich:message, rich:messages, rich:notifyMessage, rich:notifyMessages. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12920) rich:validator: and message(s) component with invalid or empty @for

by Jiří Štefek (JIRA)

Jiří Štefek created RF-12920: -------------------------------- Summary: rich:validator: and message(s) component with invalid or empty @for Key: RF-12920 URL: https://issues.jboss.org/browse/RF-12920 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-validators Environment: RichFaces 4.3.2-SNAPSHOT Metamer 5.0.0-SNAPSHOT JBoss AS 7.1.1.Final Java(TM) SE Runtime Environment 1.7.0_09-b05 @ Linux Firefox 18.0 @ Linux x86_64 Reporter: Jiří Štefek Validation on client side. When a message(s) component is using invalid or empty @for, then the component will show validation messages for all validated inputs. But when you submit the form (ajax/http) there will be no messages in this component. Message components: rich:message, rich:messages, rich:notifyMessage, rich:notifyMessages. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12688) Upgrade Guava from 11.02 to 13.0.1

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12688?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12688: ---------------------------- Issue Type: Component Upgrade (was: Bug) > Upgrade Guava from 11.02 to 13.0.1 > ---------------------------------- > > Key: RF-12688 > URL: https://issues.jboss.org/browse/RF-12688 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.3.0.M3 > Reporter: Juergen Zimmermann > Assignee: Lukáš Fryč > Fix For: 4.3.2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > The Guava version used by RF is 11.0.2. However, there is 13.0.1 (or even 14.0-rc1). -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12833) richfaces.js conflicts with prototype.js

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12833?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-12833 at 4/16/13 3:46 AM: ---------------------------------------------------------- The real problem is that inside richfaces.js module, there is two sorts of referenced to jQuery used: {{$}} and {{jQuery}}. We need to unify them at the first place. The reason why I hesitate to use {{$}} is that RichFaces itself defines [{{$}} reference internally as well|https://github.com/richfaces/richfaces5/blob/master/framework/src/ma...]. Even though it's namespaced I can see that like a reason why {{jQuery}} variable name was used instead of {{$}} originally. was (Author: lfryc): The real problem is that inside richfaces.js module, there is two sorts of referenced to jQuery used: {{$}} and {{jQuery}}. We need to unify them at the first place. The reason why I hesitate to use {{$}} is that RichFaces itself defines [{{$}} reference internally as well|https://github.com/richfaces/richfaces5/blob/master/framework/src/ma...]. Even though it's namespace I can see that like a reason why {{jQuery}} variable name was used instead of {{$}} originally. > richfaces.js conflicts with prototype.js > ---------------------------------------- > > Key: RF-12833 > URL: https://issues.jboss.org/browse/RF-12833 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.1 > Reporter: Mark Torres > Fix For: 5-Tracking > > Attachments: RF-12833.patch > > > Getting some javascript errors on richfaces.js. > Upon inspection, it is using > (function(jQuery, richfaces) { > ... > instead of > (function($, richfaces) { > ... -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12833) richfaces.js conflicts with prototype.js

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12833?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12833: --------------------------------- The real problem is that inside richfaces.js module, there is two sorts of referenced to jQuery used: {{$}} and {{jQuery}}. We need to unify them at the first place. The reason why I hesitate to use {{$}} is that RichFaces itself defines [{{$}} reference internally as well|https://github.com/richfaces/richfaces5/blob/master/framework/src/ma...]. Even though it's namespace I can see that like a reason why {{jQuery}} variable name was used instead of {{$}} originally. > richfaces.js conflicts with prototype.js > ---------------------------------------- > > Key: RF-12833 > URL: https://issues.jboss.org/browse/RF-12833 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.1 > Reporter: Mark Torres > Fix For: 5-Tracking > > Attachments: RF-12833.patch > > > Getting some javascript errors on richfaces.js. > Upon inspection, it is using > (function(jQuery, richfaces) { > ... > instead of > (function($, richfaces) { > ... -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12914) r:jquery - can not found this function

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12914?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12914: --------------------------------- This change seems to be caused by the fact that reverted patch RF-12738 fixed in 4.3.1.Final wasn't merged to 5.x: https://github.com/richfaces/components/commit/38fba5da33aff3e7943c8914a0... > r:jquery - can not found this function > -------------------------------------- > > Key: RF-12914 > URL: https://issues.jboss.org/browse/RF-12914 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 5.0.0.Alpha1 > Reporter: Juraj Húska > Fix For: 5.0.0.Alpha1 > > > The function from RF 4 {{rich:jQuery}} can not be found in RF 5. > There are {{r:jQuerySelector}} and {{r:jQueryObject}}. > Possible answer is that it was renamed to *jQueryObject* ? -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12916) a4j:push doesn't work in cluster and doesn't have a asynchronous way to notify all Topics (e.g. JMS)

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12916?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-12916 at 4/16/13 2:14 AM: ---------------------------------------------------------- Hey Luan, I don't understand the statement "a4j:push doesn't have a asynchronous way to notify all Topics such as JMS". Push (backed by Atmosphere) is not configured to work in cluster environment, thus each of the application instances is independent system. However each of the instances is also connected to JMS and subscribed to topics you are interested in. If you send a message to such topic, it will be delivered to all Push instances, which will notify all clients interested in (substribed to) particular topic. was (Author: lfryc): Hey Luan, I don't understand the statement "a4j:push doesn't have a asynchronous way to notify all Topics such as JMS". Push (backed by Atmosphere) is not configured to work in cluster environment, thus each of the application instances is independent system. However each of the instances is also connected to JMS and subscribed to topics you are interested in. If you update send a message to such topic, it will be delivered to all Push instances, which will notify all clients interested in (substribed to) particular topic. > a4j:push doesn't work in cluster and doesn't have a asynchronous way to notify all Topics (e.g. JMS) > ----------------------------------------------------------------------------------------------------- > > Key: RF-12916 > URL: https://issues.jboss.org/browse/RF-12916 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.Final > Reporter: Luan Cestari > > The customer is using JBoss in cluster and he have a Richfaces 4. The web client is using websocket using Richfaces/Atmosphere. The problem is that the customer have heavy asynchronous process that need to notify all websockets from all users (using a JMS, for example) -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12916) a4j:push doesn't work in cluster and doesn't have a asynchronous way to notify all Topics (e.g. JMS)

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12916?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-12916 at 4/16/13 2:14 AM: ---------------------------------------------------------- Hey Luan, I don't understand the statement "a4j:push doesn't have a asynchronous way to notify all Topics such as JMS". Push (backed by Atmosphere) is not configured to work in cluster environment, thus each of the application instances is independent system. However each of the instances is also connected to JMS and subscribed to topics you are interested in. If you send a message to such topic, it will be delivered to all Push instances, which will notify all clients interested in (subscribed to) particular topic. was (Author: lfryc): Hey Luan, I don't understand the statement "a4j:push doesn't have a asynchronous way to notify all Topics such as JMS". Push (backed by Atmosphere) is not configured to work in cluster environment, thus each of the application instances is independent system. However each of the instances is also connected to JMS and subscribed to topics you are interested in. If you send a message to such topic, it will be delivered to all Push instances, which will notify all clients interested in (substribed to) particular topic. > a4j:push doesn't work in cluster and doesn't have a asynchronous way to notify all Topics (e.g. JMS) > ----------------------------------------------------------------------------------------------------- > > Key: RF-12916 > URL: https://issues.jboss.org/browse/RF-12916 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.Final > Reporter: Luan Cestari > > The customer is using JBoss in cluster and he have a Richfaces 4. The web client is using websocket using Richfaces/Atmosphere. The problem is that the customer have heavy asynchronous process that need to notify all websockets from all users (using a JMS, for example) -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12916) a4j:push doesn't work in cluster and doesn't have a asynchronous way to notify all Topics (e.g. JMS)

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12916?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-12916 at 4/16/13 2:13 AM: ---------------------------------------------------------- Hey Luan, I don't understand the statement "a4j:push doesn't have a asynchronous way to notify all Topics such as JMS". Push (backed by Atmosphere) is not configured to work in cluster environment, thus each of the application instances is independent system. However each of the instances is also connected to JMS and subscribed to topics you are interested in. If you update send a message to such topic, it will be delivered to all Push instances, which will notify all clients interested in (substribed to) particular topic. was (Author: lfryc): Hey Luan, I don't understand the statement "a4j:push doesn't have a asynchronous way to notify all Topics". Push (backed by Atmosphere) is not configured to work in cluster environment, thus each of the application instances is independent system. However each of the instances is also connected to JMS and subscribed to topics you are interested in. If you update send a message to such topic, it will be delivered to all Push instances, which will notify all clients interested in (substribed to) particular topic. > a4j:push doesn't work in cluster and doesn't have a asynchronous way to notify all Topics (e.g. JMS) > ----------------------------------------------------------------------------------------------------- > > Key: RF-12916 > URL: https://issues.jboss.org/browse/RF-12916 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.Final > Reporter: Luan Cestari > > The customer is using JBoss in cluster and he have a Richfaces 4. The web client is using websocket using Richfaces/Atmosphere. The problem is that the customer have heavy asynchronous process that need to notify all websockets from all users (using a JMS, for example) -- 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

12 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues April 2013