Just checkout the source via git clone ...
Install Apache Maven 3 and run :
mvn clean install
There are 2 integration tests in fr.gwallet.market.SoaFailsIT :
- The first ask for a potato request and is given a potato response.
- The second ask for a carrot request and is given a potato response.
When using maven, a pre integration test goal launch a SOAPUI mock service corresponding to this contract.
With this contract, a market WebService is supposed to wait after potato or carrot requests.
The mocked WebService respond a good answer for any potato requests, but a bad answer for carrot request. In fact, any carrot request will receive a potato response. This mock is a very bad WebService.
The JAX-WS client can :
- make a call to the service,
- receive a bad answer that do not correspond to the request (a potato response in place of carrot response),
- all without error,
- not retrieving any information, because a potato will never be a carrot. Never.
Because, when debugging an application in production mode, we saw bad behavior, quite impossible behavior.
Showing the log, messages seems to be inconcistant. Request of type A is answered with type B. Today, we can not explain why the answered was randomly delivered, but when we force by mocking, we were very confused about the fact that the WS client stack never complains.
Nothing at the moment of writing this lines.
I was thinking that SOAP was a trustful stack with XML schema validation, and contract coupling. Now I'm wondering if it's not another boilerplate stack.