I'm doing that as well. There are minor differences between the two in the versions of the XML schemas but nothing other than that. I can see that at least I am able to connect and call my method. Its just that the parameters are all reset to null. I'll look some more.
Thanks for the suggestion. Elham > -----Original Message----- > From: Bono, Chris [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 10, 2001 10:43 AM > To: '[EMAIL PROTECTED]' > Subject: RE: interoperating between Apache and Idoox > > > I just got through intergrating MSSoap client side with our > apache soap server. If you use the TcpTunnelGui you can > watch the xml messages go back and forth. What I did was > to make a request from the apache soap client and snipped > the results out of the tunnel gui. Then I made a request > from the MSSoap client and did the same. From there I just > looked at the differences in the messages which allowed > me to see what was going on and where the issues were. > > Good luck, > Chris > > >>-----Original Message----- > >>From: Elham Chandler [mailto:[EMAIL PROTECTED]] > >>Sent: Wednesday, October 10, 2001 12:04 PM > >>To: Soap-User@Xml. Apache. Org > >>Subject: interoperating between Apache and Idoox > >> > >> > >>Hi, > >> > >>I'm currently writing an Apache SOAP client that will talk to a Idoox > >>WASP SOAP server. It appears that I can connect to the server > >>but all the > >>parameters that I pass as arguments to my method are all null > >>when it gets > >>to the WASP SOAP server. > >> > >>My suspicion is that Apache SOAP puts newlines at the end of > >>the generated > >>SOAP. However the WASP SOAP does not expect to get newlines. > >>Is there a > >>way we can avoid the newlines that are generated by the SOAP calls ? > >> > >>Also, has anyone ever tried interoperating Apache Client and > >>WASP server > >>like this ? > >> > >>Any help will be much appreciated! > >> > >>Elham Chandler > >>Interwoven Inc. > >>
