Thank you Daniel for your hint,
I already write two Interceptor classes (in/outbound) for this purpose,
and it works.
Another question is, how can I bring back the soap-envelop, which is
then read from a file
or from the database, back into the generated (wadl2java) cxf skeleton.
Do you know a way to do this.
Thanks, Alex
Daniel Kulp schrieb:
On Thu January 14 2010 1:31:04 am Alex wrote:
Hi!
How can I extract the hole raw transported message including
HTTP-Headers, Mime-Headers, SOAP-Message itself and
save them to file?
Normally, the soap message itself is discarded as it's read in. (streamed) as
it's not needed. Thus, if you need it, you'll need to write an interceptor to
handle it. There are really two options:
1) You COULD just configure in the SAAJInInterceptor and grab the soap message
as the SAAJ object model and do whatever you want.
2) You could grab the source code for the LoggingInInterceptor and modify it
for your purpose. It already pulls in the full byte stream, if it's over a
threshold, saves it in a file, resets the streams to the file stream, etc...
It also prints things like the HTTP headers so that information is available
there as well.
Dan
Is there a possibility to bring the save file back to the cxf context?
Thank you!
Alex
