The best suggestion I would have is to create a CXF client from the WSDL and try that. Capture the SOAP message from it and then also capture the message from the Delphi client and compare them.
USUALLY, a null param is the result of the client doing the namespaces wrong. For example, your schema has: elementFormDefault="unqualified" if the SOAP message has something like: <foo xmlns="http://.....";> to set the default namespace, that will cause an issue. Dan mOn Monday 06 October 2008, Alexandre A. L. Costa wrote: > Thanks for the tip. > > There aren't much "abornal" details for this service. No Exceptions to > be thrown or Security Policy yet. (Though in near future we'll need > to use SSL conection) > Just send an String and receive an String for response. > > We have been doing same tests that make us think os problems with > client's SOAP message formation too. > The SOAP message sent by the Delphi client is kind wierd. > > We already tried some "generic" client services on web (and they > function quite well). > Now we're focusing (as the sugestion) on proving that the problem are > on client side. > > Thanks again. -- J. Daniel Kulp [EMAIL PROTECTED] http://www.dankulp.com/blog
