Slashdot Mirror

← Back to Stories (view on slashdot.org)

Geronimo 1.0 Milestone Build M1 Released

Posted by michael on from the take-the-plunge dept.

Dain Sundstrom writes "The Geronimo team is pleased to announce the availability of our first milestone release, 1.0 M1. M1 marks the first of many milestone releases to come. This milestone integrates the main container components: Geronimo, MX4J, Jetty, OpenEJB and ActiveMQ. It has been amazing to see our communities come together and show such strong support for Apache Geronimo. There is still much work to be done on this integration and we look forward to fostering more collaboration between our projects to create an even more unified M2. As this is our first release and bound to draw a lot of attention, we have put together a thorough set of release notes which detail the current state of Geronimo. We advise that this is simply a milestone release and is not for general use, nor is it any indication of a final release. Our goal with this release is to start out slowly with a base set of functionality and gather some initial feedback that we can incorporate into future milestones."

4 of 147 comments (clear)

  1. Ok great by krisp · · Score: 5, Insightful

    Nice, but what exactly does it DO? Thanks for all the information about how big a milestone it is, but don't you think some information on what it is would be useful?

  2. Annoying by N8F8 · · Score: 4, Insightful

    Dear ED: Please ensure authors give brief discription of obscure projects when submitting news of obscure projects.

    --
    "God fights on the side with the best artillery." - Napoleon, Marshal of France - speaking truth to power
  3. Re:hacked? by sakshale · · Score: 3, Insightful

    The joys of allowing fools to access a Wikki site.

    --
    For every problem there is a solution that is simple, obvious and wrong.
  4. Re:What it is ... by jlrobins_uncc · · Score: 3, Insightful

    But is is just like SQL. Each EJB container vendor has their own
    suite of extensions to the specs, 'cause the specs just don't let you do all that you need to do in the real world.

    Differences in SQL is one of the reasons for this. EQL is a horribly constricting query language. Sure, it hides the SQL-vendor's flavoring from you, but since it gives you such a limited view of even 'standard' SQL, it has to be avoided for non-trivial queries -- either through EJB-container specifc deployment files, or even down to handcoded SQL in prepared statements at the session bean layer.

    Show me a non-trivial enterprise application that sticks straight to the spec. I wish it could be done. Really. But my gut feel is that it is incomplete in parts, and way too wordy in other parts.

    At least there's xdoclet.