Did you try to set in-interceptors in openejb-jar.xml? For an EJB I'm not sure you can do anything BTW. That said if you can reproduce the issue in a sample it can be interesting to understand why you get this.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2015-07-16 19:05 GMT+02:00 using namespace <[email protected]>: > Hi, Thank you for feedback > > I've tried CXF interceptors today, and here is what I clarified for myself: > > 1. The exception from my first post appears somewhere at the READ phase > 2. When I used handleFault with Message parameter at the READ phase I got > truncated top of the request Message for some reason > 3. The last line of the exception stacktrace is: > > at > > org.apache.cxf.binding.soap.saaj.SAAJInInterceptor.handleMessage(SAAJInInterceptor.java:223) > > As I understand it is SAAJInInterceptor that causes an error of XML > parsing. > So I tried to find out how to customize this interceptor, but I couldn't. > > Is it possible to customize the SAAJInInterceptor? > > > > > > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/Parse-SOAP-request-manually-tp4675503p4675513.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
