While the TomEE+ uses Apache MyFaces for JSF and Apache OpenJPA for JPA, the TomEE PluME uses Eclipse Mojarra for JSF and adds EclipseLink as a JPA option. TomEE PluME has everything TomEE+ offers but differs in two crucial APIs, JPA, and JSF. If you are not migrating from Glassfish to TomEE, you can ignore this distribution. TomEE PluME (pronounced plume) assists organizations that are migrating from Eclipse Glassfish to the Apache TomEE project. Here is a list of the APIs that are added by TomEE+: Java API for XML Web Services
#DIFFERENCE BETWEEN GLASSFISH AND TOMCAT FULL#
It also provides support for the full Jakarta Connectors specification so you can plug in any Jakarta Connector you might need. If you are using SOAP-based web services with XML messaging or the Java Message Service, then this is the solution for you. TomEE+ has everything in TomEE MicroProfie with the addition of three more specifications: JAX-WS, JEE Connectors, and JMS. Here are the MicroProfile specifications supported by TomEE MicroProfile: MicroProfile OpenTracing If you need support for MicroProfile in addition to Jakarta EE Web Profile, then this is the solution for you. TomEE MicroProfile adds full support for MicroProfile 1.3 to provide a complete and robust platform for implementing Java microservices. Jakarta Contexts and Dependency Injection Jakarta Debugging Support for Other Languages The TomEE WebProfile includes everything you would expect in the implementation of the Jakarta Web Profile including: Jakarta Servlet You should select this flavor of TomEE if you only need technologies defined in the Jakarta EE Web Profile and are not migrating from Eclipse Glassfish. TomEE WebProfile is a targeted implementation of the Jakarta EE Web Profile. The primary difference between the TomEE+ and the TomEE PluME is that TomEE PluME adds EclipseLink, and instead of using Apache MyFaces, it uses Eclipse Mojarra for JSF. Here you see that Jakarta Web Profile is the foundation of all the distributions, with each distribution adding more functionality. The others do the same but add support for MicroProfile, JMS, JAX-WS, Jakarta Connectors, and to help those porting applications from Glassfish to TomEE. TomEE WebProfile targets the complete Jakarta EE Web Profile. TomEE comes in four distributions: TomEE WebProfile, TomEE MicroProfile, TomEE+ and TomEE PluME. The use of Tomcat in conjunction with TomEE is explained in more detail in this blog post. It has, at its foundation, always been about adding Jakarta EE Web Profile (formerly Java EE) technologies to a complete Apache Tomcat distribution. The TomEE project has been evolving for twenty years. One that we hear from time to time is, “What is the difference between the different TomEE distributions?” This blog will answer that question. As a support company for TomEE and other projects, we get lots of questions from our clients some technical and others architectural.
0 kommentar(er)
