ActiveSOAP uses StAX (the Standard API for pull parsing) to implement the 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 what you need; use fast pull based event parsing or full data binding or DOMish APIs when they make sense.
You to use whatever XML marshalling and/or parsing tool you like to process different messages or headers. The following APIs are currently supported
ActiveSOAP is currently used to provide WS-Notification support in ActiveMQ.
In addition to the core StAX processing of SOAP requests (client and server side) ActiveSOAP provides support for WS-Addressing.
To get a feel for how you can work with document centric web services using ActiveSOAP and XMLBeans, take a look at an Example.
There is also a dynamic client invocation API which you can use if you don'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
Confluence RSS Feed
Confluence Syndication Feed