Message-ID: <997389872.6173.1369552220671.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_6172_1178511279.1369552220670" ------=_Part_6172_1178511279.1369552220670 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
XMLBeans is a tool for handling typically XSD typed XM= L with support for the autogenerating of beans to map to a WSDL or XSD file= .
We have an XMLBeanHandler in the XMLBeans packag= eyou can derive from if you wish to stay close to the metal.
Alternatively we've an XMLBeansRegistry 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.<= /p>
Here is an example application which demonstra= tes writing a simple POJO based services using purely XMLBeans and letting = ActiveSOAP be the REST or SOAP stack and handling the HTTP or JMS transport= s for you.
First you need some kinda service to expose. So we wrote a little interf= ace.An error occurred: cvs.activesoap.codehaus.org. The system administrator ha= s been notified.
There's a method on this interface which accepts an XMLBeans type. We ca= n 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 XMLBe= an type.
Then if we register an implementation of this interface with the XMLBean= sRegistry we can automatically publish the service as both REST and SOAP en= dpoints...An error occurred: cvs.activesoap.codehaus.org. The system administrator ha= s been notified. ------=_Part_6172_1178511279.1369552220670--