jsf-2.3

A reconnecting websocket can't connect to the server with FacesContext.getCurrentInstance() being resolved to null

家住魔仙堡 提交于 2021-01-04 11:14:23
问题 I have a plain Tomcat 8.5.47 having the following dependencies installed. <dependency> <groupId>org.glassfish</groupId> <artifactId>javax.faces</artifactId> <version>2.3.9</version> </dependency> <dependency> <groupId>org.jboss.weld.servlet</groupId> <artifactId>weld-servlet</artifactId> <version>2.4.8.Final</version> </dependency> <dependency> <groupId>javax.websocket</groupId> <artifactId>javax.websocket-api</artifactId> <version>1.1</version> </dependency> CDI seems to work fine, or at

A reconnecting websocket can't connect to the server with FacesContext.getCurrentInstance() being resolved to null

霸气de小男生 提交于 2021-01-04 11:10:53
问题 I have a plain Tomcat 8.5.47 having the following dependencies installed. <dependency> <groupId>org.glassfish</groupId> <artifactId>javax.faces</artifactId> <version>2.3.9</version> </dependency> <dependency> <groupId>org.jboss.weld.servlet</groupId> <artifactId>weld-servlet</artifactId> <version>2.4.8.Final</version> </dependency> <dependency> <groupId>javax.websocket</groupId> <artifactId>javax.websocket-api</artifactId> <version>1.1</version> </dependency> CDI seems to work fine, or at

A reconnecting websocket can't connect to the server with FacesContext.getCurrentInstance() being resolved to null

╄→гoц情女王★ 提交于 2021-01-04 11:09:02
问题 I have a plain Tomcat 8.5.47 having the following dependencies installed. <dependency> <groupId>org.glassfish</groupId> <artifactId>javax.faces</artifactId> <version>2.3.9</version> </dependency> <dependency> <groupId>org.jboss.weld.servlet</groupId> <artifactId>weld-servlet</artifactId> <version>2.4.8.Final</version> </dependency> <dependency> <groupId>javax.websocket</groupId> <artifactId>javax.websocket-api</artifactId> <version>1.1</version> </dependency> CDI seems to work fine, or at

A reconnecting websocket can't connect to the server with FacesContext.getCurrentInstance() being resolved to null

陌路散爱 提交于 2021-01-04 11:08:20
问题 I have a plain Tomcat 8.5.47 having the following dependencies installed. <dependency> <groupId>org.glassfish</groupId> <artifactId>javax.faces</artifactId> <version>2.3.9</version> </dependency> <dependency> <groupId>org.jboss.weld.servlet</groupId> <artifactId>weld-servlet</artifactId> <version>2.4.8.Final</version> </dependency> <dependency> <groupId>javax.websocket</groupId> <artifactId>javax.websocket-api</artifactId> <version>1.1</version> </dependency> CDI seems to work fine, or at

A reconnecting websocket can't connect to the server with FacesContext.getCurrentInstance() being resolved to null

柔情痞子 提交于 2021-01-04 11:07:33
问题 I have a plain Tomcat 8.5.47 having the following dependencies installed. <dependency> <groupId>org.glassfish</groupId> <artifactId>javax.faces</artifactId> <version>2.3.9</version> </dependency> <dependency> <groupId>org.jboss.weld.servlet</groupId> <artifactId>weld-servlet</artifactId> <version>2.4.8.Final</version> </dependency> <dependency> <groupId>javax.websocket</groupId> <artifactId>javax.websocket-api</artifactId> <version>1.1</version> </dependency> CDI seems to work fine, or at

JSF 2.3 Websockets throw a NullPointerException when using PrimeFaces MenuItem with ajax=true

此生再无相见时 提交于 2020-06-29 04:15:38
问题 I get a NullPointerException when navigating on a PrimeFaces menu item with ajax = true when JSF 2.3 websockets are present in the pages. Below is the exception: java.lang.NullPointerException at com.sun.faces.push.WebsocketFacesListener.processEvent(WebsocketFacesListener.java:100) at javax.faces.event.SystemEvent.processListener(SystemEvent.java:123) at javax.faces.event.ComponentSystemEvent.processListener(ComponentSystemEvent.java:110) at com.sun.faces.application.applicationimpl.Events

Websocket CdiUtils NPE using <f:websocket />

笑着哭i 提交于 2020-06-27 16:39:14
问题 This application has been working fine in TC7, Spring 3, and JSF 2.2 but I wanted to add the push capabilities of JSF 2.3 so I upgraded to TC 9.0.8, Spring 5.0.5, and JSF 2.3.0 After some simple initial problems due to the upgrades The app deploys fine and Spring Security works (I can login) but then I get this error: May 11, 2018 2:24:06 PM com.sun.faces.application.view.FaceletViewHandlingStrategy handleRenderException SEVERE: Error Rendering View[/index.xhtml] java.lang

Why does the first AJAX call reset my view parameter?

那年仲夏 提交于 2020-05-29 08:43:53
问题 I cannot find out why the first ajax call causes the setter of my view parameter to be called again while every subsequent call does not call the setter again. I have the following simple view bean: package test; import java.io.Serializable; import javax.faces.view.ViewScoped; import javax.inject.Named; @Named @ViewScoped public class TestController implements Serializable { private static final long serialVersionUID = 1L; String param; public String getParam() { return param; } public void

Why does the first AJAX call reset my view parameter?

泄露秘密 提交于 2020-05-29 08:39:33
问题 I cannot find out why the first ajax call causes the setter of my view parameter to be called again while every subsequent call does not call the setter again. I have the following simple view bean: package test; import java.io.Serializable; import javax.faces.view.ViewScoped; import javax.inject.Named; @Named @ViewScoped public class TestController implements Serializable { private static final long serialVersionUID = 1L; String param; public String getParam() { return param; } public void

Why does the first AJAX call reset my view parameter?

巧了我就是萌 提交于 2020-05-29 08:39:18
问题 I cannot find out why the first ajax call causes the setter of my view parameter to be called again while every subsequent call does not call the setter again. I have the following simple view bean: package test; import java.io.Serializable; import javax.faces.view.ViewScoped; import javax.inject.Named; @Named @ViewScoped public class TestController implements Serializable { private static final long serialVersionUID = 1L; String param; public String getParam() { return param; } public void