I had similar problems with this "delete". It was in the debug version. Read somewhere that it is due to the fact that the dlls used are compiled with different debug-parameters which messes up the heap. Should be ok in the release.
It works without but then it should be a memory leak. In the case of returning complex types the delete is not done and I guess that memory responsability is put on the caller function. Not sure about this last note, so someone please correct me if I'm wrong. /Anders -----Message d'origine----- De : Falk Sippach [mailto:[EMAIL PROTECTED] Envoy� : vendredi 3 juin 2005 11:52 � : Apache AXIS C User List Objet : AW: Settings for Java Webservice (used by C++-Client) Hello Anders, thanks for soapAction-tag hint. I set the java2wsdl flag: -A operation java org.apache.axis.wsdl.Java2WSDL -l http://flak:8080/axis/services/Beantest -o ..\wsdl\Beantest.wsdl -n "urn:Beantest" -p"com.iez.spserver.ws.beantest" "urn:Beantest" -A operation -y rpc -u encoded com.iez.spserver.ws.beantest.BeantestWS java2wsdl only writes the operation name (without "servicename#"), but it works better now for my getBean-Methods. The generated client stubs are still buggy (Axis C++ 1.5 final). I had to comment out some "delete" (they try to free the pointer of int values). For example my getInt-Method has in stub BeantestWS a "delete Ret", which follows in an unhandled exception. I don't know why. But it's working without it. Is somebody out there who has got similiar problems? Falk. -----Urspr�ngliche Nachricht----- Von: Anders Eriksson [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 3. Juni 2005 09:21 An: Apache AXIS C User List Betreff: RE: Settings for Java Webservice (used by C++-Client) Hi, I am not creating the wsdl file my self. However, I believe that it was created with java2wsdl using some standard arguments. In fact, I did have some troubles with the wsdl file. Under the tag <wsdl:binding, <wsdl:operation there is a <wsdlsoap:operation tag. This tag had soapAction="" in the file given to me and it should be "WebserviceName#MethodName". If this doesn't help, I could probably get some more information about how the wsdl file was created. /Anders -----Message d'origine----- De : Falk Sippach [mailto:[EMAIL PROTECTED] Envoy� : jeudi 2 juin 2005 19:35 � : Apache AXIS C User List Objet : AW: Settings for Java Webservice (used by C++-Client) Hello Anders, thanks for providing your experiences. The first two steps I'm already using. It would be nice if you can tell me a bit more. Do you generate the wsdl-file from a Java interface (java2wsdl) or do you write it by your own? If you use java2wsdl, which command line parameter do you use. Can you send me a small example (Java interface and wsdl-file). Thanks for your help, Falk. -----Urspr�ngliche Nachricht----- Von: Anders Eriksson [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 2. Juni 2005 17:35 An: Apache AXIS C User List Betreff: RE: Settings for Java Webservice (used by C++-Client) Hi Falk, I have an Axis C++ client/Axis Java server using rpc. Corrected the following three things: 1) disable href/multiref on the server 2) slightly changing some code in AxisClient.dll SoapDeSerializer.cpp::getXSDType to allow soapenc:string 3) making sure the server doesn't return empty arrays (as AxisClient can't deserialize those) Well, not very beautiful but it works. /Anders -----Message d'origine----- De : Falk Sippach [mailto:[EMAIL PROTECTED] Envoy� : jeudi 2 juin 2005 17:16 � : Apache AXIS C User List Objet : Re: Settings for Java Webservice (used by C++-Client) Hello, I need some more help. Is there anybody who has successfully developed an Axis C++ client calling a Java Webservice? At the moment it's not working at all. Are there other products (C++), which work together with Java Axis webservices? I've read somewhere I should use doc/lit as message style. I've tried. First I've generated a wsdl-file with java2wsdl. Then I've created the server skeletons (wsdl2java) and the client stubs (wsdl2ws). But wsdl2ws fails with a not reproducable error: -------------------- java.util.NoSuchElementException at java.util.HashMap$HashIterator.nextEntry(Unknown Source) at java.util.HashMap$ValueIterator.next(Unknown Source) at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.addDocumentStyleInputMessageToMe thodInfo(Unknown Source) at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.setMethodInfo(Unknown Source) at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.getServiceInfo(Unknown Source) at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.generateWrappers(Unknown Source) at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.main(Unknown Source) Code generation failed. Please see errors above. -------------------- If I use rpc/lit, the stub code generation succeeds. But the soap messages look like this: -------------------- <getStringResponse> <getStringReturn>test string</getStringReturn> </getStringResponse> -------------------- There is no type definition and the client can't read any string. It works, if I use rpc/encoded. But then I have the problem with URI_XSD and URI_ENC (ok, I can fix it with the patch). And I can't get int values or complex types with ints inside. It still doesn't work in the 1.6 alpha from June 1st, 3 a. m. Maybe in the next nightly build it will work, because Adrian has changed it yesterday (after the last nightly build?). What may I do wrong? Please help. Thanks, Falk.
