Hi, There were still some outstanding issues with arrays at the release of Axis C++ 1.5. There has since been a lot of work in improving the design and workings of arrays, which is available in the 1.6 nightly builds - you may wish to try these to see if your problems have already been resolved.
Regards, Adrian _______________________________________ Adrian Dick ([EMAIL PROTECTED]) Tao Yang <[EMAIL PROTECTED]> wrote on 21/02/2006 23:52:33: > Just in case someone else may want to know my lesson here. > > It turns out this is happening because I always return a array whose > last item is null - I was paranoid before I dig into Axis C++ and afraid > of it won't know the size of the array so that that null is put in as > boundary indicator. However, nicely the Axis C++ does return the array > size; but fail to cope with my "null" boundary indicator and thought > error has happened. > > This does raise a question though: why Axis C++ can't handle a "null" > item? the java version process this nicely by the way. > > cheers, > Tao > > Tao Yang wrote: > > > Oops, I forget to say. Even the valid response is observed through > > the SOAPMonitor, the c++ client code is always reporting: > > "result.size = 0" > > What could be preventing it extract the strings from the message? > > > > Thanks, > > Tao > > > >> > >
