This listener is since JSF 1.x supposed to be automatically registered by the jsf_core.tld tag library definition file. You can find it in the /META-INF folder of the JSF implementation JAR file. In case of Mojarra 2.1.3 (which you seem to be using according the logs), the listener is registered as follows from line 80 … Read more
Use a ResourceHandler instead of ServletContextHandler.
As Jan Bartel suggested, from Jetty: How to configure JSP: by adding the line below in the start.ini-file in Eclipse, it works fine. -Dorg.apache.jasper.compiler.disablejsr199=true
I think MAVEN_OPTS would be most appropriate for you. See here: http://maven.apache.org/configure.html In Unix: Add the MAVEN_OPTS environment variable to specify JVM properties, e.g. export MAVEN_OPTS=”-Xms256m -Xmx512m”. This environment variable can be used to supply extra options to Maven. In Win, you need to set environment variable via the dialogue box Add … environment variable … Read more
Setup the org.eclipse.jetty.servlets.CrossOriginFilter in your web app. Old question/answer on the topic: https://stackoverflow.com/a/8454168/775715 See Jetty Documentation Hub on CrossOriginFilter Use: Quick Start Grab yourself a copy of jetty-servlets.jar. Put the jetty-servlets.jar in your WEB-INF/lib Add the following to your WEB-INF/web.xml <filter> <filter-name>cross-origin</filter-name> <filter-class>org.eclipse.jetty.servlets.CrossOriginFilter</filter-class> <init-param> <param-name>allowedOrigins</param-name> <param-value>*</param-value> </init-param> <init-param> <param-name>allowedMethods</param-name> <param-value>GET,POST,HEAD</param-value> </init-param> <init-param> <param-name>allowedHeaders</param-name> <param-value>X-Requested-With,Content-Type,Accept,Origin</param-value> </init-param> … Read more
module-info.class is a Java9 (JPMS) feature. Jetty 9.4.9 (or newer) supports the new JAR file changes from Java 9. It does not matter what Runtime JVM you are using (Oracle Java 8, or even something like OpenJDK 11.0.3), if you are using those JEP-238 Multi-Release Jar files in your WebApp (or Server classloader) then you … Read more
Jetty 11 is based on Jakarta Servlet 5.0, which is part of Jakarta EE 9. Jakarta EE 9 underwent the “big bang” change (their name, not mine) to namespace and packaging, there is no longer a javax.servlet.* it is now jakarta.servlet.*. There is literally nothing in Jetty 11 that looks for javax.servlet.*. Some quick history … Read more
Two common techniques, presented here in a super simplified chatroom concept. Option #1: Have WebSocket report back its state to a central location @WebSocket public class ChatSocket { public Session session; @OnWebSocketConnect public void onConnect(Session session) { this.session = session; ChatRoom.getInstance().join(this); } @OnWebSocketMessage public void onText(String message) { ChatRoom.getInstance().writeAllMembers(“Hello all”); } @OnWebSocketClose public void onClose(int … Read more
So I’m running a similar setup, with an AWS box running openjdk-1.8.0.51. what solved it for me is to add bouncycastle as a provider like so: Add the bcprov-<verion>.jar to /usr/lib/jvm/jre/lib/ext Edit /usr/lib/jvm/jre/lib/security/java.security adding the following line to the list of providers: security.provider.6=org.bouncycastle.jce.provider.BouncyCastleProvider (I added it as the 6th entry but you can add higher … Read more
Jetty needs a working directory. Its search order for finding a work directory is as follows: If the WebAppContext has a temp directory specified, use it. If the ServletContext has the javax.servlet.context.tempdir attribute set, and if directory exists, use it. If a ${jetty.base}/work directory exists, use it (only valid for Jetty 9.1+) If a ${jetty.home}/work … Read more