It might be a bit better to decide with the help of the content type of
the http header if it is xml or not!?
Cheers
Thomas
Thomas Termin schrieb:
There are some other problems in the old endpoints.
The first point is related to the fault which is generated after an http
status != OK. The provider endpoint assume that the content of the http
response is an valid xml which is in the most cases not right. The
problem then is that it crashes as soon the fault is parsed. My
solution/fix would be to allways set the calling exchange to status
error with the http response text as message.
The second problem is related to the ok status of the http client. It is
also assumed that the content of the response is valid xml. That might
be right for the most cases but is not sometimes. Actually there should
be a property or whatever which indicates the provider to do a syntax
parsing before it set the normalized message.
