Hi folks, Nuxeo has actually very little adherence to the Java EE specs. The only things we need from Java EE are JTA and JCA. And because we want Nuxeo to be able to run in non-Java EE containers, we have an optional module (nuxeo-runtime-jtajca) providing those when not available (using code from the Apache Geronimo project).
The result is that, provided the necessary deployment features are there, we can run out of the box in: - Full embedded (no container), - OSGi, - Jetty, - Tomcat, - JBoss. The important part in the above is "provided the necessary deployment features are there". Because Nuxeo has a specific modular extension model not available in any spec (see http://doc.nuxeo.com/display/NXDOC/Component+model+overview#Componentmodeloverview-ExtensionPoints), we need, for the Nuxeo Runtime to work, to plug into the container's startup and deployment model. For each container we need to write a small container-specific piece of code (nuxeo-jboss-deployer, nuxeo-runtime-jetty-adapter, nuxeo-runtime-tomcat-adapter) to be able to control the deployment order of our JARs, scan them, analyze what extension points are present, and inject their configuration in the Nuxeo Runtime. Now, of course we would like to work inside GlassFish v3, and at some point in the past we had a prototype module for it, but since no customer has ever wanted Nuxeo to run under GlassFish we couldn't put too many resources behind it. In the spirit of Open Source, if you want to contribute some code for your favorite platform, you'd be very welcome. In the meantime, you should really try Nuxeo under Tomcat (which is the platform we recommend for now). Florent --- Mailing list: [email protected] Forum: http://forum.nuxeo.org/f/1/
