Message-ID: <186518617.2835.1369323876695.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2834_143372593.1369323876694" ------=_Part_2834_143372593.1369323876694 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
ActiveSOAP is a lightweight & easily embeddable REST and SOAP stack based on StAX with support for WS-A= ddressing and WSIF.
ActiveSOAP uses StAX (the Standard API for pull parsing) to implement th= e SOAP protocols and then it delegates to plugin Handler objects for the heavy duty = processing of the XML payloads. This means that you only need to pay for wh= at you need; use fast pull based event parsing or full data binding mechani= sms like JAXB or XStream or DOMish APIs like XMLBeans when they make sense.=
You can use whatever XML marshalling and/or parsing tool you like to pro= cess different messages or headers. The following APIs are currently suppor= ted
ActiveSOAP is currently used to provide WS-Notifi= cation support in ServiceMix.
In addition to the core StAX processing of SOAP requests (client and ser= ver side) ActiveSOAP provides support for WS-Addressing and provides multiple WSIF providers.
To get a feel for how you can work with document centric web services us= ing ActiveSOAP and XMLBeans, take a look at an Example.
There is also a dynamic client invocation API which you can use if you d= on't want to generate interfaces from your WSDLs such as in this example
To get a feel for the architecture, try reading How it works
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.