On Wed, Dec 5, 2012 at 10:41 PM, Scott England-Sullivan
<sully6...@gmail.com> wrote:
> The following should allow you to see both:
>
>
> from("servlet:///proxyWebService/api/?matchOnUriPrefix=true")
> .log("Request message: ${body}")
>
>
> .to("https4://realWebService:8443/api/?bridgeEndpoint=true&throwExceptionOnFailure=false")
> .log("Response message: ${body}");
>
Mind about streams as if you log the message body, it may not be
re-readable again for the actual response.
See about stream caching
http://camel.apache.org/stream-caching.html
Camel sits on top of 3rd party frameworks. So in these cases they may
offer some logging capabilities for that.
Maybe there is a logger name you can set to DEBUG or TRACE to see the raw data.
> Hope this helps.
>
> Best Regards,
> Scott ES
>
> On Wed, Dec 5, 2012 at 4:38 PM, rouble <r.ou...@gmail.com> wrote:
>
>> I have a camel route setup to proxy a web service as follows:
>>
>> from("servlet:///proxyWebService/api/?matchOnUriPrefix=true")
>>
>> .to("https4://realWebService:8443/api/?bridgeEndpoint=true&throwExceptionOnFailure=false");
>>
>> How can I see the inbound and outbound HTTP Requests and Responses? I
>> don't need any other camel logs for my purpose just the wire logs.
>>
>> tia,
>> rouble
>>
>
>
>
> --
> --
> Scott England-Sullivan
> Apache Camel Committer
> Principal Consultant / Sr. Architect | Red Hat, Inc.
> FuseSource is now part of Red Hat
> Web: fusesource.com <http://www.fusesource.com> |
> redhat.com<http://www.redhat.com>
> Blog: sully6768.blogspot.com
> Twitter: sully6768
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib...@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
