The "mod_gsoap" I'm refering to is the IIS ISAPI gsoap_win not the Apache version (we haven't tried that yet) but here is some more information anyway:
1. Windows XP 2. Microsoft Visual Studio .Net 2003 3. 2.7.11 4. Hmm, the one included with gSOAP Best regards, Jacob --- In [email protected], Jayaram Ganapathy <jayaram.ganapa...@...> wrote: > > Hi Jacob, > > Can you please give some more information. > > 1) The platform where you compiled ? > 2) The Compiler and version ? > 3) The version of gSOAP ? > 4) The version of mod_gsoap which was inside the tag gz file? > > > I can try it out and document for this community. I can try in Solaris and > windows. > > Thanks and Regards, > Jayaram > > > > > > nielsen.ja...@... > Sent by: [email protected] > 23-03-09 11:26 PM > Please respond to > [email protected] > > > To > [email protected] > cc > > Subject > [gsoap] mod_gsoap actually works (with some modifications) > > > > > > > > > > Hi everyone, as many others we've had some problems with the IIS mod_gsoap > included with gSOAP. > > We finally solved it! > > We expect to release our changes back to the gSOAP project as soon as > possible. > > 1. The first obstacle was getting mod_gsoap to compile. As others have > discovered, this can be solved by linking with a soapC.c[pp] from the > client application (I suspect we can just as well use the output from > soapcpp2.exe with an empty .h file.) > > 2. The mod_gsoap project is part C++ and part C but as the struct/class > "soap" is different under C++ and C, we had to compile everything as C++ > (adding the /TP flag to the compilation) so that all parts of the program > agreed on the layout of the struct/class "soap". This solved the problem > with mod_gsoap not returned a correct answer. > > After solving these "minor" problems, we succeeded in using mod_gsoap with > the calc-server in the mod_gsoap project and with the calc++ sample in the > gSOAP project proper. > > Best regards, > > Jacob > > > > > --- > > This e-mail may contain confidential and/or privileged information. If you > are not the intended recipient (or have received this e-mail in error) > please notify the sender immediately and destroy this e-mail. Any > unauthorized copying, disclosure or distribution of the material in this > e-mail is strictly forbidden. >
