The presentation I did in Apachecon 2009 on Axis2 Landscape.

1. Axis2 Landscape EranChinthaka School of Informatics and Computing Indiana University

3. Axis2 – Diving in to Architecture

4. How all projects fit together

6. PhD student in Indiana University, Bloomington, Indiana

8. Developed by IBM research team

9. Donated by IBM shortly after IBM joined the SOAP/WS initiative

10. Proof of concept

11. Apache Axis1

12. SAX based

13. Handler architecture

14. Widely used in many products

16. WS-Addressing , Reliable Messaging, WS-MEX

17. Performance

18. Parsers, message processing

19. Programming Abstractions

20. Asynchronous invocations, Message Exchange Patterns

21. Ease of use

23. Extensible Messaging Engine

24. Rich Information Model

25. Pluggable module, data binding, transports architecture

26. Can support XMLBeans, ADB, JAXB, JiBX, etc.,

27. Ability to plug-in any WS-* implementation

28. Easy to use deployment model

29. Convenient programming abstractions

30. WSDL 1.1, 2.0 and SOAP 1.1, 1.2 support

31. WSDL 2.0 HTTP binding, mimicing REST style invocations

32. Cloud computing support

33. Auto-scaling on Amazon

35. Academic Usage

36. De-facto web services engine in research projects

37. Eucalyptus[1]

38. Industry UsageCompanies started consulting on Axis2 and/or building products on Axis2 De-facto Web service engine for all the interoperability efforts [1]The Eucalyptus Open-source Cloud-computing System, Daniel Nurmi, Rich Wolski, Chris Grzegorczyk, GrazianoObertelli, Sunil Soman, Lamia Youseff, DmitriiZagorodnov, in Proceedings of 9th IEEE International Symposium on Cluster Computing and the Grid, Shanghai, China

39. Web services – Big Picture

40. Axis2 – SOAP Processing Model

41. Axis2 Engine Axis2 - Components Tools WSDL CodeGeneration Handlers Transports Information Model Deployment Model XML Model

43. API is more like simplified DOM

44. Fundamental Difference

45. Data read and objects created on-demand using pull parsers

46. Allows direct access to the underlying pull stream with or without building the tree

47. Support for storing binary data

48. API also provides a StAX parser interface at any element

50. Phases, Modules, Handlers

51. Extensible Messaging Engine

53. Dispatching

54. AddressingBasedDispatcher

55. RequestURIBasedDispatcher

56. SOAPActionBasedDispatcher

57. SOAPMessageBodyBasedDispatcher

58. User Handlers

61. MEP dependent (MEP ?? )

62. Does the actual business logic invocation

63. Ability to write custom Message Receivers

64. Injects dependencies to services

65. Default Message Receivers

66. RawXMLINOnlyMessageReceiver

67. RawXMLINOutMessageReceiver

69. In-Out

70. In only

73. modify the XML files or

74. Call the admin client, add to the classpath, restart the server

75. Archive based deployment

76. Bundle all together and drop in

77. Directory based deployment (similar structure as archive )

78. Hot Deployment

79. Archive file can contain

82. No need to have a WSDL around to be a valid service !!!

83. Contains

84. Exposed transports

85. Service scopes

86. Action mappings and message receivers

89. Concept of callbacks for the client for non- blocking case

90. handle both transport dependent and transport independent asynchrony

91. sendRobust

92. fireAndForget

93. sendReceive

95. for invoking a Web service

96. Stub, callback handler, data bound classes, build file

97. For authoring a Web service

99. WS-Commons

100. Axiom – the XML object model

101. XmlSchema – Xml schema model used within code generation, WSDL models

102. Transports

103. Neethi – WS-Policy implementation

104. Modules

105. Sandesha – WS-Reliable Messaging implementation

106. Rampart, Rahas – WS-Security, WS-Secureconversation, WS-Security Policy, WS-Trust implementations

107. Savan– WS-Eventing implementation

108. WS-Addressing

109. WSS4j – Web services security implementation including XML security

111. http://ws.apache.org/axis2

112. Feedback, bugs, questions

114. Axis2 hands on

116. Special thanks to DeepalJayasinghe for sharing his slides