tomee

I am trying to enable CORS on my server. It hosts both an Apache HTTPD and an Apache Tomee. HTTPD is configured as: SetEnvIf Origin "^https://(.+\.)?my-domain.com$" allowed_origin=$0 Header always set Access-Control-Allow-Origin %{allowed_origin}e env=allowed_origin Header set Access-Control-Allow-Credentials "true" Header set Access-Control-Allow-Methods "GET, POST, OPTIONS, HEAD, PUT, DELETE, PATCH" Header set Access-Control-Allow-Headers "accept,x-requested-method,origin,x-requested-with,x-request,cache-control,content-type" Header set Access-Control-Max-Age "600" and my Tomee web XML :

I have a Jersey-based REST webservice which is working fine when deployed on Glassfish. When I deploy the same war file on Apache TomEE+ 1.6 version, i get the exception java.lang.IllegalAccessError: tried to access method com.sun.jersey.core.reflection.ReflectionHelper.getContextClassLoader()Ljava/lang/ClassLoader; from class com.sun.jersey.spi.scanning.AnnotationScannerListener com.sun.jersey.spi.scanning.AnnotationScannerListener.<init>(AnnotationScannerListener.java:89) com.sun.jersey.spi.scanning.PathProviderScannerListener.<init>(PathProviderScannerListener.java:59) com.sun.jersey.api

Whats the difference between service tomcat start/stop and ./catalina.sh run/stop in Tomcat or TomEE? Do they do exactly the same thing? catalina.sh run starts tomcat in the foreground, displaying the logs on the console that you started it. Hitting Ctrl-C will terminate tomcat. startup.sh will start tomcat in the background. You'll have to tail -f logs/catalina.out to see the logs. Both will do the same things, apart from the foreground/background distinction. Actually, startup.sh is quite small. If you inspect the file, you'll see that it in turn calls catalina.sh start . And in catalina.sh

I have just migrated to Tomcat 8. I used to work with system property org.apache.el.parser.COERCE_TO_ZERO=false so empty strings, numbers, booleans etc. are treated as null . In Tomcat 8, EL 3.0, it is supposed to be the default but it is in fact converting null string to empty string "" on JSF side. It is supposed to be a bug and it is supposed to be corrected but I'm not able to get it working in TomEE snapshot (Tomcat 8.0.27.0, MyFaces 2.2.8). BalusC This is a bug in the EL 3.0 specification. Since EL 3.0, as consequence of overzealous fix of JSP spec issue 184 , null will be coerced back

I'm using NetBeans 8.0.2 (also, tried it in the latest nightly build) and trying to start TomEE Plume server on port 8084 (tried it on different port too). Server starts and works fine, but NetBeans thinks it is not started and after approximately 2 minutes of waiting ("Waiting for Tomcat") throws an error window "Tomcat failed to start" or something like that. There are questions similar to mine with the difference that I have totally no errors, only "Tomcat failed to start" window, so I can't even put the log here as it says nothing useful. Also, available solutions are not working for me. I

I need to setup a Tomcat 8.5.x server version in Eclipse. When I try to create a server using Eclipse GUI, I get in Eclipse Luna as choice the latest version " Apache Tomcat v8.0 ". When I select it and I browse to my Tomcat 8.5.x server, I get this blocking error message: The Apache Tomcat installation at this directory is version 8.5.0. A Tomcat 8.0 installation is expected. The same error appears when trying TomEE 7.x, which is internally based on Tomcat 8.5. In Eclipse Neon the latest version as choice is " Apache Tomcat v9.0 " and it gives the same error. There isn't even a " Apache