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.
--
Alexandre Augusto Leite Costa
Desenvolvimento
Dextra Sistemas
www.dextra.com.br
+55 19 3256-6722 / 9208-7944
Glen Mazza wrote:
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
