Answer the question
In order to leave comments, you need to log in
Does Tomcat support java 8? If not, what containers do they support?
At work I write under android, I decided to start writing my own client-server project. For server-side I decided to use java (preferably 8). Does Tomcat support java 8? Or advise a good container with java 8 support
Answer the question
In order to leave comments, you need to log in
As far as I remember, Tomcat 8 is recommended for Java 8. I ran Tomcat 8 under Java 8, deployed a fairly complex, complex application - it worked. I did not use it, because the first Java 8 feature tested did not work in JSF (the fault of the JSF libraries, not Tomcat itself). Well, plus my hosting only provides Tomcat 7 so far. So if it is possible to deploy Java 8 and Tomcat 8 in production, then why not?
About containers. Tomcat 8 is an excellent application server where you can deploy almost any application. But you will have to do this at the cost of independently integrating various frameworks into your application. For example, to deploy web services, you need to figure out how to do it, perhaps even deploy a web services "engine". But in JBoss (or WildFly) a lot of frameworks have already been deployed, and in order to deploy a web service, it is enough to add the necessary annotations to your sources, and the web services "engine" is already there.
In the simpler and lighter Tomcat, more effort is required to connect frameworks to your application, as in addition to directly connecting to the application, the deployment of the frameworks themselves is also required (usually this is not so difficult, and Google has everything).
The heavier JBoss has done some of the work for you, but that work comes at a price. Firstly, the stack of technologies and their versions is tightly tied to a specific version of JBoss: if you need to deploy a more recent version of a particular framework or even a library API, in most cases this is simply impossible. Or if your application is using some API-v2.jar, and JBoss is already actively using some API-v1.jar, then you will often need to dance with tambourines to solve compatibility problems. Plus settings: often, instead of the standard framework settings, you will have to deal with their JBoss version.
Thus, for complex applications, JBoss can give a faster start compared to Tomcat. But later, when the time comes after the start of specific settings and requirements, JBoss can lead to a dead end, or at least make it seriously "stall out of the blue"
I, perhaps, will advise Tomcat nevertheless
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question