a

axis2-parent

Axis2 is an effort to re-design and totally re-implement both Axis/Java and (eventually) Axis/C++ on a new architecture. Evolving from the now standard "handler chain" model which Axis1 pioneered, Axis2 is developing a more flexible pipeline architecture which can yet be managed and packaged in a more organized manner. This new design acknowledges the maturing of the Web services space in terms of new protocols such as WS-ReliableMessaging, WS-Security and WS-Addressing that are built on top of the base SOAP system. At the time Axis1 was designed, while it was fully expected that other protocols such as WS-ReliableMessaging would be built on top of it, there was not a proper extension architecture defined to enable clean composition of such layers. Thus, one of the key motivations for Axis2 is to provide a clean and simple environment for like Apache Sandesha and Apache WSS4J to layer on top of the base SOAP system. Another driving force for Axis2 as well as the move away from RPC oriented Web services towards more document-oriented, message style asynchronous service interactions. The Axis2 project is centered on a new representation for SOAP messages called AXIOM (AXIs Object Model). AXIOM consists of two parts: a complete XML Infoset representation and a SOAP Infoset representation on top of that. The XML Infoset representation provides a JDOM-like simple API but is built on a deferred model via a StAX-based (Streaming API for XML) pull parsing API. A key feature of AXIOM is that it allows one to stop building the XML tree and just access the pull stream directly; thus enabling both maximum flexibility and maximum performance. This approach allows us to support multiple levels of abstraction for consuming and offering Web services: using plain AXIOM, using generated code and statically data-bound data types and so on. At the time of Axis1's design, RPC-style, synchronous, request-response interactions were the order of the day for Web services. Today service interactions are much more message -oriented and exploit many different message exchange patterns. The Axis2 engine architecture is careful to not build in any assumptions of request-response patterns to ensure that it can be used easily to support arbitrary message exchange patterns.
http://axis.apache.org/axis2/java/core/
Saminda Abeyruwan Afkham Azeez Jeff Barrett Eran Chinthaka Glen Daniels Brian DePradine Jaliya Ekanayake Ruchith Fernando Nicholas Gallardo Thilina Gunarathne Chathura Herath David Illsley Deepal Jayasinghe Robert Lazarski Senaka Fernando Steve Loughran Bill Nagy Chatra Nakkawita Sumedha Rubasinghe Charitha Kamkanamge Srinath Perera Ajith Ranabahu Venkat Reddy Michael Rheinheimer Ann Robinson Sanka Samaranayake Rich Scheuerle Ashutosh Shahi Aleksander Slominski Dennis Sosnoski Davanum Srinivas Jayachandra Sekhara Rao Sunkara Nandana Mihindukulasooriya Nikhil Thaker Chamil Thanthrimudalige Dasarath Weerathunga Eranga Jayasundera Sanjiva Weerawarana Keith Chapman Andreas Veithen Ruwan Linton
maturing using statically layers parts towards consuming time tree levels asynchronous oriented feature consists fully exchange move services patterns support defined engine wss4j organized like flexible many project managed system enabling abstraction pioneered soap axiom different stream simple data easily deferred space addressing build messages document designed clean built ensure just streaming centered stax acknowledges access eventually extension sandesha chain base reliablemessaging force bound based design arbitrary both provide careful pull motivations terms enable driving apache architecture used were packaged more would request jdom composition developing totally synchronous proper directly flexibility infoset such protocols effort offering code evolving much that environment representation maximum generated assumptions called this stop model other today object well from security while response another style order complete allows performance parsing implement plain types multiple interactions axis building standard thus layer provides exploit message axis2 away axis1 expected which pipeline there service approach java manner handler
Files download
File Operation
axis2-parent-1.6.2.pom download
Apache Maven 
<dependency>
  <groupId>org.apache.axis2</groupId>
  <artifactId>axis2-parent</artifactId>
  <version>1.6.2</version>
  <type>pom</type>
</dependency>
Gradle Groovy 
implementation 'org.apache.axis2:axis2-parent:1.6.2'
Gradle Kotlin 
implementation("org.apache.axis2:axis2-parent:1.6.2")
Scala SBT 
libraryDependencies += "org.apache.axis2" % "axis2-parent" % "1.6.2"
Groovy Grape 
@Grapes(
  @Grab(group='org.apache.axis2', module='axis2-parent', version='1.6.2')
)
Apache Ivy 
<dependency org="org.apache.axis2" name="axis2-parent" rev="1.6.2" />
Leiningen 
[org.apache.axis2/axis2-parent "1.6.2"]
Apache Buildr 
'org.apache.axis2:axis2-parent:jar:1.6.2'
Dependencies 
<parent>
  <groupId>org.apache</groupId>
  <artifactId>apache</artifactId>
  <version>8</version>
</parent>
The project has no third-party dependencies