Actually, C support is as complete as the C++ support. But only on client side, and only for doc/literal.
>From an old post when I asked the question long ago: ============ AxisC++ is a very good, solid, 2nd generation Web Services stack written in C++. It supports being a client to UDDI, and certainly it would be possible to support WS-Sec under it. However standards like RM and WS-Addressing are hard to support. If you look at the iterations of development, the first iteration (e.g. ApacheSOAP) was just about getting the job done simply. The next iteration added better parsing and more flexible handler models, which successfully supports WSSecurity and simple extensions to SOAP. However, the big change has been WS-Addressing, which has made WS much more asynchronous and message based. Unfortunately a lot of WS stacks including Axis/Java 1.x and Axis/C++ 1.x were built with a very RPC-like model. Axis2 C is the start of the move of Axis in C/C++ to the Axis2 model. When we wrote Axis2/Java we started again. In building Axis2/C we also started again. =========== So basically Axis2/C and Axis2/Java were created to support more of the standards and improve on what was learned in prior implementations. Nadir Amra Olivier Mengué <omen...@oxymel.com> wrote on 02/11/2010 03:57:55 AM: > [image removed] > > RE : Need suggestions on Axis/c client stub > > Olivier Mengué > > to: > > Apache AXIS C User List, Apache AXIS C User List > > 02/11/2010 04:02 AM > > Cc: > > "Apache AXIS C User List" > > Please respond to "Apache AXIS C User List" > > > > De: Nadir Amra > >Axis-C++ client-side is not broken or buggy. It is perfectly functional > >and in some cases much easier to use than axis2/C. > > So why Axis2/C was created? I'm insterested in the history of the project. > Is it because "C support is not complete." in Axis C++ ? > (according to http://ws.apache.org/axis/cpp/index.html#Known_issues ) > > Olivier.
