If you want to access the XML payload please refer LoggingInInterceptor and LoggingOutInterptor interceptor. In simple way you you can extend these class and customize how you want it. Just follow same phase control the execution order using addBefore or addAfter methods.
On Tue, Jun 19, 2018 at 6:41 PM, Morein, Arnie <[email protected]> wrote: > FYI, the exception I'm encountering is: > > java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 > at java.util.LinkedList.checkElementIndex(LinkedList.java:555) > ~[?:1.8.0_172] > at java.util.LinkedList.remove(LinkedList.java:525) ~[?:1.8.0_172] > at org.apache.cxf.staxutils.OverlayW3CDOMStreamWriter. > writeEndElement(OverlayW3CDOMStreamWriter.java:89) > ~[cxf-core-3.1.15.jar:3.1.15] > > > From: Morein, Arnie > Sent: Tuesday, June 19, 2018 11:38 AM > To: [email protected] > Subject: Help with SOAP XML Logging > > I need to create four interceptor ancestor classes to log the SOAP XML of > an inbound or outbound message to the database. > > I've seen examples and some work to a point but mostly I'm just confused. > > I need clarification as to which phase to write them for: > > WS client outbound: ? POST_MARSHAL or MARSHAL_ENDING ? > WS client inbound: ? POST_PROTOCOL_ENDING or UNMARSHAL ? > > WS server inbound: ? PROTOCOL_ENDING ? > WS server outbound: ? PROTOCOL ? > > One of the examples I got off the CXF site seems to work for client code > (my application consuming a web service) but when I created a new > descendent for another client, an exception occurs deep inside stax code. > > This line: SOAPMessage saaj = message.getContent(SOAPMessage.class); > frequently returns nothing. Why? > > >
