Copy Page

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account. You can also Sign Up for a new account.

<a href="http://xmlbeans.apache.org/">XMLBeans</a> is a tool for handling typically XSD typed XML with support for the autogenerating of beans to map to a WSDL or XSD file.

We have an <a href="http://activesoap.codehaus.org/maven/apidocs/org/codehaus/activesoap/handler/xmlbeans/XMLBeansHandler.html">XMLBeanHandler</a> in the <a href="http://activesoap.codehaus.org/maven/apidocs/org/codehaus/activesoap/handler/xmlbeans/package-summary.html">XMLBeans package</a>you can derive from if you wish to stay close to the metal.

Alternatively we've an <a href="http://activesoap.codehaus.org/maven/apidocs/org/codehaus/activesoap/handler/xmlbeans/XMLBeansRegistry.html">XMLBeansRegistry</a> which you can use with a RestService or SoapService to bind any service instances which can process incoming XMLBeans document types and possibly process some output.

Here is an <a href="http://cvs.activesoap.codehaus.org/viewrep/activesoap/activesoap/src/test/org/codehaus/activesoap/examples/snowboard/">example application</a> which demonstrates writing a simple POJO based services using purely XMLBeans and letting ActiveSOAP be the REST or SOAP stack and handling the HTTP or JMS transports for you.

First you need some kinda service to expose. So we wrote a little interface.

<table class="wysiwyg-macro" data-macro-name="unmigrated-inline-wiki-markup" data-macro-parameters="atlassian-macro-output-type=BLOCK" style="background-image: url(/plugins/servlet/confluence/placeholder/macro-heading?definition=e3VubWlncmF0ZWQtaW5saW5lLXdpa2ktbWFya3VwOmF0bGFzc2lhbi1tYWNyby1vdXRwdXQtdHlwZT1CTE9DS30&amp;locale=en_GB&amp;version=2); background-repeat: no-repeat;" data-macro-body-type="PLAIN_TEXT"><tr><td class="wysiwyg-macro-body"><pre>{snippet:id=example|lang=java|url=http://cvs.activesoap.codehaus.org/viewrep/~raw,r=HEAD/activesoap/activesoap/src/test/org/codehaus/activesoap/examples/snowboard/SnowboardService.java}</pre></td></tr></table>

There's a method on this interface which accepts an XMLBeans type. We can have as many methods as we like all auto-published, the only requirement is that the parameter must be an XMLBeans type, so that when we register it with XMLBeansRegistry it can auto-deduce the QName which matches the XMLBean type.

Then if we register an implementation of this interface with the XMLBeansRegistry we can automatically publish the service as both REST and SOAP endpoints...