Skip to end of metadata
Go to start of metadata

We have support for the processing of XML headers or body elements through the use of the XStream library. XStream is idea when you have a bunch of POJOs and you want to stream them over XML.

If you are given a WSDL and want to create beans for it, we recommend a tool like XMLBeans, Castor or JAXB. However if you're starting with POJOs then XStream is nice & simple & fast.

The client API is pretty much the same as for the other marshalling tools. First off we have a regular interface that represents some service...

An error occurred: cvs.activesoap.codehaus.org. The system administrator has been notified.

Now here's a REST client invoking a remote service..

An error occurred: cvs.activesoap.codehaus.org. The system administrator has been notified.

Or the SOAP client looks like this

An error occurred: cvs.activesoap.codehaus.org. The system administrator has been notified.

The server side

The following example demonstrates how to bind the server side implementation of a service to the some transport ready for being dispatched.

Here's a REST service example

An error occurred: cvs.activesoap.codehaus.org. The system administrator has been notified.

Here's a SOAP service example

An error occurred: cvs.activesoap.codehaus.org. The system administrator has been notified.

Dynamic client interface

You can avoid using service interfaces and dynamic proxies and just pass typed document POJOs around using the dynamic interface.

Here's a REST client example

An error occurred: cvs.activesoap.codehaus.org. The system administrator has been notified.

Here's a SOAP client example

An error occurred: cvs.activesoap.codehaus.org. The system administrator has been notified.
  • No labels

1 Comment

  1. Does this already work?