...

It is now possible to deploy and run EJB apps that are not in a *.jar archive. For example, for ejb app located at:

/home/jsmith/myejbapp/META-INF/ejb-jar.xml

Simply add a Deployments declaration to the openejb.conf like the following:

<Deployment dir="/home/jsmith/myejbapp" />

Auto Deploy for Simple Apps

...

The speed of the Remote Server has been improved tremendously to compensate for differing default parameters for TCP Socket creation and closing in the Mac OSX Java VM. This makes sequential calls from a Remote Client to the Server several times faster.

Upgrade Notes

baz

Changelog

...

CMP Config Change

In 0.9.2 and before, the JDO database was using the private JNDI namespace of the very first CMP accessed to grab a datasource and hold onto it for use on all requests into the CMP container. This was configured with something like this:

   <database name="Global_TX_Database" engine="instantdb">
       <jndi name="java:comp/env/jdbc/basic/entityDatabase" />
       <mapping href="conf/default.cmp_mapping.xml" />
   </database>

This was just wrong. We've switched it so that the "jndi" tag of a Castor database.xml file can be set directly to the global JNDI name of a Connector element declared in an openejb.conf file.

   <database name="Global_TX_Database" engine="instantdb">
       <jndi name="java:openejb/connector/Default JDBC Database" />
       <mapping href="conf/default.cmp_mapping.xml" />
   </database>

This is still not so optimal as we do not want to people using OpenEJB's internal jndi and encourage people to become dependent on it. Newer releases of Castor allow for a completely programmatic way to configure a JDO database. In future releases, these global and local database files will go away all together! You will only need to specify your mapping.xml and will be able to pack it in your ejb jar.

ClassLoader change

In 0.9.2 all EJBs were added to the same classloader as the Containers, Server and all the other EJBs. In 1.0 beta1, all the EJBs are still in the same classloader, but one that is a child of the Container and Server. The code to keep each EJB jar in it's own classloader does exist, but limitations in the way we configure the CMP container with Castor prevent us from using it. When the CMP change made above is fixed, we will support separate classloaders for each EJB jar as an option.

Changelog