August 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13033) inputNumberSlider, inputNumberSpinner: @label is not working

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13033?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-13033. -------------------------------- Assignee: (was: Jiří Štefek) Resolution: Rejected It should work with any validator that h:input works with. Please open a new issue if you find it doesn't work as expected. > inputNumberSlider, inputNumberSpinner: @label is not working > ------------------------------------------------------------ > > Key: RF-13033 > URL: https://issues.jboss.org/browse/RF-13033 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, doc > Affects Versions: 3.3.2.CR1, 4.3.2, 5.0.0.Alpha1 > Reporter: Jiří Štefek > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > These two components have attribute @label. > And it doesn't work -- there is no sign of it on the page source. > Where should it be displayed? Should it replace the default value? > Or should this attribute be deleted? > Please also update the VDL-DOC in all cases. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12802) Move page fragments from repository qa to richfaces5

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12802: ------------------------------------ Is there any progress on this issue? It's blocking RF-12950. > Move page fragments from repository qa to richfaces5 > ---------------------------------------------------- > > Key: RF-12802 > URL: https://issues.jboss.org/browse/RF-12802 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Pavol Pitonak > Fix For: 5.0.0.Alpha2 > > > As discussed on community meeting on Feb 12, we should move page fragments for RichFaces components to richfaces5 repository so that they are distributed with framework. > We should find out how to prepare them so that they are easy to use for community members. RichFaces QE/dev need to test internals of components, community members will probably test only high-level functionality of components. One possible solution would be to create package "internal" in which there would be page fragments extending those from "public" package. QE team would then use "internal" implementations. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12949) Create a set of Photoalbum smoke tests which will verify it starts and that the basic features works

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12949?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12949: ------------------------------------ [~ppitonak] this should be done promptly considering that photoalbum will be included in WFK 2.4. > Create a set of Photoalbum smoke tests which will verify it starts and that the basic features works > ---------------------------------------------------------------------------------------------------- > > Key: RF-12949 > URL: https://issues.jboss.org/browse/RF-12949 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Assignee: Jiří Štefek > > The Photoalbum example should have a test which will make sure it starts correctly and basic functionality works as expected. -- 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, 7 months

1
0
0 / 0

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

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12916?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12916: ------------------------------- Labels: waiting_on_user (was: ) > a4j:push doesn't work in cluster and doesn't have an 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 > Labels: waiting_on_user > Attachments: proj_jms_rich.zip > > > 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, 7 months

1
0
0 / 0

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

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12916?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12916: ------------------------------------ [~luan.cestari] can you elaborate on the state of the sample you provided? What doesn't work about using clustered JMS with RichFaces push? > a4j:push doesn't work in cluster and doesn't have an 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 > Assignee: Lukáš Fryč > Attachments: proj_jms_rich.zip > > > 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, 7 months

1
0
0 / 0

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

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12916?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-12916: ---------------------------------- Assignee: (was: Lukáš Fryč) > a4j:push doesn't work in cluster and doesn't have an 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 > Attachments: proj_jms_rich.zip > > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12801) org.richfaces.resourceOptimization.enabled parameter with true value disables WebBeansELResolver to register in Websphere

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12801?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12801: ------------------------------- Assignee: (was: Lukáš Fryč) > org.richfaces.resourceOptimization.enabled parameter with true value disables WebBeansELResolver to register in Websphere > ------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12801 > URL: https://issues.jboss.org/browse/RF-12801 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.3.0.Final > Environment: Websphere 8.0.0.3 and Websphere 8.0.0.5, Windows 7, Richfaces 4.3.0.Final > Reporter: Erdem YILMAZ > Labels: ELResolver, optimization, resource, waiting_on_user, websphere > > when we use context param org.richfaces.resourceOptimization.enabled in web.xml, the CDI listener is not registered in Websphere. > resourcesOptimization parameter disables org.apache.webbeans.el.WebBeansELResolver in Websphere. In richfaces 4.2.3.Final version, resourceOptimization parameter do not affect the CDI behaviour. > we have disabled the resource optimization in order to work with richfaces but for the production environment, we prefer to enable it. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12801) org.richfaces.resourceOptimization.enabled parameter with true value disables WebBeansELResolver to register in Websphere

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12801?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12801: ------------------------------- Labels: ELResolver optimization resource waiting_on_user websphere (was: ELResolver optimization resource websphere) > org.richfaces.resourceOptimization.enabled parameter with true value disables WebBeansELResolver to register in Websphere > ------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12801 > URL: https://issues.jboss.org/browse/RF-12801 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.3.0.Final > Environment: Websphere 8.0.0.3 and Websphere 8.0.0.5, Windows 7, Richfaces 4.3.0.Final > Reporter: Erdem YILMAZ > Assignee: Lukáš Fryč > Labels: ELResolver, optimization, resource, waiting_on_user, websphere > > when we use context param org.richfaces.resourceOptimization.enabled in web.xml, the CDI listener is not registered in Websphere. > resourcesOptimization parameter disables org.apache.webbeans.el.WebBeansELResolver in Websphere. In richfaces 4.2.3.Final version, resourceOptimization parameter do not affect the CDI behaviour. > we have disabled the resource optimization in order to work with richfaces but for the production environment, we prefer to enable it. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12801) org.richfaces.resourceOptimization.enabled parameter with true value disables WebBeansELResolver to register in Websphere

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12801?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12801: ------------------------------------ [~sebcramer] can you reproduce this in tomcat with OpenWebBeans and MyFaces? If not, it sounds like a WebSphere issue, you should consider opening up a ticket with IBM. > org.richfaces.resourceOptimization.enabled parameter with true value disables WebBeansELResolver to register in Websphere > ------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12801 > URL: https://issues.jboss.org/browse/RF-12801 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.3.0.Final > Environment: Websphere 8.0.0.3 and Websphere 8.0.0.5, Windows 7, Richfaces 4.3.0.Final > Reporter: Erdem YILMAZ > Assignee: Lukáš Fryč > Labels: ELResolver, optimization, resource, websphere > > when we use context param org.richfaces.resourceOptimization.enabled in web.xml, the CDI listener is not registered in Websphere. > resourcesOptimization parameter disables org.apache.webbeans.el.WebBeansELResolver in Websphere. In richfaces 4.2.3.Final version, resourceOptimization parameter do not affect the CDI behaviour. > we have disabled the resource optimization in order to work with richfaces but for the production environment, we prefer to enable it. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13118) Combination of tabPanel and accordion results in Javascript error

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13118?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13118: ------------------------------- Fix Version/s: 5-Tracking > Combination of tabPanel and accordion results in Javascript error > ----------------------------------------------------------------- > > Key: RF-13118 > URL: https://issues.jboss.org/browse/RF-13118 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.3 > Environment: jdk1.7.0_21; apache-tomcat-7.0.42; Mojarra 2.1.24; Firefox; > Reporter: Alexey Shakov > Fix For: 5-Tracking > > > Test code: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > <html xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html" > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > <h:head> >  > </h:head> > <h:body> > <c:if test="#{testBean.activeItem==null}"> > <c:set target="#{testBean}" property="activeItem" value="tab1" /> > </c:if> > > <h:form id="form" prependId="false"> > <h:panelGroup id="pg"> > <rich:tabPanel activeItem="#{testBean.activeItem}" id="tabPanel"> > <rich:tab header="tab1" name="tab1" render="tabPanel"> > <rich:accordion switchType="client"> > <rich:accordionItem header="Item1"> > <a4j:commandLink value="show tab2" action="#{testBean.put('activeItem','tab2')}" render="pg" execute="@this"/> > </rich:accordionItem> > <rich:accordionItem header="Item2"> > <a4j:commandLink value="show tab2" action="#{testBean.put('activeItem','tab2')}" render="pg" execute="@this"/> > </rich:accordionItem> > </rich:accordion> > </rich:tab> > <rich:tab header="tab2" name="tab2"> > <a4j:commandLink value="back" action="#{testBean.put('activeItem','tab1')}" render="pg" execute="@this"/> > </rich:tab> > </rich:tabPanel> > </h:panelGroup> > </h:form> > > </h:body> > </html> > {code} > where testBean is a simple HashMap with session scope. > So, the page contains a tab-panel with two tabs. > First tab contains an accordion with some items. The accordion items have some menu-links inside. Click on one of this links causes second tab to be selected. -- 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, 7 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 August 2013