Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C User List" <axis-c-user@ws.apache.org>
Received-SPF: pass (hermes.apache.org: domain of andras.horti@joanneum.at
 designates 143.224.185.3 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: AW: Is Axis(C++) stable and mature
Date: Mon, 4 Oct 2004 08:05:58 +0200
Message-ID: <768DACDC356ED04EA1F1130F97D298521C0CB3@RZJC2EX.jr1.local>
Thread-Topic: Is Axis(C++) stable and mature
Thread-Index: AcSn0ZDZu4UTDdUKQ7KW83pChLVrPwCBk3Lw
From: "Horti, Andras" <andras.horti@joanneum.at>
To: "Apache AXIS C User List" <axis-c-user@ws.apache.org>

8.) Internally all strings must be handled as Unicode (otherwise you can =
forget projects using different character sets).

-----Urspr=FCngliche Nachricht-----
Von: Alexei Dets [mailto:adets@idsk.com]=20
Gesendet: Freitag, 01. Oktober 2004 18:03
An: Apache AXIS C User List
Betreff: Re: Is Axis(C++) stable and mature

Hi!
On Friday 01 October 2004 05:56, John Hawkins wrote:
> I would like to disagree with that....
>
> We have four major projects that are using the code as is - we still=20
> need to make a few additions  - however, they are happy with the =
results so far.
>
> Yes, the project needs to include more function - but this will=20
> happen. If you have specific requirements then please shout and we=20
> will do our best to accomodate.

Axis C++ is not even nearly of production quality at least because of:
1) Very active development that causes nearly everyday API and behaviour =
changes, new bugs and bugfixes etc. - unfortunately Axis C++ has no =
stable version at all (see below).
2) Latest "stable" 1.2 is UNUSABLE for everything except simple demos:=20
transport layer is _completely_ broken and is usually unable to exchange =
SOAP messages bigger than ~2K.=20
3) Axis C++ currently is a mess of C & C++ code. In particular this =
leads to memory allocation/deallocation problems (AFAIK Axis C++ has =
tons of memory leaks). Also this complicates C++ coding a lot because =
instead of strings and vectors users are forced to deal with plain C =
data types.
4) Axis C++ doesn't support ref/href/multiRef that are recommended  for =
SOAP messages and are _default_ at least in Axis Java (that seems to be =
one of the most popular SOAP implementations). This means that =
interoperability sucks, there is a very good chance that you'll not be =
able to communicate with another side.
5) Axis C++ has problems in the SOAP faults processing.
6) Axis C++ has nearly NO documentation. And what it has is partially =
incorrect.
7) Fortunately, Axis C++ developers perfectly understand the main =
problems of the current Axis C++ API & design. Unfortunately, to solve =
them major rewrite is planned that will in turn require user application =
changes. Probably major changes.

In the other words - if you are ready to actively _develop_ Axis C++ =
then may be you can use it for some projects. But prepare that this =
means that your project will not become stable until Axis C++ become =
stable. So, if you project release date is somewhere around 2006 (or =
later) you can probably start with Axis C++ now but not otherwise. Axis =
C++ is very promising but it is not mature yet, it is growing and =
changing.

As for me, what I want to see in Axis C++:
1) Redesign Axis, implement native C++ API in the whole project. This =
means ONLY new/delete for memory allocations, NO char* etc. C++ (STL) =
data types instead - string, vector etc.
2) Get rid of memory leaks. Probably switching to C++ will help a lot in =
this.=20
Document memory management model in Axis - who, when & how should =
allocate and deallocate memory.
3) Interoperability, more functions, better standards compatibility.=20
ref/href/multiRef as the first priority. Also there are some other =
interoperability issues.
4) _Stable_ release with 1,2 & 3.

:-)

	Alexei