project_key: SOA

I crossed the issue when verifying SOA-3013. The original customer's requirement was for HttpRouter not to swallow exceptions and propagate them. This is now true in some cases including UnknownHostException (endpointUrl points to an invalid hostname). So this satisfies customer's scenario.
On the other hand, when the host specified in endpointUrl exists and only the rest of the URL is invalid (pointing to non-existing service), no exception is thrown. Just the message returned by a wen server on the host is placed in ESB message payload.
The customer was asking how they could recognize a problem except for examining the return message. In case of UnknownHostException, they receive an exception on the client side. In case of non-existing service, the action pipeline continues to execute following actions which can further modify the response and the client might not realize the issue. Please see the attached quickstart (ant deploy, ant runtest).
I think that these problems should be handle in the same way and an exception should be thrown instead of logging a WARN message.