February 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-11953) showcase - a4j:push - demos do not work on Tomcats

by Juraj Huska (JIRA)

Juraj Huska created RF-11953: -------------------------------- Summary: showcase - a4j:push - demos do not work on Tomcats Key: RF-11953 URL: https://issues.jboss.org/browse/RF-11953 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-push/poll, showcase Environment: container: Tomcat 6.0.32, Tomcat 7.0.20 app: RichFaces showcase 4.2.0.CR1 Reporter: Juraj Huska Priority: Critical The demos for a4j:push are not working at all. There is just error on firebug: {code} java.lang.RuntimeException: javax.servlet.ServletException: Throwable org.atmosphere.handler.ReflectorServletProcessor.onRequest(ReflectorServletProcessor.java:154) org.atmosphere.cpr.AsynchronousProcessor.action(AsynchronousProcessor.java:219) org.atmosphere.cpr.AsynchronousProcessor.suspended(AsynchronousProcessor.java:154) org.atmosphere.container.BlockingIOCometSupport.service(BlockingIOCometSupport.java:89) org.atmosphere.cpr.AtmosphereServlet.doCometSupport(AtmosphereServlet.java:1217) org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:1176) org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:1162) org.richfaces.webapp.PushFilter.doFilter(PushFilter.java:125) </pre>root cause <pre>javax.servlet.ServletException: Throwable org.atmosphere.util.AtmosphereFilterChain.doFilter(AtmosphereFilterChain.java:147) org.atmosphere.util.AtmosphereFilterChain.invokeFilterChain(AtmosphereFilterChain.java:116) org.atmosphere.handler.ReflectorServletProcessor$FilterChainServletWrapper.service(ReflectorServletProcessor.java:293) org.atmosphere.handler.ReflectorServletProcessor.onRequest(ReflectorServletProcessor.java:151) org.atmosphere.cpr.AsynchronousProcessor.action(AsynchronousProcessor.java:219) org.atmosphere.cpr.AsynchronousProcessor.suspended(AsynchronousProcessor.java:154) org.atmosphere.container.BlockingIOCometSupport.service(BlockingIOCometSupport.java:89) org.atmosphere.cpr.AtmosphereServlet.doCometSupport(AtmosphereServlet.java:1217) org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:1176) org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:1162) org.richfaces.webapp.PushFilter.doFilter(PushFilter.java:125) </pre>root cause <pre>java.lang.NoSuchMethodError: javax.servlet.ServletRequest.getServletContext()Ljavax/servlet/ServletContext; org.richfaces.webapp.PushHandlerFilter.getSessionManager(PushHandlerFilter.java:123) org.richfaces.webapp.PushHandlerFilter.doFilter(PushHandlerFilter.java:84) org.atmosphere.util.AtmosphereFilterChain.doFilter(AtmosphereFilterChain.java:139) org.atmosphere.util.AtmosphereFilterChain.invokeFilterChain(AtmosphereFilterChain.java:116) org.atmosphere.handler.ReflectorServletProcessor$FilterChainServletWrapper.service(ReflectorServletProcessor.java:293) org.atmosphere.handler.ReflectorServletProcessor.onRequest(ReflectorServletProcessor.java:151) org.atmosphere.cpr.AsynchronousProcessor.action(AsynchronousProcessor.java:219) org.atmosphere.cpr.AsynchronousProcessor.suspended(AsynchronousProcessor.java:154) org.atmosphere.container.BlockingIOCometSupport.service(BlockingIOCometSupport.java:89) org.atmosphere.cpr.AtmosphereServlet.doCometSupport(AtmosphereServlet.java:1217) org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:1176) org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:1162) org.richfaces.webapp.PushFilter.doFilter(PushFilter.java:125) {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

12 years, 10 months

3
8
0 / 0

[JBoss JIRA] (RF-11933) Push: user-friendly topics initialization on startup

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-11933: ------------------------------- Summary: Push: user-friendly topics initialization on startup Key: RF-11933 URL: https://issues.jboss.org/browse/RF-11933 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: core Affects Versions: 4.2.0.CR1 Reporter: Lukáš Fryč Currently, when custom threads (like JMS) out of {{FacesContext}} context tries to initialize {{PushContext}} e.g. by {{TopicsContext.lookup()}}, initializations fails with: {code} 11:12:39,189 ERROR [stderr] (MessageProducerThread) Exception in thread "MessageProducerThread" java.lang.ExceptionInInitializerError 11:12:39,191 ERROR [stderr] (MessageProducerThread) at org.richfaces.application.push.impl.PushContextFactoryImpl.getPushContext(PushContextFactoryImpl.java:89) 11:12:39,191 ERROR [stderr] (MessageProducerThread) at org.richfaces.application.push.TopicsContext.lookup(TopicsContext.java:79) 11:12:39,192 ERROR [stderr] (MessageProducerThread) at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:45) 11:12:39,192 ERROR [stderr] (MessageProducerThread) at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) 11:12:39,192 ERROR [stderr] (MessageProducerThread) at java.lang.Thread.run(Thread.java:662) 11:12:39,192 ERROR [stderr] (MessageProducerThread) Caused by: java.lang.NullPointerException 11:12:39,192 ERROR [stderr] (MessageProducerThread) at org.richfaces.application.push.impl.PushContextFactoryImpl.createInstance(PushContextFactoryImpl.java:74) 11:12:39,193 ERROR [stderr] (MessageProducerThread) at org.richfaces.application.push.impl.PushContextFactoryImpl.access$0(PushContextFactoryImpl.java:71) 11:12:39,193 ERROR [stderr] (MessageProducerThread) at org.richfaces.application.push.impl.PushContextFactoryImpl$PushContextHolder.<clinit>(PushContextFactoryImpl.java:43) 11:12:39,193 ERROR [stderr] (MessageProducerThread) ... 5 more {code} and then any other try for accessing context fails with: {code} 11:19:45,829 INFO [javax.enterprise.resource.webcontainer.jsf.context] (http--0.0.0.0-8080-4) Exception when handling error trying to reset the response.: java.lang.NoClassDefFoundError: Could not initialize class org.richfaces.application.push.impl.PushContextFactoryImpl$PushContextHolder at org.richfaces.application.push.impl.PushContextFactoryImpl.getPushContext(PushContextFactoryImpl.java:89) [richfaces-core-impl-4.2.0-SNAPSHOT.jar:] at org.richfaces.renderkit.PushRendererBase.getPushHandlerUrl(PushRendererBase.java:55) [richfaces-components-ui-4.2.0-SNAPSHOT.jar:] at org.richfaces.renderkit.html.PushRenderer.encodeEnd(PushRenderer.java:89) [richfaces-components-ui-4.2.0-SNAPSHOT.jar:] {code} ---- Users can initialize {{PushContext}} with {{web.xml}} param: * {{org.richfaces.push.initializeOnStartup}} ** we don't initialize on startup automatically, since not every app needs Push but current impl is quite a bit unfriendly, since it throws the exceptions above and do not get any solution. ---- I would recommend following improvements: * sensible default = automatically initialize on startup when {{org.richfaces.push.jms.enabled = true}} ** when user configures app to use Push JMS integration, it's clear he wants to use Push * log error with message describing how to use context-param {{org.richfaces.push.initializeOnStartup}} ** to allow user configure this option without need for studying documentation * throw application-specific unchecked exception (e.g. {{PushContextInitializationException}}) ** it will allow to handle these exceptions by application (waiting for initialization) * hold {{PushContext}} singleton reference in {{AtomicReference}} instead of in [static inner class|https://github.com/richfaces/core/blob/develop/impl/src/main/java/o...] ** allows app to initialize context once {{FacesContext}} available and do not fail with {{NoClassDefFoundError: Could not initialize class PushContextFactoryImpl$PushContextHolder}} -- 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

12 years, 10 months

1
4
0 / 0

[JBoss JIRA] (RF-11949) Exclude jquery.js from resource packaging

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-11949: ------------------------------- Summary: Exclude jquery.js from resource packaging Key: RF-11949 URL: https://issues.jboss.org/browse/RF-11949 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component Affects Versions: 4.2.0.CR1 Reporter: Lukáš Fryč Currently when you request {{jquery.js}} resource loaded (implicitly by rendering third-party component which depends on {{jquery.js}} or explicitly with {{<h:outputScript />}}), {{packed.js}} is renderer instead. It leads into errors when {{packed.js}} is loaded before {{jsf.js}} as in RF-11739. For RichFaces components, issue was solved in RF-11876, but page still can be broken. ---- I suggest to remove {{jquery.js}} from default packaging - we will get one more request, but we will achieve ability to rewrite {{jquery.js}} (leading into improved interoperability) and we will avoid issues which you mentioned. Currently resource dependency graph starts with {{javax.faces:jsf.js}} -> {{null:jquery.js}} -> ... so I don't see problem in excluding {{jquery.js}} from packaging since it shoudln't cause any other problems with resource dependency ordering. -- 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

12 years, 10 months

1
3
0 / 0

[JBoss JIRA] (RF-11939) Mobile Showcase - rich:contextMenu demo and "right click" action

by Jan Papousek (JIRA)

Jan Papousek created RF-11939: --------------------------------- Summary: Mobile Showcase - rich:contextMenu demo and "right click" action Key: RF-11939 URL: https://issues.jboss.org/browse/RF-11939 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: mobile, showcase Affects Versions: 4.2.0.CR1 Environment: iPhone 4.2.1 Reporter: Jan Papousek The description on rich:contextMenu demo page says: {quote} The context menu is invisable until triggered by a user action on the parent object. In this example, the context menu is displayed when one right-clicks on the image. {quote} The "right-click" action is not available (or it isn't common knowledge) on mobile devices. The demo should be: # updated for mobile devices or # excluded for mobile devices -- 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

12 years, 10 months

2
4
0 / 0

[JBoss JIRA] (RF-11938) Mobile Showcase - small font in a4j:actionListener demo

by Jan Papousek (JIRA)

Jan Papousek created RF-11938: --------------------------------- Summary: Mobile Showcase - small font in a4j:actionListener demo Key: RF-11938 URL: https://issues.jboss.org/browse/RF-11938 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: mobile, showcase Affects Versions: 4.2.0.CR1 Reporter: Jan Papousek Priority: Optional Text in "Messages" area in a4j:actionListener demo is really small on mobile devices. -- 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

12 years, 10 months

2
4
0 / 0

[JBoss JIRA] (RF-11931) The generated VDL doc should include a column displaying the default value of an attribute

by Brian Leathem (JIRA)

Brian Leathem created RF-11931: ---------------------------------- Summary: The generated VDL doc should include a column displaying the default value of an attribute Key: RF-11931 URL: https://issues.jboss.org/browse/RF-11931 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: cdk, doc Reporter: Brian Leathem -- 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

12 years, 10 months

2
9
0 / 0

[JBoss JIRA] (RF-11958) Menu item: ecss for drop down menu not rendered

by Pavol Pitonak (JIRA)

Pavol Pitonak created RF-11958: ---------------------------------- Summary: Menu item: ecss for drop down menu not rendered Key: RF-11958 URL: https://issues.jboss.org/browse/RF-11958 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu Affects Versions: 4.2.0.CR1 Environment: RichFaces 4.2.0-SNAPSHOT Mojarra 2.1.5-SNAPSHOT JBoss AS 7.1.0.CR1 OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux Chrome 16.0.912.77 @ Linux i686 Reporter: Pavol Pitonak When rich:menuItem is placed on the page without rich:dropDownMenu (see sample below), ECSS file for drop down menu is not rendered on page. However, menu item uses CSS classes from drop down menu, e.g. rf-ddm-itm, rf-ddm-itm-lbl, rf-ddm-itm-unsel, rf-ddm-emptyIcon ... {code:xml} <ui:composition template="template.xhtml"> <ui:define name="main"> <h:form id="menuForm"> <rich:toolbar id="menuBar" itemSeparator="disc" height="23px"> <rich:menuItem id="index" action="components/richAccordion/simple?faces-redirect=true" label="Accordion" /> <rich:menuItem id="table" action="components/richCalendar/simple?faces-redirect=true" label="Calendar" /> <rich:menuItem id="chart" action="components/richEditor/simple?faces-redirect=true" label="Editor" /> </rich:toolbar> </h:form> </ui:define> </ui:composition> {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

12 years, 10 months

2
3
0 / 0

[JBoss JIRA] (RF-11981) rich:meunItem should have it's own css file

by Brian Leathem (JIRA)

Brian Leathem created RF-11981: ---------------------------------- Summary: rich:meunItem should have it's own css file Key: RF-11981 URL: https://issues.jboss.org/browse/RF-11981 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-menu Reporter: Brian Leathem Assignee: Brian Leathem Fix For: 4.3-Tracking Currently, rich:menuItem uses the style sheet from rich:dropDownMenu, or rich:contextMenu. It should have it's styles defined in it's own style sheet. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-11980) Readme.txt is outdated

by Karel Piwko (JIRA)

Karel Piwko created RF-11980: -------------------------------- Summary: Readme.txt is outdated Key: RF-11980 URL: https://issues.jboss.org/browse/RF-11980 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: archetype Affects Versions: 4.2.0.CR1 Reporter: Karel Piwko Fix For: 4.2.0.Final The jar file distributed as a part of RichFaces 4.2.0.CR1 richfaces-4.2.0.CR1/archetypes/richfaces-archetype-simpleapp.jar contains outdated information in readme.txt: * RichFaces 4.0.0.Final ARCHETYPE PROJECT * Maven 2.1.0 or later (it should go 3.0 or later) * It references JBoss AS6, it should go for AS7/EAP6 -- 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

12 years, 10 months

2
2
0 / 0

[JBoss JIRA] (RF-11943) [a4j:commandLink] [a4j:queue] IE8 throws an js error if using an global queue within site

by Rene O (JIRA)

Rene O created RF-11943: --------------------------- Summary: [a4j:commandLink] [a4j:queue] IE8 throws an js error if using an global queue within site Key: RF-11943 URL: https://issues.jboss.org/browse/RF-11943 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.0.CR1 Environment: richfaces-4.2.0-SNAPSHOT, IE8 Reporter: Rene O Note, that this issue only occurs with IE8. This issue doesn't occur with richfaces-4.1.0.Final To reproduce this issue test the following site and click the a4j:commandLink {code:title=Testpage} <!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:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:a4j="http://richfaces.org/a4j" xmlns:rich="http://richfaces.org/rich" > <h:head> <title>JSF Test</title> </h:head> <h:body> <a4j:queue id="myQ" name="myQ" requestDelay="1200" ignoreDupResponses="true" /> <h:form id="myForm"> <a4j:commandLink id="myLink" value="myLink" /> </h:form> </h:body> </html> {code} The following error occurs: {code:title=JS Console Error within IE8} Meldung: Das Objekt unterstützt diese Eigenschaft oder Methode nicht. Zeile: 130 Zeichen: 17 Code: 0 URI: http://localhost:8080/jsftest/javax.faces.resource/richfaces-queue.js.jsf... {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

12 years, 10 months

4
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues February 2012