Package orc.orchard.soap

JAX-WS bindings for Orchard services.

See:
Description

Class Summary

CompilerService	HACK: We must explicitly declare every published web method in this class, we can't simply inherit them, for the following reasons: JAX-WS ignores (does not publish) inherited methods.
ExecutorService	HACK: We must explicitly declare every published web method in this class, we can't simply inherit them.

Package orc.orchard.soap Description

JAX-WS bindings for Orchard services.

In order to compile these, you will need to do a manual or clean build. I have added an Ant wsgen.xml file with the necessary tasks to build the webservice stuff.

There are two separate implementations of the services depending on how you intend to deploy them (unfortunately some duplication seems to be unavoidable):

standalone

Run without a separate servlet container. These are ideal for testing and development in Eclipse. Just run the Java class directly; the "main" method will start an embedded HTTP server.

servlet

Packaged in a WAR to be run in a servlet container. These are typically how you would deploy the services in production.

In theory it should be possible to integrate this stuff into Eclipse automatically via the JDT-APT plugin (which is included in 3.2+). Unfortunately there are problems with the JAX-WS annotation processor which make it impossible to use via JDT-APT:

• "The JAX-WS annotation processor stores and reads static data that prevents it from being used incrementally", according to JDT-APT bug 106541. Fortunately, the JDT-APT folks provide a work around which allows JAX-WS annotations to be processed in "Batch" mode (although this makes it no more automatic than the Ant solution we're currently using).
• More seriously, if JAX-WS RI is used to process annotations on multiple webservices at once with different endpointInterface annotations, it barfs. This is recorded as a "feature request" at JAX-WS RI bug 345, but in any case that makes the annotation processor unusable even with the "Batch mode" hack.

For testing purposes I would recommend installing the soapUI plugin. Instructions can be found at http://www.soapui.org/eclipse/index.html