For situations like this, I developed a simple Camel component that uses the old SAAJ classes instead of JAX-WS. That way, you get full access to the whole XML document. Combined with XSLTs to form the request documents and working with overly complicated or non-standard SOAP services became far easier!
On 11 July 2014 04:10, Aki Yoshida <elak...@gmail.com> wrote: > That would be one possibility but you would be losing the exact form > (the serialised wire message isn't the same as the original wire > message). > > If you really need to get a cloned wire message at your camel route, > one option would be to write a CXF interceptor to capture the original > message and pass it to the camel route as an additional runtime > context object. Maybe, actually I think there is no other option. > > If a DOM object is acceptable, you can also write a CXF interceptor to > grab it within CXF and pass it to camel. > > regards, aki > > > 2014-07-01 19:16 GMT+02:00 ychawla <premiergenerat...@yahoo.com>: > > Hello All, > > We use payload mode to process our CXF messages. It is very convenient > and > > will properly process the Soap Headers, SAML assertions, WS-Security > headers > > etc. > > > > I have a requirements to get the entire raw Soap message in my camel > route > > and call a processor with it. There are other ways to do this, but the > > requirement explicitly states that the raw soap message is required. > > > > How can I get the entire raw soap message in Payload mode? I guess I > could > > reconstruct it manually by looping through the soap headers and > re-creating > > the DOM but is there another way to get at it? > > > > Thanks, > > Yogesh > > > > > > > > -- > > View this message in context: > http://camel.465427.n5.nabble.com/Getting-entire-Soap-Message-with-header-and-body-in-Payload-mode-tp5753162.html > > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Matt Sicker <boa...@gmail.com>
