Skip to end of metadata
Go to start of metadata

Space Index

0-9 ... 0 A ... 0 B ... 1 C ... 1 D ... 2 E ... 1
F ... 1 G ... 1 H ... 4 I ... 1 J ... 1 K ... 0
L ... 0 M ... 0 N ... 2 O ... 0 P ... 0 Q ... 1
R ... 2 S ... 1 T ... 1 U ... 1 V ... 0 W ... 4
X ... 2 Y ... 0 Z ... 0 !@#$ ... 0    




Page: Building
AcitveSOAP uses Maven as its build tool. If you don't fancy using Maven you can use your IDE directly or Download a distribution or JAR. We have tested the build with Maven 1.0 and it works fine. Later versions of Maven may vary -


Page: Contributing
There are many ways you can help make ActiveSOAP a better piece of software - please dive in and help! Try surf the documentation - if somethings confusing or not clear, let us know. Download the code & try it out and see what you think. Browse the source


Page: Download
You can download a jar of ActiveSOAP here Or the full binary and source distributions are here
Page: Dynamic Client
Instead of generating an interface for a WSDL endpoint as shown in the introductory examples, we can use the dynamic interface to pass in/out any arbitrary XML blob over REST or SOAP. So here is a dynamic web service invocation using XMLBeans as the body


Page: Example
Here is an example of an interface to a service. Note that the interface is optional, you can expose a class as a service - we've just used an interface in this example as its good practice and makes the example easier to follow. {snippet:id=example|lang=


Page: FAQ


Page: General
General questions about ActiveSOAP


Home page: Home
ActiveSOAP is a lightweight & easily embeddable REST and SOAP stack based on StAX with support for WS-Addressing and WSIF. ActiveSOAP uses StAX (the Standard API for pull parsing) to implement the SOAP protocols and then it delegates to plugin Handler htt
Page: How do I add SOAP headers on a client invocation
You can register a Handler with the SoapClient to perform some processing and output any custom headers as part of a SOAP client invocation. e.g. SoapClient client = ...; Ha
Page: How do I compile from the source
See the Building page
Page: How it works
ActiveSOAP is essentially a small, lightweight XML router using the StAX pull parser API. When an XML request is processed, the QName of the root element is extracted and then passed on to some Handler


Page: Index


Page: JAXB
JAXB 2.0 now supports StAX natively and integrates easily into ActiveSOAP. Here is an example application





Page: Navigation
Overview Home News FAQ JavaDocs Download Using ActiveSOAP Building Example Dynamic Client WS-Addressing How it works Supported Tools JAXB XMLBeans XStream Related Projects ServiceMix Act
Page: News




Page: QuickLinks
Download | JavaDocs | CVS | Wiki | Mailing Lists


Page: REST
REST stands for REpresentational State Transfer, and is an architectural style for large-scale software design. Within the scope of the ActiveSOAP project we tend to refer to REST services as being services which c
Page: RightHeader


Page: StAX
Streaming API for XML is an event based pull parser API for Java. See JSR 173


Page: Terminology
Questions on acronyms and terminology used


Page: Using ActiveSOAP
Questions on using ActiveSOAP



Page: What is ActiveSOAP
ActiveSOAP is a high performance, lightweight, StAX based SOAP framework for document centric Web Services and SOAP intermediaries. It allows a variety of XML marshalling and data binding tools to be dropped in to provide a flexible framework for document
Page: What is the licence
This software is open source using the Apache 2.0 licence (a liberal BSD style licence which is very commercial friendly)
Page: WS-Addressing
You can see the WS-Addressing support in the javadoc The most common use case is when implementing a server side handler wishing to process the cu
Page: WSIF
The Web Services Invocation Framework provides a generic way to invoke web services along with a way of adorning a WSDL with extra metadata to describe the WSIF binding in more detail. We currently have experimental WSIF provide


Page: XMLBeans
XMLBeans 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 XMLBeanHandler
Page: XStream
We have support for the processing of XML headers or body elements through the use of the XStream library. XStream is idea when you have a bunch of POJOs and you want to stream them over XML. If you are given a WSDL and want t




  • No labels