You should choose between JAX-RS or CMIS. Btw, CMIS is using JAX-RS for the rest implementation. CMIS provides a standardized way to interop. with repositories but it is not covering all specific functionality of Nuxeo. In time the Nuxeo Core will align with CMIS specifications so that more and more functionality will be exposed through CMIS. But anyway there are some specific Nuxeo aspects that will never be provided through CMIS (if CMIS will not define them in future). To overcome this we plan to add some nuxeo specific features over CMIS (in nuxeo CMIS impl.) to be able to address all our services. The problem is this can take at least some months of work.
If you plan in short term to have better control and to use specific nuxeo APIs that are not covered by CMIS you should envisage JAX-RS. Otherwise you can wait for all Nuxeo services to be exposed through an extension of CMIS. (or help us with this). If you want something that you can control better (in terms of functionality) and you don't want to be dependent on milestones in having a fully CMIS working with Nuxeo + all Nuxeo additional features , then you should take the JAX-RS approach. Now about JAX-RS. I think there is an misunderstanding about WebEngine. - The first goal of WebEngine is to provide JAX-RS abilities in Nuxeo. This inclues complete JAX-RS support (as it is provided by the JBoss reasteasy implementation used by webengine), Nuxeo Login and Session management on the JAX-RS objects, and also transaction management (using EJB annotations or default transaction mechanism - i.e. a transaction per request) - The second goal of webengine is to provide a suitable framework to build Web Sites using JAX-RS objcets. For this WebEngine extends the JAX-RS model by adding new concepts like WebObjects, WebAdapters etc. The second point is optional, you can always use WebEngine to build good REST interfaces to Nuxeo without having to deal with WebEngine support for web sites. You can create pure JAX-RS application if that is what you want. In that case WebEngine will do the integration of your JAX-RS objects in a running Nuxeo server. We already have examples in Nuxeo that are using WebEngine only to provide REST APis. More, even if you don't use WebObjects (the extended webengine model) you can still use some cool features like freemarker templates, groovy, path bindings in configuration files for your root JAX-RS objects etc. So I would not say Nuxeo JAX-RS support is not mature enough. It is as mature as JBoss Resteasy implementation is mature... You have nothing that is missing - you have only optional functionality (provided by webengine) that you can choose to use or not. I can provide you examples on how to build JAX-RS applications with Nuxeo if you need. Bogdan -- Posted by "bstefanescu" at Nuxeo Discussions <http://nuxeo.org/discussions> View the complete thread: <http://www.nuxeo.org/discussions/thread.jspa?threadID=2941#8623> _______________________________________________ ECM mailing list [email protected] http://lists.nuxeo.com/mailman/listinfo/ecm To unsubscribe, go to http://lists.nuxeo.com/mailman/options/ecm
