I would have them test your web service with SOAP UI. If it works with SOAP UI but not their client, greater focus should be on the client instead of the web service provider.
Can you tell us something about the web service operation--anything strange or out-of-the-ordinary about the parameters of the SOAP request or response--or is it just a bunch a simple types, etc. Are you using WS-Security--that could be causing some incompatibilities. Glen Alexandre Costa wrote: > > Good Morning, > > I'm using CXF 2.0.7 to publish and acess a WebService in my application. > > The project was going well till one of the partners decide to create its > WebService client in Delphi 2007 and other one in .Net (don't know the > language or version for sure). > > The result detected is that they find the service, but the message sent > has > null in their parameters. > > Same one already see this problem? (or better, knows a solution) > > Thanks, > -- > Alexandre Augusto Leite Costa > Desenvolvimento > Dextra Sistemas > www.dextra.com.br > +55 19 3256-6722 / 9208-7944 > > -- View this message in context: http://www.nabble.com/Fwd%3A-Problems-with-non-Java-clients-tp19839463p19842983.html Sent from the cxf-user mailing list archive at Nabble.com.
