Apache Geronimo

Apache Geronimo
Name	Apache Geronimo
Developer	Apache Software Foundation
Released	2003
Latest release	3.0.1
Programming language	Java
Operating system	Cross-platform
License	Apache License 2.0

Apache Geronimo Apache Geronimo is an open source Java EE application server developed by the Apache Software Foundation, designed to run Java enterprise applications on platforms such as Linux, Microsoft Windows, macOS, Solaris, and IBM AIX. It integrates components from projects including Apache Tomcat, Eclipse Jetty, Apache ActiveMQ, Spring Framework, and Hibernate, aiming to support standards defined by the Java Community Process, the Java Platform, Enterprise Edition, and related specifications.

Overview

Apache Geronimo is a modular, server-side runtime that assembles and manages Java EE services, leveraging pluggable containers and service kernels drawn from projects like Apache Avalon, OSGi, Apache Commons, Apache Maven, and Apache Ant. The server targets enterprise deployment scenarios that involve integration with products such as Oracle Database, MySQL, PostgreSQL, Microsoft SQL Server, and middleware like JBoss and GlassFish in comparative evaluations. Geronimo emphasizes extensibility and standards alignment with communities represented by the Java Community Process, the Eclipse Foundation, and the Apache Software Foundation.

History and development

Initial efforts began in the early 2000s with contributions from organizations including IBM, Intel, Sony, Red Hat, and SpringSource under the stewardship of the Apache Software Foundation. Early releases incorporated components such as Apache Tomcat and Jetty while integrating management tooling familiar to developers from projects like Eclipse IDE and NetBeans. Over time, development tracked changes in the Java EE specifications, with milestones aligning to releases and votes within the Java Community Process and discussions in influential venues like the JavaOne conference. Corporate contributors and independent committers coordinated through the Apache Geronimo PMC and mailing lists, negotiating roadmap choices alongside adjacent projects including Apache ActiveMQ and Apache Camel.

Architecture and components

Geronimo's architecture is built around a kernel and GBeans, integrating container technologies such as Apache Tomcat, Eclipse Jetty, and Jetty Continuations for web profile functionality, and employing messaging via Apache ActiveMQ for JMS implementations. The server supports persistence layers through Hibernate, Java Data Objects, and JDBC drivers for relational systems like Oracle Database and MySQL. Management and deployment tooling integrate with IDEs and build systems including Eclipse IDE, IntelliJ IDEA, Apache Maven, and Apache Ant, while configuration and runtime concerns use concepts and libraries from OSGi and Apache Felix.

Features and standards compliance

Geronimo aimed to implement Java EE standards such as Java Servlet, JavaServer Pages, Enterprise JavaBeans, Java Transaction API, Java Message Service, and Java Persistence API as defined by the Java Community Process and the Java SE platform. It offered security features compatible with Java Authentication and Authorization Service, supported clustering and high availability patterns comparable to those in JBoss AS and GlassFish Server Open Source Edition, and provided administrative interfaces influenced by management frameworks like JMX and standards referenced by the Open Grid Services Architecture community. Integration with web services stacks included interoperability with Apache CXF and SOAP/WS-* specifications that are prevalent in enterprise interoperability scenarios discussed at events like WS-* panels.

Deployment and administration

Deployment and administration workflows leveraged tools and ecosystems such as Apache Maven for build and packaging, Jenkins and Hudson for continuous integration, and IDE plugins for Eclipse IDE and IntelliJ IDEA to support developers and operations teams familiar with practices presented at conferences like DevOpsDays and JavaOne. Runtime administration used JMX consoles and scripting utilities influenced by Apache Felix and OSGi management patterns; clustering and scalability strategies referenced patterns similar to those in HAProxy deployments and load balancing approaches documented by practitioners at LinuxCon and OpenStack sessions.

Community and governance

Project governance followed the Apache Software Foundation model with a Project Management Committee and meritocratic commit access drawn from contributors affiliated with organizations such as IBM, Red Hat, Intel, Sony, and independent participants who engaged through mailing lists and issue trackers during events like ApacheCon. Release decisions, security handling, and licensing were managed under ASF policies and overseen by volunteers coordinating with adjacent open source communities including Apache Tomcat, Apache ActiveMQ, Spring Framework, and Hibernate.

Adoption and notable uses

Geronimo saw adoption in academic, enterprise, and governmental contexts where organizations required a standards-compliant Java EE runtime; deployments were reported in institutions comparable to CERN-style research facilities, financial services deployments akin to systems used by Deutsche Bank-scale firms, and public sector projects with integration requirements similar to those at NASA centers. Comparative analyses and case studies often placed Geronimo alongside GlassFish, JBoss AS, Apache Tomcat, and commercial offerings from Oracle Corporation and IBM WebSphere when enterprises evaluated application server choices for interoperability, total cost of ownership, and compliance with Java EE roadmaps.

Category:Java enterprise platforms