Lars Grefer

This part here seems to be the "problem": ``` java.lang.NoClassDefFoundError: jakarta/validation/ConstraintViolation at java.base/java.lang.Class.getDeclaredMethods0(Native Method) ~[na:na] at java.base/java.lang.Class.privateGetDeclaredMethods(Class.java:3402) ~[na:na] at java.base/java.lang.Class.getDeclaredMethods(Class.java:2504) ~[na:na] at com.sun.faces.util.Util.classHasAnnotations(Util.java:1255) ~[jakarta.faces-3.0.2.jar:3.0.2] at com.sun.faces.application.ApplicationInstanceFactoryMetadataMap.onPut(ApplicationInstanceFactoryMetadataMap.java:54) ~[jakarta.faces-3.0.2.jar:3.0.2] at com.sun.faces.application.ApplicationInstanceFactoryMetadataMap.onPut(ApplicationInstanceFactoryMetadataMap.java:27) ~[jakarta.faces-3.0.2.jar:3.0.2]...

I've opened https://github.com/eclipse-ee4j/mojarra/issues/5041 to see what the mojarra team thinks about this.

That depends on whether you are also using _Spring Web MVC_ and how you are deploying your application If you use Spring Web MVC you should have a look at...

The `PushContext` implementations of both MyFaces and Mojarra heavily depend on CDI.

`org.apache.myfaces.push.cdi.PushContextImpl` itself heavily depends on CDI.

You could try If `PushContext` works when including `org.joinfaces:weld-spring-boot-starter`

The problem is directly in the log: ``` [WARNING] bootstrap class path not set in conjunction with -source 8 [ERROR] warnings found and -Werror specified ```

I'm afraid JSF flows would need CDI, which isn't available by default in JoinFaces based applications. You could use spring-webflow or try to make it work using the starter for...

Seems like Omnifaces 3 or Weld can't handle the restart. We have to see if we can do something about that.

`5.2.1.RELEASE` seems to be the correct Framework version for JoinFaces 4.1.1. Can you provide an example project, which reproduces the issue?