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.
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. How
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
Tao Yang wrote:
Hi,
Again with my Axis C++ 1.5 client running against th
Hi,
Again with my Axis C++ 1.5 client running against the Axis JAVA 1.3
server experiment:
I have a webservice has interface : String[] search(String getIgnored)
the java client handle it perfectly by the way.
My c++ client is a bit funky though. The stub generated has following
code (I add s
