Differences between revisions 23 and 24
Revision 23 as of 2004-12-06 04:40:33
Size: 3288
Comment:
Revision 24 as of 2009-09-20 22:48:58
Size: 3292
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 22: Line 22:
 * Release Plan [http://wiki.apache.org/ws/FrontPage/Axis2/Release01M1]
 * TO DO's [http://wiki.apache.org/ws/FrontPage/Axis2/ToDo01M1]
 * Release Plan [[http://wiki.apache.org/ws/FrontPage/Axis2/Release01M1]]
 * TO DO's [[http://wiki.apache.org/ws/FrontPage/Axis2/ToDo01M1]]

Apache Axis 2 Project Plan

Requirements and initial architecture was discussed between the 21st-24th of August 2004 in Colombo. It was decided that we prototype some of the identified components for a period of three months before a final plan for Axis 2.0 is prepared.

Prototyping

The following components are being prototyped:

  • OM
  • Engine
  • Deployment
  • Data Binding
  • WSDL
  • Client API

High Level Plan

  1. Start Date: 25th August 2004
  2. Tentative End Date : 10th December 2004
  3. Integration and working prototype to be available on or before the 31st of December 2004

Milestone Release Plan for Axis2 01/M1

Sanjiva

  • (1) OM interfaces supporting the base SOAP Infoset (i.e., without MTOM) (2) OM implementation (3) Engine supporting
    • - "phased handlers" architecture complete - burnt-in concepts of WS-Addressing, suitably abstracted to make sure system can run with or without WS-Addressing headers - ability to deploy modules consisting of one or more handlers slotting into various phases - servlet HTTP transport

      - native HTTP transport (use code from SimpleAxisServer?) - support for ReplyTo style redirection even for HTTP cases - hot deployment of services - no service isolation - no data binding

    (4) Programming model for service implementors
    • - Only Java code supported - For WSDL 1.1 request-response style operations:
      • - Blocking:
        • Option 1: OM doFoo (OM)
          • (Basically take in an OM and produce an OM. This is good
            • for anyone who just wants the payload to play with and wishes to produce a payload to ship out.)
          Option 2: MC doFoo (MC)
          • (Basically take in the whole message context and produce
            • an MC .. which is the programming model for a handler too I guess!)
        - Non-blocking:
        • void startDoFoo (MC)
          • (App gets the message and when its ready to send the response (using the same thread or another thread or whatever), uses the client API to send it. Note: Method may return without having completed the response writing.
      - For WSDL 1.1 input-only style operations:
      • - void doFoo (OM) - void doFoo (MC) (App can consume just the payload or the full MC.)
    (5) Programming model for clients
    • - Blocking and non-blocking programming models (sync/async) - Details TBD
    (6) Deployment descriptor for services: service.xml (as discussed in Wiki) (7) Deployment descriptor for engine: engine.xml (as discussed in Wiki (?)) (8) Deployment descriptor for modules: module.xml (as discussed in Wiki) (9) Packaging/directory hierarchy for engine: as discussed in Wiki (10) Design docs, architecture docs, user guide update sufficiently to allow people to play with the M1 release.

Axis 2.0

Axis 2.0 Alpha

Axis 2.0 Beta

Axis 2.0 Final

Axis 2.1

FrontPage/Axis2/ProjectPlan (last edited 2009-09-20 22:48:58 by localhost)