OpenEJB 0.8 Final Released


News: OpenEJB 0.8 Final Released

  1. OpenEJB 0.8 Final Released (17 messages)

    OpenEJB is an open-source, portable EJB container system and that can be plugged into any server environment including application servers, CORBA ORBs, Web servers, databases, etc. For example, OpenEJB is used in Apple computer's WebObjects. As of 0.8, OpenEJB comes with fast, lightweight EJB Servers for both Local and Remote access.

    Check out OpenEJB -- EJB Container System and EJB Server.

    More info
    OpenEJB comes with fast, lightweight EJB Servers for both Local and Remote access. That's right, deploy your EJBs into the container system, then just start the Remote EJB Server from the command line! Or, put OpenEJB in your class path and use it as an embedded library through the Local EJB Server.

    Release 0.8 Final available at

    Threaded Messages (17)

  2. OpenEJB 0.8 Final Released[ Go to top ]

    That is a good message.
  3. OpenEJB 0.8 Final Released[ Go to top ]

    Thanks for the kind words. We work very hard, feedback like this is rejuvenating.

    Have you been following OpenEJB long?
  4. OpenEJB 0.8 Final Released[ Go to top ]

    Have you been following OpenEJB long?

    Because of my JMS profession I've mostly watched your cousin, OpenJMS. In fact, I thought that OpenEJB was dead. But now it seems to be alive with a very good concept behind. I'll join your list. See you there!

    -- Andreas
  5. OpenEJB 0.8 Final Released[ Go to top ]

    We get that a lot. We moved to SourceForge in January, that threw people for a loop. Also, we don't control the domain name. Intalio owns that. They announced in June that they are no longer supporting the Exolab projects anymore (except castor) and that they have moved to SourceForge. But it seems they haven't yet decided what to do with the domain names.

    I have good faith Intalio will do the right thing. Though Intalio has dropped support for the project, OpenEJB is very grateful for the two years of solid support and resources they dedicated to the project.

  6. OpenEJB 0.8 Final Released[ Go to top ]

    I can't understand why the hell people waste their time on JBoss. For deployment because it's free? I have never heard of anyone deploying serious commercial apps on JBoss.
    For development? Why? This thing has a very poor documentation so I can't understand why someone would waste his precious time on it. They released 3.0 some months ago but there is still no documentation in sight. If they were wise people, they would be writing the docs along side development so both get released at the same time.

    If you need a container for development purposes, I urge you to choose one of the more serious containers such as IBM's Websphere or Oracle's OC4j. They are well documented and are free for development purposes. Maybe you should also have a look at OpenEJB. It is also well documented.
  7. OpenEJB 0.8 Final Released[ Go to top ]

    Jboss has been around longer. big community.helpful members. great support. several releases -- all solid. great forums. helpful user mailinglist. solid. fun!

    hope that answers why I like jboss
  8. OpenEJB 0.8 Final Released[ Go to top ]

    For the record, OpenEJB has been around since Dec. 1999.

    OpenEJB has a strong community and community spirit. We work very hard to answer questions and perfect our software. It's something people notice right away. The following comment from our user list this week says it nicely.

        "I'm pleased with the quickness and depth of the responses from the OpenEJB team to my posts on this list."
  9. Related projects...[ Go to top ]

    Related projects:

  10. Related projects...[ Go to top ]

    What is the difference between OpenEJB and JBOSS?
  11. What is the difference between OpenEJB and JBOSS?

    Pluggable container vs app server.

    I like that idea, however, I don't know what happens whether I don't have a JTA, for instance. Is there a light weight JTA included to drive XA tx? Ok, I should take a look at the docs...

    -- Andreas
  12. Related projects...[ Go to top ]

    OpenEJB uses Tyrex, just like Tomcat.

    On that note, both Tomcat and OpenEJB are embeddable, so you would stick 'em together and embed them both into Ant or Eclipse, for example.

    You could also embed OpenEJB right into your EJB application while you were developing and debugging (done with the Local Server). Then you could step all the way through your client code, into the container, into your bean code, and all the way back. No need for remote debugging tools or starting and stopping external processes.

    Once you get your app and beans the way you like them, just start the Remote Server. OpenEJB will startup in standalone mode and your remote clients will be able to access your beans.

    We run our test suite exactly like I described. First, we run our test ejbs and application against the Local Server. This is just one process, the application's process. The first time a client app makes a 'new InitialContext(...)' call, OpenEJB and the Local Server are automatically started inside the client's VM (pretty neat). The whole embedded part happens automatically. So our test ejbs and application are actually a standalone application in this case.

    Secondly, we start OpenEJB as a standard vanilla EJB server using the OpenEJB Remote Server. Then we change the JNDI properties of our test application to point to the Remote Server IP and Port, and run the tests again in client/server mode. To make the switch between servers, we just have to change the JNDI properties we use to get our InitialContext.
  13. Related projects...[ Go to top ]


    Background of my JTA questions was an idea to use the container inside SwiftMQ. Just wrap a Swiftlet around OpenEJB and it runs inside a router. We provide an intraVM JMS client anyway for the next release so MDBs could (once you provide EJB 2.0) run inside SwiftMQ.

    However, this is just an idea I had after I read your announcement. It would probably require more work to embed it, e.g. it should use SwiftMQ's thread pools, logging, etc.

    -- Andreas
  14. Related projects...[ Go to top ]


    That's a great way to use OpenEJB. You're right inline with the vision of the project. We are designed to be embedded, as such all the related parts we use are pluggable too; Transaction, Security, Resource Managers, Logging, you name it. So integrators can replace them with their own parts. Users can remove what they don't want or plug-in alternate implementations.

    The way you configure OpenEJB is pluggable too, so you can swap it with other implementations. We have two of those at the moment, Apple is still using and maintaining our original one, and we have a newer one that ships as the default in our own releases--the two have different file structures and syntax. The newer one is very simple for users.

    But here's the real fun part. Our servers are just client-server wrappers around the container system. We have a wrapper (server) for same-vm invocations, a wrapper for vanilla client/server invocations, and an wrapper that creates stubs and ties and exports them to a CORBA ORB for RMI-IIOP. People/vendors can use one of the existing wrappers or write their own. In the case of Apple and WebObjects, they kind of did both. They used our existing RMI-IIOP wrapper, but have recently rewritten it and will be donating it back to us. That will ship with OpenEJB 0.9.

    I recommend you hop on our development list and say hi.

    NOTE TO USERS; don't worry, you don't need to know any of this to use OpenEJB. You just unpack your distribution and type 'openejb start' to start the server and 'openejb deploy' to deploy, very simple. But if someday you have the need for more control, it's there.

  15. Related projects...[ Go to top ]

    What is the difference between OpenEJB and JBOSS?

    > Pluggable container vs app server.

    FWIW, JBoss is also a pluggable container. That's kind of the idea behind a highly modularized kernel-oriented architecture. You can either plug your stuff into it, or JBoss into your stuff. Either works.

  16. Related projects...[ Go to top ]

    FWIW, JBoss is also a pluggable container.

    Really? I'm sure you mean that I should write an MBean (or use one) to plug it into SwiftMQ. And another MBean to bridge our thread pools somewhere into the container. Same with logging, tracing, JNDI, etc.

    The big difference is that OpenEJB seems to be *only* a pluggable container with clean interfaces and docs and all that. I'll definitively check that out.
  17. OpenEJB 0.8 Final Released[ Go to top ]

    What is the advantage in using OpenEJB over the other range of open/developer source EJB containers on the market?
  18. Hi!

    What has always surpised me much with JBoss/Tomcat and JBoss/Resin integration was that I could have ONLY ONE GLOBAL JNDI namespaces shared by all web-apps.

    Can OPEN EJB be better integrated with Tomcat/Resin other web containers to follow along J2EE lines?