| Info |
|---|
Since version 0.4 |
RequestRequest/response tracking functionality allows to save internal communication between routes or communication with external systems into database.
Functionality is disabled by default - see see ohf.requestSaving.enable parameter to enable it. There is another parameter parameter ohf.requestSaving.endpointFilter that defines pattern for filtering endpoints URI which requests/response should be saved. See configuration for more details.
...
Default implementation uses standard Camel events that has one possible disadvantage - it's necessary to join request and response together (= two Camel events) and if exchange is changed from sending request until response receive (e.g. using wireTap) then it's not possible to join it. But this limitation is mainly for internal communication, there is no problem with saving request/response to/from external system.
...