Hi Pete, My first quick answer is to wait sometime (may be 1 week). We are in the process of improving the client api. This would not take much time. Once we are done we will come up with a somewhat comprehensive documentation on how to write clients. The decision we took to change the API right now is to limit the number of ppl who need to change their client code. If we have gone 1.0 with the current API and go on changing it, it would be a very difficult task. In my personal sense I like to do the changes right now rather than waiting for some time. But the bad side is we are gonna scrap out the older api - which implies that the current sample base will be invalid (if you also have some client code those will not work once the change happens). But I am quite sure once the new API is in place (which goes aligned with current Axis2 java code) you would be much comfortable with it.
Thanks - Sahan Pete Robbins wrote: > Hi, I'm currently working on the Tuscany project using Axis2C for > webservice support. I'm sure this change will affect me ;-) > > I've been coding an Axis2C client in Tuscany and did struggle a bit > trying to guess what the "official" client interface is supposed to > be. Is there any documentation on what the client side api is? The > samples are a starting point but there is a fair bit of assumed > knowledge required to follow them. > > Cheers, > > > On 25/04/06, *Nabeel* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: > > Keeping inline with the Axis2 Java Service Client API, I am > implementing > a similar client API for Axis2 C. > It has the following interfaces: > axis2_svc_client.h > axis2_op_client.h > axis2_options.h > > Once this is implemented, axis2_call.h interface can be removed. (This > will affect all the existing samples, documentations, PHP & Firefox > extensions written on top of Axis2 C) > > thanks > -Nabeel > > > > > -- > Pete
