[JBoss JIRA] (RF-11991) NPE in ...push.impl.RequestImpl.onBroadcast()
by Juergen Zimmermann (JIRA)
Juergen Zimmermann created RF-11991:
---------------------------------------
Summary: NPE in ...push.impl.RequestImpl.onBroadcast()
Key: RF-11991
URL: https://issues.jboss.org/browse/RF-11991
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-push/poll
Affects Versions: 4.2.0.CR1
Environment: JBossAS 7.1.0 Web Profile
Reporter: Juergen Zimmermann
I'm using JBossAS 7.1 (Web Profile) via standalone (not domain). When there is no push event I'm getting a NPE (see stacktrace below).
These JARs are in WEB-INF/lib:
atmosphere-compat-jbossweb-0.8.4.jar
atmosphere-compat-jetty-0.8.4.jar
atmosphere-compat-tomcat-0.8.4.jar
atmosphere-compat-tomcat7-0.8.4.jar
atmosphere-compat-weblogic-0.8.4.jar
atmosphere-runtime-0.8.4.jar
web.xml is configured as follows:
<context-param>
<param-name>org.atmosphere.useBlocking</param-name>
<param-value>true</param-value>
</context-param>
Stacktrace:
18:50:47,754 Schwerwiegend [org.richfaces.log.Application] (http-localhost-127.0.0.1-8080-5) null: java.lang.NullPointerException
at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:124) [richfaces-core-impl-4.2.0.CR1.jar:4.2.0.CR1]
at org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663) [atmosphere-runtime-0.8.4.jar:0.8.4]
at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608) [atmosphere-runtime-0.8.4.jar:0.8.4]
at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584) [atmosphere-runtime-0.8.4.jar:0.8.4]
at org.atmosphere.cpr.AsynchronousProcessor.timedout(AsynchronousProcessor.java:379) [atmosphere-runtime-0.8.4.jar:0.8.4]
at org.atmosphere.container.BlockingIOCometSupport.suspend(BlockingIOCometSupport.java:148) [atmosphere-runtime-0.8.4.jar:0.8.4]
at org.atmosphere.container.BlockingIOCometSupport.service(BlockingIOCometSupport.java:92) [atmosphere-runtime-0.8.4.jar:0.8.4]
at org.atmosphere.cpr.AtmosphereServlet.doCometSupport(AtmosphereServlet.java:1217) [atmosphere-runtime-0.8.4.jar:0.8.4]
at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:1176) [atmosphere-runtime-0.8.4.jar:0.8.4]
at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:1162) [atmosphere-runtime-0.8.4.jar:0.8.4]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.10.Final.jar:]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:]
at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:]
at org.jboss.solder.servlet.exception.CatchExceptionFilter.doFilter(CatchExceptionFilter.java:65) [solder-impl-3.1.0.Final.jar:3.1.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:]
at org.jboss.solder.servlet.event.ServletEventBridgeFilter.doFilter(ServletEventBridgeFilter.java:74) [solder-impl-3.1.0.Final.jar:3.1.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:]
at com.ocpsoft.pretty.PrettyFilter.doFilter(PrettyFilter.java:126) [prettyfaces-jsf2-3.3.2.jar:]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.10.Final.jar:]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.10.Final.jar:]
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397) [jbossweb-7.0.10.Final.jar:]
at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.0.Final.jar:7.1.0.Final]
at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.10.Final.jar:]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.10.Final.jar:]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.10.Final.jar:]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.10.Final.jar:]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.10.Final.jar:]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.10.Final.jar:]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.10.Final.jar:]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_03]
--
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, 7 months
[JBoss JIRA] (RF-11995) autocomplete only displaying select popup on minChars + 1
by Brendan Healey (JIRA)
Brendan Healey created RF-11995:
-----------------------------------
Summary: autocomplete only displaying select popup on minChars + 1
Key: RF-11995
URL: https://issues.jboss.org/browse/RF-11995
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-input
Affects Versions: 4.2.0.CR1
Environment: Glassfish 3.1.1 / Mojarra 2.1.7 / Chrome browser
Reporter: Brendan Healey
I'm running the following test with org.richfaces.resourceOptimization.enabled
set to true.
After typing the minChars number of characters (2), I see an ajax request being
sent to the server and a response is successfully returned (observed using chrome
developer tools), but the popup selection list does not appear until minChars + 1
(3) characters are entered.
Typing the third character causes a get request for combo_list_shadow.png to be
sent.
<rich:autocomplete id="findSomething"
mode="cachedAjax"
var="var"
fetchValue="#{var.name}"
minChars="2"
autocompleteMethod="#{bean.doSearch}">
<rich:column>
<h:outputText value="#{var.name}"/>
</rich:column>
</rich:autocomplete>
I've only just migrated to rich:autocomplete from a self-developed custom component
so I don't know if this behavior existed in any richfaces version prior to 4.2.0.CR1.
I tried this on the showcase example here:
http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=autocom...
(in the first autocomplete on the page) and could not reproduce the behavior.
I tried using mode="ajax" and mode="client" and could not get the popup to show in
either case, although I'd only ever want to use cachedAjax mode normally.
--
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, 7 months
[JBoss JIRA] Created: (RF-10968) Tree: treeSelectionChangeListener and treeToggleListener do not work
by Pavol Pitonak (JIRA)
Tree: treeSelectionChangeListener and treeToggleListener do not work
--------------------------------------------------------------------
Key: RF-10968
URL: https://issues.jboss.org/browse/RF-10968
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-tree
Affects Versions: 4.0.0.Final
Environment: RichFaces 4.1.0-SNAPSHOT r.22458
Metamer 4.1.0-SNAPSHOT r.22459
Mojarra 2.0.3-
JBoss AS 6.0.0.Final
OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux
Chrome 11.0.696.57 @ Linux i686
Reporter: Pavol Pitonak
Attributes treeSelectionChangeListener and treeToggleListener in rich:tree do not work. However, attributes selectionChangeListener and toggleListener do work.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (RF-11975) Prototype script error in Portal
by Ken Finnigan (JIRA)
Ken Finnigan created RF-11975:
---------------------------------
Summary: Prototype script error in Portal
Key: RF-11975
URL: https://issues.jboss.org/browse/RF-11975
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: third-party
Affects Versions: 3.3.3.Final
Environment: GateIn v3.2
JBoss PortletBridge v2.2.0.Final
Firefox
Reporter: Ken Finnigan
Priority: Minor
When a user wants to add two separate portlets to the same portal page, with both portlets using RichFaces components, the JBoss PortletBridge needs to have the context parameter "org.jboss.portletbridge.WRAP_SCRIPTS" set to true. This wraps the RichFaces JavaScript files with a check to prevent the same file being loaded twice on the one page, as there are two portlets with RichFaces scripts being loaded.
In this situation, the prototype.js script (or framework_pack.js when LoadScriptStrategy is ALL) returns "$A() is not defined" within Firefox, but in Chrome and IE it works fine.
This JS error in Firefox can be resolved by moving the $A function to the very top of the file to ensure it is defined when needed.
--
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, 7 months