Download all versions of axis2-parent JAR files with all dependencies
axis2-parent from group org.apache.axis2 (version 1.5)
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.
Group: org.apache.axis2 Artifact: axis2-parent
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact axis2-parent
Group org.apache.axis2
Version 1.5
Last update 28. May 2009
Tags: 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
Organization Apache Software Foundation
URL http://ws.apache.org/axis2/
License not specified
Dependencies amount 9
Dependencies axiom-api, axiom-impl, axiom-dom, mail, xmlunit, xalan, ${stax.impl.artifact}, geronimo-stax-api_1.0_spec, commons-io,
There are maybe transitive dependencies!
Group org.apache.axis2
Version 1.5
Last update 28. May 2009
Tags: 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
Organization Apache Software Foundation
URL http://ws.apache.org/axis2/
License not specified
Dependencies amount 9
Dependencies axiom-api, axiom-impl, axiom-dom, mail, xmlunit, xalan, ${stax.impl.artifact}, geronimo-stax-api_1.0_spec, commons-io,
There are maybe transitive dependencies!
axis2-parent from group org.apache.axis2 (version 1.4.1)
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.
Group: org.apache.axis2 Artifact: axis2-parent
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact axis2-parent
Group org.apache.axis2
Version 1.4.1
Last update 25. August 2008
Tags: 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
Organization Apache Software Foundation
URL http://ws.apache.org/axis2/
License not specified
Dependencies amount 10
Dependencies axiom-api, axiom-impl, axiom-dom, mail, xmlunit, xalan, ${stax.impl.artifact}, geronimo-stax-api_1.0_spec, xercesImpl, commons-io,
There are maybe transitive dependencies!
Group org.apache.axis2
Version 1.4.1
Last update 25. August 2008
Tags: 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
Organization Apache Software Foundation
URL http://ws.apache.org/axis2/
License not specified
Dependencies amount 10
Dependencies axiom-api, axiom-impl, axiom-dom, mail, xmlunit, xalan, ${stax.impl.artifact}, geronimo-stax-api_1.0_spec, xercesImpl, commons-io,
There are maybe transitive dependencies!
axis2-parent from group org.apache.axis2 (version 1.4)
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.
Group: org.apache.axis2 Artifact: axis2-parent
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact axis2-parent
Group org.apache.axis2
Version 1.4
Last update 01. May 2008
Tags: 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
Organization Apache Software Foundation
URL http://ws.apache.org/axis2/
License not specified
Dependencies amount 10
Dependencies axiom-api, axiom-impl, axiom-dom, mail, xmlunit, xalan, ${stax.impl.artifact}, geronimo-stax-api_1.0_spec, xercesImpl, commons-io,
There are maybe transitive dependencies!
Group org.apache.axis2
Version 1.4
Last update 01. May 2008
Tags: 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
Organization Apache Software Foundation
URL http://ws.apache.org/axis2/
License not specified
Dependencies amount 10
Dependencies axiom-api, axiom-impl, axiom-dom, mail, xmlunit, xalan, ${stax.impl.artifact}, geronimo-stax-api_1.0_spec, xercesImpl, commons-io,
There are maybe transitive dependencies!
axis2-parent from group org.apache.axis2 (version 1.3)
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.
Group: org.apache.axis2 Artifact: axis2-parent
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact axis2-parent
Group org.apache.axis2
Version 1.3
Last update 10. August 2007
Tags: 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
Organization Apache Software Foundation
URL http://ws.apache.org/axis2/
License not specified
Dependencies amount 9
Dependencies axiom-api, axiom-impl, axiom-dom, mail, xmlunit, xalan, ${stax.impl.artifactid}, xercesImpl, commons-io,
There are maybe transitive dependencies!
Group org.apache.axis2
Version 1.3
Last update 10. August 2007
Tags: 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
Organization Apache Software Foundation
URL http://ws.apache.org/axis2/
License not specified
Dependencies amount 9
Dependencies axiom-api, axiom-impl, axiom-dom, mail, xmlunit, xalan, ${stax.impl.artifactid}, xercesImpl, commons-io,
There are maybe transitive dependencies!
axis2-parent from group org.apache.axis2 (version 1.2)
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.
Group: org.apache.axis2 Artifact: axis2-parent
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact axis2-parent
Group org.apache.axis2
Version 1.2
Last update 27. April 2007
Tags: 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
Organization Apache Software Foundation
URL http://ws.apache.org/axis2/
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.apache.axis2
Version 1.2
Last update 27. April 2007
Tags: 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
Organization Apache Software Foundation
URL http://ws.apache.org/axis2/
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
axis2-parent from group org.apache.axis2 (version 1.1)
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.
Group: org.apache.axis2 Artifact: axis2-parent
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact axis2-parent
Group org.apache.axis2
Version 1.1
Last update 14. November 2006
Tags: 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
Organization Apache Software Foundation
URL http://ws.apache.org/axis2/
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.apache.axis2
Version 1.1
Last update 14. November 2006
Tags: 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
Organization Apache Software Foundation
URL http://ws.apache.org/axis2/
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Page 2 from 2 (items total 16)