fixed bug in DynamicHeaderProcessor
XmlXpathValidationProcessor is not tied to incoming xml anymore (the response code is configurable), can also be used to validate outgoing xml etc
setting throwable as cause on AsyncHttpClientProcessorException in callback onThrowable to make sure we can set response code based on this ie ConnectException == 502 etc
responsefilter and response schema validation processors config interfaces now specify boolean doRun methods to let implementations decide if these processors should run at all. Some responses shouldn't be filtered / validated but rather redirected via a Location header for example
Merge branch 'xpathvalidations'