Intalio (Exolab) Halts J2EE OSS Support Except for Castor XML

Discussions

News: Intalio (Exolab) Halts J2EE OSS Support Except for Castor XML

  1. Intalio Inc., providers of the Exolab set of open source J2EE tools, has refocused its efforts on the emerging Business Process Management tools market, and has stopped supporting many of its popular OSS tools. OpenJMS, Tyrex, OpenORB, and OpenEJB have been released as active projects on sourceforge, while the popular CastorXML will still be hosted and supported at www.exolab.org.

    Announcement:
    --------------------------
    Dear Community,

    Intalio,Inc has over the past three years has initiated
    and sponsored a number of open source projects. These
    projects have matured and now used in a number of
    commercial products and bespoke projects undertaken
    by companies and individuals.

    Intalio,Inc focus has changed over this timeframe to
    focus on expanding the technologies in the area of
    Business Process Management (BPM), helping found BPMI.org,
    author the BPML specification and introduce a product
    Intalio|n3 (BPMS) into the marketplace.

    As we continue a strategy focused on delivering BPM
    products, we can no longer support all the open source
    projects with our limited resources. In the best interest
    of the open source community we would like to announce
    the following changes:


    OpenORB:
    We support the project on Sourceforge and recommend any
    contributors to contribute to this project.
    OpenORB will no longer be hosted on Exolab.
    http://sourceforge.net/projects/openorb

    OpenEJB:
    We support the project on Sourceforge and recommend any
    contributors to support this project.
    OpenEJB will no longer be hosted on Exolab.
    http://sourceforge.net/projects/openejb


    OpenJMS:
    We will move the project on Sourceforge and recommend any
    contributors to support this project.
    OpenJMS will no longer be hosted on Exolab.
    http://sourceforge.net/projects/openjms/


    Tyrex:
    We will move the project on Sourceforge and recommend any
    contributors to support this project.
    Tyrex will no longer be hosted on Exolab.
    http://sourceforge.net/projects/tyrex

    We will continue to support CastorXML as an open source
    project and host it on Exolab.

    The cvs, ftp, mail archives and web sites for the affected
    projects are being transferred over the next few days so
    you will notice some interruptions. You will have to
    subscribe to the mailing list on sourceforge and also
    change the CVS configurations that you are using.

    If you would like to get more actively involved with
    any of the projects please send an e-mail on the sourceforge
    mailing lists.

    We would like to thank all the contributors and supporters
    of the projects over the years who have made them a success.

    Regards,
    Ashish
    --------------------------------------------------------
    Ashish Agrawal ashish at intalio dot com
    VP. of Engineering, Intalio,Inc. www.intalio.com
    The Business Process Management Company
  2. Just an additional note, Castor JDO will stay at Exolab with Castor XML.
  3. Asish et al,

    My colleagues and I would like to express our heartfelt thanks to the outstanding efforts of Intalio and Intalio's open-source contributors, particularly on the Castor project.

    Fyi, we make extensive use of CastorXML throughout critical layers of our component-based application development and deployment framework.

    Bravo!

    Bob
    --
    Robert E. Newby

    Principal Software Engineer
    ViviPort, Inc.
    500 Edgewater Drive, 3rd Floor
    Wakefield, Massachusetts 01880 USA
    781-224-3646 | Bob_Newby at viviport dot com | www.viviport.com
  4. I was very confused while trying to figure out what Intalio
    is offering as a solution. Is their business process management system capable of orchestrating loosely coupled services into business processes?

    The only solution that is flexible enough that I've found so far is Collaxa's orchestration server using Scenario Beans.

    Jill.
  5. "OpenJMS", "OpenEJB" - won't those names fall foul of the same Sun lawyers that made the OpenJMX project change their name to MX4J?
  6. Certain Exolab projects had already left Exolab long before Intalio announced they could no longer support them. OpenORB was the first go.

    OpenORB community members began revolting in November 2001, disgruntled that the patches they were sending were not getting added to the public cvs. Contributors demanded full access to the open source version of OpenORB and control over its future.

    The conflict came to a breaking point in early January 2002 when Intalio issued an official statement acknowledging the contributions of the community over the previous four months, but further stating, “No new release has been done since the community views OpenORB as a stable project. As a stable project we foresee less releases based on number of contributions made.” The OpenORB community clearly demonstrated their views by immediately forking the project to souceforge.net and cutting a new release. The souceforge.net project is aptly titled “The Community OpenORB”. (http://openorb.sourceforge.net/)

    A mere ten days later, the Community OpenORB was joined by the OpenEJB project. OpenEJB founders Richard Monson-Haefel and David Blevins picked up the project and moved its base of operations to SourceForge as well. Mailing lists and cvs were moved, but the openejb.org domain, owned and controlled by Intalio, remained pointed at the broken and abandoned Exolab site for five months. Mr. Monson-Haefels’s own “Enterprise JavaBeans” book, which was on the shelves before the move, still referenced the Intalio controlled openejb.org. It wasn’t till the widely announced release of OpenEJB 0.8 beta 1, that people who had visited the openejb.org website realized the project was, in fact, not dead.
    (http://openejb.sourceforge.net/)

    In Intalio's announcement, Intalio precedented these changes in Exolab as being “In the best interest of the open source community....” Where exactly was this best interest six months ago when the changes actually happened? Regardless of Intalio’s misplaced best interest in the past, two very important questions remain about Intalio’s best interests for the open source community in the future.

    Will Intalio give up ownership of the domains that belong to these projects and will Intalio continue to own copyright over the hard work of contributors on projects they do not support?