On Aug 21, 2014, at 11:26 AM, Ed Bras <[email protected]> wrote: > Thanks for your feedback, > I think we have a misunderstanding here. > I would love to create a test-case if I would be able to understand how to > code it, which is what I am asking below. > > I want to use the logging interceptor with the newly Stax WWS4j, that uses > XmlStreamWriter. The current logging interceptors don't support this (see > details below). > So how can I use the logging interceptors with this ? (or are there any > logging interceptor that does support this which I am not aware of?) > > If my description is unclear, let me know,
The logging interceptors log what gets sent in/out on the wire. They log what is written to the output stream. They should be supporting this just fine with the StAX based security stuff. I’m not sure what issue you are seeing with the logging. Dan > - Ed > > >> -----Original Message----- >> From: Colm O hEigeartaigh [mailto:[email protected]] >> Sent: donderdag 21 augustus 2014 17:11 >> To: [email protected] >> Subject: Re: Issues upgrading to 3.0.1 >> >> Could you create a test-case that shows the issue? >> >> Colm. >> >> >> On Thu, Aug 14, 2014 at 9:52 AM, Ed Bras <[email protected]> wrote: >> >>> Can somebody please give me some pointers about logging the >>> XmlStreamWriter with the Stax WWS4j (see details below). >>> Thanks, Ed >>> >>>> -----Original Message----- >>>> From: Ed Bras [mailto:[email protected]] >>>> Sent: maandag 11 augustus 2014 21:32 >>>> To: [email protected] >>>> Subject: Issues upgrading to 3.0.1 >>>> >>>> I encounter some issues upgrading from 2.7.11 to 3.0.1 Please some >>>> help (I am following the migrating guide). >>>> >>>> >>>> >>>> First, to be able to see what the real problem is, I try to log the >>>> outgoing soap message. >>>> >>>> However the current LoggingOutInterceptor supports OutputStream and >>>> Writer and not the XMLStreamWriter instance that is contained in >> the >>>> soap message that I send (I noticed this during debugging). >>>> >>>> How can I log the soap message? >>>> >>>> >>>> >>>> Details: >>>> >>>> I am using ws-security through the WSS4JStaxOutInterceptor and >>>> WSS4JStaxInInterceptor interceptors. >>>> >>>> I am using the mechanism as described in LINKE >>>> <http://davidvaleri.wordpress.com/2010/09/15/signing-ws-addressing- >>>> headers-i >>>> n-apache-cxf/> , and changed it to using the Stax interceptors. >>>> >>>> >>>> >>>> Please some tips how to log the message so I can see what I am >>>> sending and trying to solve the other upgrade issues (example: >> WARNING: >>>> Security processing failed (actions mismatch)). >>>> >>>> >>>> >>>> - Ed >>> >>> >>> >> >> >> -- >> Colm O hEigeartaigh >> >> Talend Community Coder >> http://coders.talend.com > -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
