Great work Dain, I noticed you didn't include a lifecyle listener in web.xml, does that mean it's no longer used?
Could we just stipulate that OpenEJB's load on startup has to be a lower value than web apps that use OpenEJB? And are you saying that Tomcat 5.5 is now supported (with the agent)?? thanks again, Dario > I finally figured out how to integrate with Tomcat without the need > for an explicit installer stage. With the latest code, you simply > copy the openejb.war into the Tomcat webapps directory. That's it. > When the openejb.war starts, it will boot OpenEJB and process any > already running applications. Processing application is pretty cool > now. We simply deploy any EJBs and persistence units embedded in the > application and resolve any of the unresolved JNDI references in the > application. > > With the new system there are two cases where you still want to run > the installer: > > 1) If you have a servlet with load-on-startup _and_ this servlet uses > EJB or persistence units, you will need to run the installer to > assure that OpenEJB starts before the load-on-startup servlet is > created. > > 2) If you are on Java5 and using OpenJPA (the default JPA provider), > you will need to install the JavaAgent for anything but trivial JPA > clients. For example, the itests need the JavaAgent on Java5. > > > Basically, if you are on Java6 you most likely don't need to run the > installer, which makes using an IDE much easier. If you do want to > run the installer, just click the install button as before. > > I updated the files in my home directory if you want to try it out > (http://people.apache.org/~dain/openejb-temp/). > > -dain >
