Fact-checked by Grok 2 weeks ago

Jakarta Project

The Jakarta Project was an umbrella initiative of dedicated to the development and maintenance of solutions for the platform. Founded in 1999, it served as a collaborative hub for a diverse array of Java-related projects, fostering innovation in server-side technologies, web frameworks, and utilities during the early growth of the Java ecosystem. The project originated from code donations by , including early contributions that formed the basis of key components like the for Java Servlets and JavaServer Pages. Over its lifespan, the Jakarta Project incubated and hosted numerous subprojects that became foundational to Java development, such as —a servlet container that evolved from Sun's donated codebase and achieved widespread adoption for web application hosting—and , an MVC framework for building dynamic web applications that transitioned to independent status. Other notable efforts under its umbrella included utilities like for reusable Java components and tools like for , many of which addressed common needs in enterprise Java programming. In 2005, as part of the 's push for a flatter , Jakarta's subprojects began migrating to become standalone top-level Apache projects, join existing ones, or retire if no longer active. This transition process concluded with the project's full retirement on December 21, 2011, after which its resources were archived in the for historical preservation. The name "" was inspired by a meeting room at where initial Java community discussions occurred, reflecting the project's roots in collaborative open-source efforts. Although retired by , the moniker was later revived with permission in 2018 for the platform under the , which rebranded and evolved the former Java EE specifications into a vendor-neutral standard for cloud-native enterprise Java applications—but this represents a distinct initiative separate from the original Apache project.

History

Origins and Founding

The Jakarta Project originated from discussions in 1999 among representatives from , , and the Group, held in a conference room named "" at Sun's facilities in . These meetings focused on fostering collaboration to advance open-source technologies for web servers, ultimately leading to the project's formal establishment as a top-level Apache project later that year. The name "Jakarta" was chosen to honor the location of these pivotal sessions, reflecting the collaborative origins and Sun's practice of naming conference rooms after global cities. The founding purpose of the Jakarta Project was to develop and host open-source Java tools and libraries that complemented the Java 2 Platform, Enterprise Edition (J2EE), by providing community-driven implementations of key specifications under the . This initiative aimed to promote portability, open standards, and innovation in Java platform extensions, particularly for server-side applications, without competing directly with Sun's proprietary efforts. A key early milestone was the project's launch in October 1999, with an initial emphasis on web-related technologies such as servlet and JavaServer Pages (JSP) implementations. Sun contributed its reference implementations of these technologies to the community via the project, enabling broader adoption and development. Subprojects like emerged as early examples, serving as the reference servlet container and demonstrating the hosting model's potential for collaborative innovation.

Development and Restructuring

Following its founding in 1999, the Apache Jakarta Project experienced significant growth throughout the early , evolving from a handful of initial subprojects focused on Java server-side technologies to hosting over 20 diverse initiatives by the mid-. These subprojects encompassed tools for , testing frameworks, and utility libraries, reflecting the burgeoning demand for open-source Java solutions in enterprise environments. This expansion was driven by the project's role as an incubator for innovative Java components, attracting contributors and fostering collaborative development under (ASF). A pivotal moment in the project's development occurred in 2005, when the ASF approved a to flatten its organizational as part of a broader initiative to streamline and reduce bureaucratic layers across the . This restructuring aimed to empower mature subprojects with greater autonomy by transitioning them to independent top-level Apache projects, thereby enhancing efficiency and decision-making speed. Notable examples include (graduated in 2000 but emblematic of the trend), Apache Struts (graduated in 2004), and (which originated within and became a top-level project in 2003), allowing these components to operate without the umbrella oversight of . During this period of active incubation, subprojects such as and matured significantly, providing reusable libraries for common programming tasks and file manipulation, respectively. Commons, initiated in the early , offered foundational utilities like and that became staples in enterprise applications, while POI enabled Java-based handling of proprietary formats, promoting interoperability in . These developments contributed to Jakarta's widespread adoption, as the project's outputs integrated into major Java ecosystems and supported scalable, robust application development.

Retirement

The Jakarta Project was officially retired on December 21, 2011, by the board after determining that no active subprojects remained. This closure stemmed from the culmination of earlier restructuring efforts, in which viable subprojects had transitioned to independent top-level projects or been retired on an individual basis. For instance, the ORO and Regexp subprojects were retired in October 2010 and April 2011, respectively, due to lack of ongoing development. The retirement process included a final review by the Project Management Committee, which verified the project's overall inactivity and lack of future activity. Subsequently, the project's resources and archives were transferred to the Apache Attic to preserve its historical materials for reference. This event signified the conclusion of the Jakarta Project's role as a central for Java-related initiatives at , having incubated dozens of subprojects since its inception in 1999.

Organization and Governance

Project Management Committee

The (PMC) of the Jakarta Project served as its primary , composed of experienced committers selected through a meritocratic process. Members were nominated by existing PMC participants based on their sustained, valuable contributions to the project, with approval requiring a three-quarters majority vote among the committee, including at least three affirmative votes. This structure ensured that the PMC drew from individuals deeply invested in the project's success, operating under the Apache Software Foundation's (ASF) bylaws to maintain transparency and accountability. Key responsibilities of the included overseeing the strategic direction of the Jakarta Project and its subprojects, approving proposals for new initiatives, and ensuring compliance with ASF guidelines. The committee managed incubation processes for emerging subprojects through the Incubator, allocated resources to support development, resolved conflicts among contributors, and provided quarterly reports to the ASF Board on project progress and challenges. Major decisions, such as subproject graduation or structural changes, required via structured voting: binary issues needed a majority approval with a minimum of three positive votes and three-quarters of cast votes in favor, while matters sought broad community agreement, all conducted over a one-week period on public mailing lists to promote openness. Formed by the ASF Board in September 1999, the evolved alongside the project's expansion, emphasizing a merit-based model where rights and influence stemmed directly from contributions rather than formal titles. This approach fostered , with the guiding the project's growth from its early Java-focused efforts to a diverse umbrella of open-source tools by the mid-2000s. Post-2005 restructuring, the 's authority adapted to support the independence of graduated subprojects while retaining oversight for remaining activities until the project's retirement.

Development Processes

The Jakarta Project employed a collaborative development model centered on asynchronous communication and structured tools to facilitate contributions from a global community of developers. Discussions on technical aspects, such as source code modifications and feature proposals, primarily occurred via dedicated mailing lists, including [email protected], where developers exchanged ideas, shared patches, and resolved issues related to software development. Issue tracking was managed through Apache Bugzilla, which served as the central repository for reporting bugs, proposing new features, and monitoring progress, ensuring all changes were documented and prioritized effectively. Version control relied on CVS (cvs.apache.org) and Subversion (svn.apache.org) repositories, providing committers with write access while allowing anonymous read access to promote transparency and encourage external input. Releases followed the standardized Apache process, beginning with a proposal from the Release Manager outlining the scope, timeline, and testing requirements, followed by a community vote requiring at least three binding +1 votes and more positive than negative votes for approval. Once approved by the Project Management Committee (PMC) as the overseeing body, the release artifacts were signed using PGP keys to verify integrity and authenticity, with showstoppers tracked in a STATUS file until resolved by consensus. This cycle ensured rigorous validation and security in distributing stable versions. Community guidelines emphasized open participation, requiring all contributions to be submitted as patches via or developer mailing lists, subject to review and approval by existing committers to maintain code quality. Committers conducted thorough code reviews, focusing on functionality, adherence to best practices, and compatibility, while all committed had to include and be licensed under the 2.0, granting broad permissions for use, modification, and distribution. To support modular development across subprojects, the Jakarta Project adopted specific coordination mechanisms, including shared like the build tool, which standardized compilation and packaging processes while allowing independent evolution of components under the umbrella structure. This approach enabled efficient resource sharing without mandating uniform implementation details, fostering within a cohesive ecosystem.

Subprojects

Active Subprojects

As the Jakarta Project approached its in December 2011, four subprojects remained under its , having not yet graduated to independent status or been formally retired: the Byte Code Engineering Library (BCEL), Bean Scripting Framework (BSF), , and JMeter. These represented the final holdovers amid a broader trend of subproject transitions, with overall development activity diminishing significantly after , resulting in few commits or releases during the project's waning years. BCEL provided a toolkit for analyzing, creating, and manipulating , enabling developers to inspect and modify class files at a low level for tasks such as optimization and . Its last release under , version 5.2, occurred in November 2006, after which it received only sporadic maintenance until its transfer to in June 2011. BSF facilitated the embedding of scripting languages, such as or , within Java applications, allowing dynamic code execution and integration of scripts with Java objects for enhanced flexibility in enterprise environments. The framework's final release was version 3.1 in June 2010, with prior versions like 3.0 in October 2009, before it moved to in September 2011. Cactus served as an integration testing framework for J2EE applications, extending to simulate remote requests and test server-side components like servlets, EJBs, and filters in a distributed manner. It integrated seamlessly with for writing and running tests across client-server boundaries. The project's last release, version 1.8.1, was issued in January 2009, followed by retirement to the Attic in August 2011 due to lack of ongoing development. Apache JMeter functioned as a performance testing tool for web applications, supporting protocols for load, stress, and to measure response times and throughput under various conditions. It allowed of heavy loads on servers, networks, or objects to assess overall system behavior. JMeter's final releases under Jakarta were version 2.5.1 in October 2011 and 2.5 in August 2011, immediately preceding its elevation to a top-level project later that month.

Graduated and Independent Projects

The Jakarta Project facilitated the maturation of numerous subprojects, many of which graduated to become independent top-level Apache projects, especially following the 2005 restructuring of the to create a flatter and encourage for mature initiatives. This shift reduced administrative overhead and allowed successful projects to operate autonomously while retaining their open-source focus. Apache Ant, a build automation tool originally developed as a Jakarta subproject to simplify software builds using XML-based scripting, was among the earliest to graduate, achieving top-level status on November 18, 2002 and revolutionizing Java project automation by replacing cumbersome Makefiles with declarative targets and tasks. Similarly, Apache Commons emerged from Jakarta as a repository of reusable components, including utilities for logging, I/O operations, and collections; it transitioned to a top-level project in June 2007, establishing itself as a foundational library for Java developers seeking standardized utilities. Apache Maven, which began as a subproject within the effort to streamline build processes and dependency management, entered the in 2003 and graduated to top-level independence in 2003, introducing project object models (POMs) for enhanced comprehension and automation in ecosystems. , a for handling formats like Excel and Word, started as a subproject in 2002 and became a top-level project in June 2007, enabling robust document manipulation without dependencies. Apache Struts, an MVC framework for web applications that originated in Jakarta, graduated with honors to top-level status on March 18, 2004, providing a foundational structure for enterprise-level web development through its action-based architecture and integration with servlet containers. , the reference implementation of Java servlet and JSP technologies, evolved from roots and achieved independence as a top-level project in 2005, serving as the core in countless Java stacks. Other notable graduations include Apache Velocity, a templating engine that moved from Jakarta to top-level status in November 2006, supporting dynamic content generation in web and email applications; Apache , a component-oriented that transitioned from Jakarta subproject releases in the early 2000s to top-level independence around 2006; and Apache Turbine, a servlet-based framework for web applications that graduated to top-level in 2007 after originating in Jakarta. By 2011, over 20 such graduations had occurred, reflecting the project's role in nurturing high-impact Java tools toward maturity.

Legacy and Impact

Contributions to Java Ecosystem

The Jakarta Project significantly advanced the Java ecosystem through the development of foundational libraries and tools that addressed core needs in bytecode manipulation, web serving, and reusable utilities. A prime example is the Byte Code Engineering Library (BCEL), originally incubated under Jakarta and later transitioned to , which provides APIs for analyzing, generating, and transforming Java class files. BCEL has been widely utilized in the creation of compilers, code obfuscators, aspect-oriented tools like , and dynamic language implementations such as Cobertura, enabling developers to extend Java's capabilities at the bytecode level without proprietary dependencies. Beyond individual libraries, the project's subprojects fostered a robust for enterprise development, with offering a suite of reusable components for tasks like , , and that integrated seamlessly into applications. These outputs democratized access to high-quality, open-source tools, reducing reliance on vendor-specific solutions and promoting modular, maintainable code across diverse projects. For instance, components have been incorporated into numerous top-level projects and third-party frameworks, enhancing overall ecosystem interoperability. The Jakarta Project also played a pivotal role in community building within the Java space, drawing developers who contributed to its initiatives, thereby positioning as a vital center for Java innovation outside the control of or . This collaborative model encouraged distributed development practices that influenced subsequent open-source Java efforts, emphasizing and in project governance. In terms of standardization, subprojects like provided critical reference implementations for key J2EE specifications, including Java Servlet and JavaServer Pages (JSP), which ensured compatibility and portability for web applications across different environments. Tomcat's compliance with these standards facilitated the adoption of J2EE in enterprise settings by offering a lightweight, reliable servlet container that developers could use to test and deploy standards-based applications without full J2EE application servers. This influence helped solidify J2EE as a for server-side Java, supporting scalable web architectures in production systems.

Relation to Modern Initiatives

The adoption of the name "" by the in 2018 for the donated Java EE assets represents a naming coincidence with the Apache Jakarta Project, sharing only a thematic connection to development and no direct organizational or technical lineage. The selected "" through a community poll in February 2018, where it received over 64% of nearly 7,000 votes, evoking the historical significance of the Apache Jakarta Project as an early hub for open-source innovations without infringing on Oracle's "Java" trademark. The granted permission for the name's reuse, as the project had been retired in 2011, emphasizing the unrelated nature of the two initiatives beyond this shared nomenclature. Despite the lack of direct lineage, indirect influences persist through alumni technologies from the Apache Jakarta Project, such as , which forms the basis for servlet container implementations in -compatible servers like Eclipse GlassFish. Eclipse GlassFish, the for , incorporates a derived from Tomcat's architecture to handle servlet and JSP processing, enabling seamless integration of legacy web components into modern enterprise applications. This reuse highlights how foundational tools from the Apache era continue to underpin contemporary ecosystems. Following its retirement in December 2011, the Apache Jakarta Project's resources, including , documentation, and historical artifacts from its subprojects, were preserved in the Apache Attic, serving as an archival reference for developers studying deprecated Java tools or tracing the evolution of open-source Java practices. These materials remain accessible to inform current efforts, such as avoiding outdated dependencies in migrations, without active maintenance. While there is no formal successor relationship, the Apache Jakarta Project's model of incubating multiple collaborative subprojects under a unified open-source umbrella influenced the structure of Eclipse's EE4J top-level project during the 2017-2018 transition of Java EE assets from , promoting a similar vendor-neutral, community-driven approach to enterprise Java . This inspiration is reflected in EE4J's organization as a collection of modular projects, echoing Jakarta's role in fostering Java ecosystem growth.

References

  1. [1]
    The Jakarta Site - The Apache Jakarta™ Project -- Java Related ...
    Founded in 1999, the Jakarta Project housed a diverse set of popular open source Java solutions. In 2005, as a part of creating a flatter Apache Software ...Project Guidelines · Project Management Committee · Oro · Mailing Lists
  2. [2]
    Apache Tomcat® - Heritage
    In 2005, Tomcat became its own top-level Apache project, leaving the Jakarta umbrella and oversight structure to manage itself.Missing: origin | Show results with:origin
  3. [3]
    Apache Struts Framework - javaskool.com
    Jan 4, 2018 · Formerly located under the Apache Jakarta Project and known as Jakarta Struts, it became a top-level Apache project in 2005. The WebWork ...
  4. [4]
    Old Charter - Apache Commons
    Apache-Java and Jakarta originally hosted product-based subprojects, consisting of one major deliverable. The Java language however is package-based, and most ...Missing: history | Show results with:history
  5. [5]
    Jakarta | The Apache Attic
    Founded in 1999, the Jakarta Project housed a diverse set of popular open source Java solutions. In December 2011, Jakarta was retired as all of its subprojects ...Missing: history | Show results with:history
  6. [6]
    Frequently Asked Questions | the Future of Cloud Native Java
    In the early days of Java, the Apache Jakarta project was the home of many exciting innovations in the Java ecosystem. It was particularly instrumental in ...
  7. [7]
    NEWS: Jakarta Goes LIVE-Apache Mail Archives
    ... Apache Group (now the Apache Software Foundation) met in Cupertino CA in a conference room named "Jakarta". The topic of the meeting: How could we all ...Missing: founding | Show results with:founding
  8. [8]
    New Subproject proposal Config4J-Apache Mail Archives
    It was because Sun names their meeting rooms after different geographical places. The meetings about this project were held in the 'Jakarta' room. -jon ...
  9. [9]
    [INFO] Wired article about Sun's JavaServlet/Java Server hand over ...
    The free Web server group's Jakarta Project will integrate Sun's recently announced JavaServlet and JavaServer Pages technologies and make it available as open ...
  10. [10]
    Apache Ant™ Mission
    Apache Ant is a project of the Apache Software Foundation. It started as a subproject of the Apache Jakarta Project. This is the board resolution (from the ...
  11. [11]
    The Jakarta Site - News and Status
    18 March 2004 - Jakarta Struts' graduation with honors into Apache Struts. Jakarta Struts graduats with honors into Apache Struts - Jakarta Struts formed its ...
  12. [12]
    Welcome to Apache Maven – Maven
    Apache Maven is a build tool for Java projects. Using a project object model (POM), Maven manages a project's compilation, testing, and documentation.Download · Introduction · Maven Central Repository · Maven Plugins
  13. [13]
    Apache POI™ - Download Release Artifacts
    Apache POI became a top level project in June 2007 and POI 3.0 artifacts were re-released. Prior to that date POI was a sub-project of Apache Jakarta.History of Changes · The Apache Jakarta™ Project · Bin · Component OverviewMissing: history | Show results with:history
  14. [14]
    News and Status - 2011 Oct-Dec - The Jakarta Site
    Oct 26, 2011 · The Jakarta project was retired on Dec 21, 2011. JMeter became a top-level project on Oct 26, 2011, and JMeter 2.5.1 was released on Oct 3,  ...
  15. [15]
    Jakarta ORO | The Apache Attic
    Jakarta ORO retired in October 2010 and the move to the Attic was completed in October 2010. Jakarta previously hosted ORO, a set of text-processing Java ...
  16. [16]
    Jakarta Regexp
    As of 2011-04-17, the Regexp project is retired. This is an archived site. As there were no new features or releases planned in the future, the Jakarta ...
  17. [17]
    Project Management Committee Bylaws - The Jakarta Site
    The Apache Incubator is the primary source of new subprojects for Jakarta, though the PMC may choose to waive this if the Incubator PMC is agreeable. A ...
  18. [18]
    Roles and Responsibilities - The Jakarta Site
    This committee is the official managing body of the Jakarta Project and is responsible for setting overall project direction.Missing: composition | Show results with:composition
  19. [19]
    Mailing Lists - The Jakarta Site
    The "Developer" lists where you can send questions and comments about the actual software source code and general "development" types of questions. Some ...
  20. [20]
    The Jakarta Site - Bugs
    Apache projects track bugs, new feature ideas and other issues in one of two issue trackers: Bugzilla and JIRA. We take bugs very seriously.
  21. [21]
    Source Repositories - The Jakarta Site
    The Project's codebase is maintained in shared information repositories using either Subversion (svn.apache.org) or CVS (cvs.apache.org).Missing: control Git
  22. [22]
    Proposed Changes - Jakarta Project Guidelines - The Jakarta Site
    Public Release - Majority vote, if no showstoppers are listed in the status file. Showstoppers - Lazy consensus until resolved and removed from status file.Missing: PGP keys
  23. [23]
    Release Policy - The Apache Software Foundation
    For a release vote to pass, a minimum of three positive binding votes and more positive binding votes than negative binding votes MUST be cast. Releases may not ...
  24. [24]
    Signing Releases - The Apache Software Foundation - FTP
    This document describes the Apache release signing and checksum policy, answers questions related to this policy and gives a basic primer on the wider ...Missing: proposal | Show results with:proposal
  25. [25]
    Project Guidelines - The Jakarta Site
    Defines the methodology for proposing new top level Jakarta Subprojects. This is a living document. Changes can be made by the Project Management Committee.
  26. [26]
    Apache License, Version 2.0
    The 2.0 version of the Apache License, approved by the ASF in 2004, helps us achieve our goal of providing reliable and long-lived software products.Missing: Jakarta reviews
  27. [27]
    Jakarta Directory Layout - The Jakarta Site
    The docs/ directory contain most of the documentation for the Jakarta sub-project. ... All Jakarta projects are required to use ANT as their build tool.
  28. [28]
    Board Meeting Minutes - Jakarta - Apache Whimsy
    ... Apache Jakarta project is hereby terminated; and be it further RESOLVED ... * General We completed the moves of two subprojects to the Apache Attic: Jakarta ECS ...
  29. [29]
    News and Status - 2011 Apr-Jun - The Jakarta Site
    Jun 25, 2011 · JCS and BCEL moved to Apache Commons. The Jakarta Regexp project was retired due to lack of development activity.
  30. [30]
    News and Status - 2011 Jul-Sep - The Jakarta Site
    Sep 11, 2011 · The Jakarta BSF project has moved over to Apache ... Due to a lack of development activity, the Jakarta Cactus project has been retired.
  31. [31]
    News and Status - 2009 Jan-Mar - The Jakarta Site
    26 January 2009 - Apache Cactus 1.8.1 released. Version 1.8.1 of Apache Cactus has been released. For details of new features and fixes, please see the ...
  32. [32]
    https://projects.apache.org/project.html?jmeter
  33. [33]
    Apache JMeter - Apache Project Information
    2.5.1 final (2011-10-03): Apache Jakarta JMeter; 2.5 final (2011-08-17): Apache Jakarta JMeter; 2.4 final (2010 ...
  34. [34]
    Jakarta Slide | The Apache Attic
    Jakarta Slide retired in April 2010 and the move to the Attic was completed in October 2010. Jakarta previously hosted Slide, a content repository which could ...Missing: date | Show results with:date
  35. [35]
    The Jakarta Slide project
    As of 2007-11-03, the Slide project is retired. This site is kept online for archiving purposes. Due to the lack of a developer community, the codebase was ...Missing: date | Show results with:date
  36. [36]
    Board Meeting Minutes - Commons - Apache Whimsy
    ## Membership Data: Apache Commons was founded 2007-06-19 (17 years ago) There are currently 150 committers and 44 PMC members in this project. The Committer-to ...
  37. [37]
    Introduction - Apache Maven
    Maven, a Yiddish word meaning accumulator of knowledge, began as an attempt to simplify the build processes in the Jakarta Turbine project. There were several ...
  38. [38]
    Apache POI™ - Project History
    The POI project was dreamed up back around April 2001, when Andrew Oliver landed a short term contract to do Java-based reporting to Excel.Missing: subproject | Show results with:subproject
  39. [39]
    How It Works - Apache Velocity
    We have evolved into Top Level state from being a founding and long-time member of the Apache Jakarta Project and owe most of our rules and guidelines to the ...Missing: history graduation
  40. [40]
    https://turbine.apache.org/
  41. [41]
    About - Apache Tapestry
    Tapestry is released under the Apache Software License 2.0. Tapestry has a long history, with the oldest code dating back to January 2000. That means a lot ...Missing: Jakarta | Show results with:Jakarta
  42. [42]
    Apache Turbine - The Apache Software Foundation
    Apache Turbine is a servlet based framework that allows experienced Java developers to quickly build web applications.Missing: history | Show results with:history
  43. [43]
    https://commons.apache.org/
  44. [44]
    Byte Code Engineering Library (BCEL) - Apache Commons
    Oct 9, 2025 · To deal with the necessary class file transformations, we introduce an API that helps developers to conveniently implement their transformations.Missing: Jakarta usage
  45. [45]
    Apache Commons – Apache Commons
    Apache Commons is an Apache project focused on all aspects of reusable Java components. The Apache Commons project is composed of three parts.
  46. [46]
    [PDF] An Empirical Analysis of the Apache HTTP Server Project
    Project committee members are responsible for all aspects of managing an. Apache subproject including project plans and roadmaps, release schedules, etc. The ...<|control11|><|separator|>
  47. [47]
    Apache Tomcat® - Which Version Do I Want?
    Apache Tomcat® is an open source software implementation of a subset of the Jakarta EE (formally Java EE) technologies. Different versions of Apache Tomcat ...Tomcat Native · End-of-life · 2022-10-31 · 2018-06-30Missing: origin | Show results with:origin<|control11|><|separator|>
  48. [48]
    Java Basics: What Is Apache Tomcat? - JRebel
    Jan 18, 2024 · It's a production-ready Java development tool used to implement many types of Jakarta EE (formerly known as Java EE) specifications. Apache ...Missing: origin | Show results with:origin
  49. [49]
    Does GlassFish servlet container use that catalina? - Stack Overflow
    Oct 16, 2021 · According to this FAQ entry the Glassfish web container is a fork of Tomcat 5.5. Therefore it uses the same package names, although Tomcat's ...What is the difference between Tomcat, JBoss and Glassfish?Spring and tomcat or Spring and Glassfish - Stack OverflowMore results from stackoverflow.com
  50. [50]
    Which server will be better in a production environment, Glassfish or ...
    Nov 13, 2014 · GlassFish is an application server. Tomcat is a servlet container. Actually, GlassFish uses tomcat as it's servlet container.What's the difference between Glassfish and Apache Tomcat? Are ...What are the differences between JBoss, GlassFish, and Apache ...More results from www.quora.com<|separator|>
  51. [51]
    Re-introducing Jakarta EE: Eclipse takes Java EE back to its roots
    Feb 27, 2018 · Jakarta EE is named after Apache Jakarta, which was founded in 1999 and retired in 2011. “Those were roughly the dates when Java EE mattered ...