1 / 25

Axis2 - Overview

Axis2 - Overview. Agenda. What is already there Overall Architecture Core AXIOM WSDL Deployment Client API What is yet to come Encoding – Pluggable data binding Other transports. Overall Architecture of Axis2. Introduction to the terminology.

beryl
Download Presentation

Axis2 - Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Axis2 - Overview

  2. Agenda • What is already there • Overall Architecture • Core • AXIOM • WSDL • Deployment • Client API • What is yet to come • Encoding – Pluggable data binding • Other transports

  3. Overall Architecture of Axis2

  4. Introduction to the terminology • Inflow – The sequence of event that happens when a message is received • Outflow - The sequence of event that happens when a message is sent out

  5. Core • Core consist of the following • Handler Framework • Message Context • Registry • Engine

  6. Core (cont…) • The relationship of the Core components is as follows

  7. Core :: Message Context • Container for the SOAP message and related information. • Other components such as engine and handlers are stateless

  8. Core:: Handler Framework • Handlers are the “execution units” • Always works with a message context • Handlers can be executed in the inflow and the outflow • 3 basic categories – Transport, Global and Service • Phases are logical handler collections • Ordered at the server startup • Handlers are ordered in Phases • Depending on the phase rules defined in the service descriptor

  9. Core:: Handler Framework (cont..) • Special handlers • Receiver • Receives messages • Is used to call the provider component • Sender • Sends message • Invokes the outflow handler chain • Dispatcher • Finds the service

  10. Core :: Registry • Keeper for the Services • Dispatcher works on the Registry • Is filled by the deployment mechanism.

  11. Core :: Engine • The “Controller” • Stateless! • State is kept in the Message Context

  12. How the Axis2 core works • Example Axis2 animation on the server side in-out message flow

  13. AXIOM • The SOAP info set representation • Tightly bound to StAX • Features differed building

  14. AXIOM :: SOAP Implementation • Layered on AXIOM base classes • Tight coupling • Version support on 1.1 • SOAP based builders based on StAX

  15. WSDL • The WSDL handling mechanism • New Object model • WOM(WSDL Object Model)

  16. Deployment • The new Archive format • Hot deployment

  17. Deployment :: Service Archive • Axis archive – .aar file. • A jar file with all the service classes and the service description • Can be uploaded through the web or directly through the file system. • Service description included in the service.xml

  18. Client API • Facility for Synchronous / Asynchronous invocations • Supported styles • In-out sync • In-out async (response on the same channel) • In-Only

  19. What is yet to come? • Messaging based core • MTOM support for AXIOM • Pluggable data binding • Multiple transports

  20. MTOM Support • MTOM support for AXIOM • Introduction of New Object - OMBlob • MIME / XOP aware builder

  21. Message based core • The current core is visibly not message centric • Add a messageSender and a messageReceiver ?

  22. Transport • SMTP/POP support

  23. Data binding • Pluggable Encoding / Data binding support • XMLBeans • JAXB • Castor

  24. Questions ?

  25. Thank you

More Related