He discusses the difficulties in writing an application server and some of the difficulties such a project faces, as well as discussing specific Geronimo project technical goals that required writing a new open-source application server in the first place: scalability, manageability, and configuration management are highlighted. A sidebar points out that the Apache License is used throughout Geronimo as a primary value-add, similar to the reasoning behind Apache's Harmony project. Both Geronimo and Apache share Geir Magnussen, Jr., as a project lead.
He also discusses Geronimo-specific jargon to enable developers to understand what elements go into the Geronimo server.
With IBM now employing many of the core Geronimo developers through their acquisition of GlueCode, Geronimo's development and documentation processes are likely to advance quickly. Already, for example, there's an Eclipse plugin for Geronimo available from IBM.
This has the potential to tilt the open-source application server market away from JBoss slightly, because of IBM's marketing. However, Geronimo is not certified as a J2EE application server yet.
What do you think are the long-term effects of all of this? Some have said Apache is being used by IBM to somehow wrest control of Java away from Sun. Do you think this is true? If so, what does it mean for Java, or for Apache?
- Jeremy Boynes on Geronimo, also from developerWorks