That is good news, but I wonder why SOAP 1.1 and SOAP 1.2 are not fully supported? Also you don't mention MEPs such as one-way and async. Do you plan to support polymorphism (e.g. Apache Axis map)? Attachments?
Note that gSOAP (SourceForge and soon: Debian) is already stable and provides more features. It supports both SOAP 1.1 and SOAP 1.2. It serializes native C and C++ data types as well (including STL and polymorphism), so no hassle with conversion and/or mappings. Actually, gSOAP is more XML-centric than SOAP-centric as it provides more generic compiler-based XML encoding. No offense, but I am just wondering if this release announcement is not taking us a step back.
- Prof. Robert van Engelen, Florida State University
On Wednesday, October 15, 2003, at 05:35 AM, Susantha Kumara wrote:
Hi all,
We are happy to announce our plan to release Apache Axis C++ implementation.
I have volunteered to be the release manager for Apache Axis C++ initial release.
Following is the release plan.
Introduction: ------------ This is the release plan for Axis/C++ version 1.0. The goal of Axis/C++ version 1.0 is to provide a stable platform for developing Web services using C++ as well as to use Web services in C++ client applications. Major features of Axis/C++ include: - SOAP engine with both client and server support - Partial support for both SOAP 1.1 and SOAP 1.2 - WSDD based deployment with dynamic deployment tools. - Support for all basic types, Complex types and Arrays - WSDL2WS tool for building following C/C++ components Server side - Skeletons and Wrappers Client side - Stubs - WSDL2WS tool that generates wrappers, which perform the following functions. These wrappers act as RPC Providers. Serialization Deserialization Method invocation - WSDLs hosted statistically in the server. - Standalone server (with HTTP support) - Web server modules for Apache HTTPD 1.3 (Linux/Windows) - Web interface to the deployed services and their WSDLs. - Sample web services and client applications. - Supportive documentation for developers and users.
Dates: ----- The following dates are proposed: Code freeze October 21, 2003 Release alpha version October 23, 2003 Release beta version October 30, 2003 Release 1.0 November 6, 2003
Once release freeze is achieved, inclusion of fixes into the release requires consensus of active Axis committers. Deferring of a fix requires simple majority.
Fixes are to continue to be made on the "HEAD" of the release. Once
there is consensus that a particular fix is to be included in the
release, I'll merge it into the branch. In order to make this as smooth
and as painless a process as possible for the release manager, I'll ask
that committers show restraint in committing unrelated fixes to the HEAD
during this time in areas of the code that might interfere with the
merge process.
Release Criteria: ---------------- - All Axis/C++ functional tests pass. - All critical bugs are fixed - Basic interop tests pass - Confirmation that the released version works on Apache HTTP 1.3* on Win32 and Linux
Release Manager: --------------- Susantha Kumara, [EMAIL PROTECTED]
Release Announcements: --------------------- [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Thanks, Susantha (on behalf of Axis C++ team)
