Skip to content

Developing on the service registry

mkalam-alami edited this page Jul 5, 2011 · 29 revisions

Development environment

Check out the easysoa-model-demo project, do a mvn eclipse:eclipse at the root of the maven projects (in plugins/), import them in Eclipse and you're ready to go !

In order to build and deploy the plugins, you can either:

  • Use [Buildr](Development Environment) (recommended). Check out the easysoa-demo-dist to the same folder as the other repository, configure your Nuxeo location in build.yaml, then build and deploy by typing buildr nx_mvn nx_dist from the easysoa-demo-dist folder.
  • Build them using the buildPlugins.sh (or .bat) script, them move the target/plugins contents to your Nuxeo plugins folder (./nxserver/plugins).

Testing

To test (with JUnit) Nuxeo developments, there must be a runnning Nuxeo server, or at least part of it. There are several ways :

Embedded Nuxeo using custom Feature annotations

Use a custom JUnit Feature, and annotations to configure an embedded Nuxeo deployment. Available features :

(older, obsolete) Embedded Nuxeo using Nuxeo helpers

Extend org.nuxeo.runtime.test.NXRuntimeTestCase, and use the deployBundle, deployContrib methods & others to configure an embedded Nuxeo deployment. Example : see org.nuxeo.ecm.core.storage.sql.SQLRepositoryTestCase

Full Nuxeo deployment

Write tests that interact remotely with a manually deployed Nuxeo by extending [NotificationTestCase] (https://github.com/easysoa/easysoa-model-demo/blob/master/plugins/easysoa-model-demo-rest/src/test/java/org/easysoa/test/rest/tools/NotificationTestCase.java), or using other remote interaction alternatives as described above.

Clone this wiki locally