September 2012 - richfaces-issues

[JBoss JIRA] Created: (RF-10473) Push: invalid 'Max re-connection reached.' error

by Nick Belaevski (JIRA)

Push: invalid 'Max re-connection reached.' error ------------------------------------------------ Key: RF-10473 URL: https://issues.jboss.org/browse/RF-10473 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-push/poll Affects Versions: 4.0.0.CR1 Reporter: Nick Belaevski Assignee: Nick Belaevski Fix For: 4.0.0.CR1 Open push-demo in Chrome & FF. Toggle arbitrary channel in Chrome in fast temp & many times -> Firefox stops receiving messages after some time, console contains 'Max re-connection reached.' message. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (RF-11081) Dynamically created tabs: tab switch doesn't work with switchType "ajax" or null

by Ján Jamrich (JIRA)

Dynamically created tabs: tab switch doesn't work with switchType "ajax" or null -------------------------------------------------------------------------------- Key: RF-11081 URL: https://issues.jboss.org/browse/RF-11081 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component Affects Versions: 4.0.0.Final Environment: RichFaces 4.1.0-SNAPSHOT r.22533 Metamer 4.1.0-SNAPSHOT r.22533 Mojarra 2.0.4-b09 Apache Tomcat 7.0.12 Java(TM) SE Runtime Environment 1.6.0_19-b04 @ Linux Chrome 12.0.718.0 @ Linux i686 Reporter: Ján Jamrich With swithType set to "ajax" or not set (null) tab switch doesn't work (tab don't get switched). With option "server" tab switching works, but another issue influences behavior. Its important note that this happens only for dynamically created tabs. (For statically created tabs works tab switching correctly). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

4
4
0 / 0

[JBoss JIRA] (RF-12401) ViewExpiredException caused by Queues

by Michael Heinen (JIRA)

Michael Heinen created RF-12401: ----------------------------------- Summary: ViewExpiredException caused by Queues Key: RF-12401 URL: https://issues.jboss.org/browse/RF-12401 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.2.Final Environment: myFaces 2.1.8 Tomahawk 6.0.35 Reporter: Michael Heinen a4j:queue does not work if number of views in session is set to 1. I assume that the viewState of queued requests is simply not updated correctly! org.apache.myfaces.NUMBER_OF_VIEWS_IN_SESSION must be set to 1. {code:xml} <a4j:queue name="myQueue" ignoreDupResponses="true" requestDelay="100"/> <h:inputText value="#{myController.expression}"> <a4j:ajax execute="@form" listener="#{myController.dummyListener}" event="keyup" render="expLength"> <a4j:attachQueue name="myQueue"/> </a4j:ajax> </h:inputText> {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

4
12
0 / 0

[JBoss JIRA] (RF-12437) Knowing at the startup time of RF, which compression/optimization is set/activated by the developer

by Jean ANDRE (JIRA)

Jean ANDRE created RF-12437: ------------------------------- Summary: Knowing at the startup time of RF, which compression/optimization is set/activated by the developer Key: RF-12437 URL: https://issues.jboss.org/browse/RF-12437 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.2.2.Final Environment: Any Reporter: Jean ANDRE In order to know which compression/optimization Richfaces is using (taking from the configuration file), it is possible to display at the console and/or at the log.INFO, all suitable information related to this topic ? Actually, we cannot know which optimization is setup and active or if the optimization options are correct. Like this RF confirms us what we have done or setup is active and correct. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

2
4
0 / 0

[JBoss JIRA] (RF-12342) RichFunction: warn user or fail when no component found for given clientId

by Lukáš Fryč (JIRA)

11 years, 6 months

2
5
0 / 0

[JBoss JIRA] (RF-12478) Re-structure CDK build

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12478: ------------------------------- Summary: Re-structure CDK build Key: RF-12478 URL: https://issues.jboss.org/browse/RF-12478 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: build/distribution Reporter: Lukáš Fryč Fix For: 4.3.0.Milestone2 According to diagram at: https://community.jboss.org/wiki/RichFaces43BuildRedesign It should not depend on RichFaces framework anymore. -- 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

11 years, 6 months

2
2
0 / 0

[JBoss JIRA] (RF-12375) iteration-demo doesn't work on TomEE - wrong persistence setup

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12375: ------------------------------- Summary: iteration-demo doesn't work on TomEE - wrong persistence setup Key: RF-12375 URL: https://issues.jboss.org/browse/RF-12375 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: examples Affects Versions: 4.3.0.Milestone1 Reporter: Lukáš Fryč I expect the problem is that we define DataSource using *-ds.xml file, which is special feature of AS7. Thus there is no such DS on TomEE. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

2
6
0 / 0

[JBoss JIRA] (RF-11584) Un-ignore TestCaptureEL and ValueExpressionAnalayserTest tests

by Lukáš Fryč (Created) (JIRA)

Un-ignore TestCaptureEL and ValueExpressionAnalayserTest tests -------------------------------------------------------------- Key: RF-11584 URL: https://issues.jboss.org/browse/RF-11584 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: tests - unit Affects Versions: 4.1.0.Milestone4 Reporter: Lukáš Fryč Priority: Critical Fix For: 4.1.0.CR1 When resolving RF-11544, it was necessary to ignore following tests in components module, because of changes in jsf-test to support org.jboss.spec.javax.faces:jboss-jsf-api_2.1_spec * validator/ui/src/test/java/org/richfaces/el/ValueExpressionAnalayserTest.java * validator/ui/src/test/java/org/richfaces/el/TestCaptureEL.java -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

5
10
0 / 0

[JBoss JIRA] (RF-12257) CDK: generating listener tags

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12257: ------------------------------- Summary: CDK: generating listener tags Key: RF-12257 URL: https://issues.jboss.org/browse/RF-12257 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: cdk Affects Versions: 4.2.0.Final Reporter: Bernard Labno -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

3
15
0 / 0

[JBoss JIRA] (RF-12309) CDK: naming conventions to avoid necessity write all the FQNs of classes in Renderer template and Component stub

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12309: ------------------------------- Summary: CDK: naming conventions to avoid necessity write all the FQNs of classes in Renderer template and Component stub Key: RF-12309 URL: https://issues.jboss.org/browse/RF-12309 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: cdk Affects Versions: 4.2.0.Final Reporter: Lukáš Fryč There are lot of bindings which needs to be manually hard-coded in order to make the component work: Look at sample of the calendar component: 1. [Renderer template|https://github.com/richfaces/components/blob/4.2.2.20120513-Fina...] 2. [Component interface|https://github.com/richfaces/components/blob/4.2.2.20120513-Fin...] ---- What could follow naming conventions? 1. *Renderer template* * {{<class>}} - use the package where the template resides in: {{calendar.template.xml}} -> {{CalendarRenderer}} * {{<superclass}} - use the {{<class> + Base}}: {{CalendarRenderer}} -> {{CalendarRendererBase}}, if not exists, use {{org.richfaces.renderkit.RendererBase}} 2. *component* {{org.richfaces.component.AbstractCalendar}} * component-type: {{org.richfaces.Calendar}} * component-family: {{org.richfaces.Calendar}} * generated class: {{org.richfaces.component.UICalendar}} * renderer: {{org.richfaces.CalendarRenderer}} * tag: {{@Tag(name = "calendar", handler = "org.richfaces.view.facelets.CalendarHandler")}} Some definitions what need to be configured per component library: e.g. prefix for component type/family/renderer, etc. Only classes which violates conventions would be necessary to configure specifically. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

2
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues September 2012