Message-ID: <1698646622.301595.1369144624906.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_301594_1762119.1369144624905" ------=_Part_301594_1762119.1369144624905 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
JAXB 2.0 looks quite good - it supports XML Schema, gen= erates nice POJOs, supports schema extension points and has StAX support. T= he only downside is its Java 5 specific - and the XJC tool tends to break w= hen you give it a collection of real world WSDLs (like WS-Notification for = example).
ActiveSOAP now fully supports JAXB 2.0 as a marshalling layer for REST a= nd SOAP web services; allowing you to use a nice and simple marshalling lay= er and keep your code based on simple POJOs. To get a feel for how this wor= ks see the examples
So now we've the best of both worlds.
You can happily mix and match both approaches, together with any other k= inds of XML binding tools you wish - all using a simple & lightweight R= EST/SOAP framework with pluggable transports for HTTP and JMS.
We have added a few examples of usi= ng ActiveSOAP and XMLBeans to invoke web services or REST services, which r= elies on auto-generating a service interface from the WSDL at the same time= you generate your XMLBeans interfaces.
If you want to be dynamic, there's also a Dynamic client which allows you to invoke services without co= de generation.
Its very popular to use a RESTful approach of sending blobs of XML over = HTTP or JMS. Using the full SOAP protocol and WS-* is often an unnecessary = overhead.
ActiveSOAP now supports both pure REST= and one or more SOAP protocols concurrently on the same service endpoint o= ver HTTP and/or JMS (or other transports).
This allows lightweight some clients to use pure REST and then when the = use of the SOAP protocol (and other optional WS-protocols) makes sense, to = support those too all in the same endpoint.
This is useful as you should only pay for what you need; for many use ca= ses pure REST is fine - its often up to the endpoint to decide whether or n= ot the SOAP protocol is worth the cost and if it is which version of SOAP i= t wishes to support along with what of the WS-protocols it requires too.
We've added an example to CVS whic= h demonstrates how to bind a POJO service written using XMLBeans generated = from a WSDL to both REST and SOAP.
Its easy to map multiple operations on different ports to the same servi= ce instance or to separate operations on the same port to different service= instances however you see fit.
Could not access the content at the URL because it is not fro= m an allowed source.
You may contact your site administrator and request that this URL b= e added to the list of allowed sources.