SOAP headers being removed from proxied message

I'm trying to use the WSO2 ESB to proxy between two Apache Tuscany instances.  The instances are each running the Tuscany Tours sample app spread over two servers.  Tuscany sticks a bunch of stuff in the SOAP header to support doing async callbacks.  When I pass the message thru WSO2, all the stuff in the header completely removed. Here's an example of what is being sent to the ESB (slightly edited, because Axis chokes on the lack of a wsa:Action tag): <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header><wsa:From xmlns:wsa="http://www.w3.org/2005/08/addressing"><wsa:Address>http://mitch-linux.corp.shutterfly.com:8084/Hotel/SearchCallback</wsa:Address><wsa:ReferenceParameters><tuscany:CallbackID xmlns:tuscany="http://tuscany.apache.org/xmlns/sca/1.0">HotelSearchCallbackID-f8def3a6-9814-4a83-9aad-68aaa4bae3f6</tuscany:CallbackID><tuscany:ConversationID xmlns:tuscany="http://tuscany.apache.org/xmlns/sca/1.0">1108b941-f4f9-4122-b1cc-0b808fd2bf6a</tuscany:ConversationID></wsa:ReferenceParameters></wsa:From> <wsa:Action xmlns:wsa="http://www.w3.org/2005/08/addressing">searchAsync</wsa:Action> </soapenv:Header><soapenv:Body><_ns_:searchAsynch xmlns:_ns_="http://common.tuscanyscatours.com/"><arg0 xmlns:ns2="http://common.tuscanyscatours.com/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="tripLeg"><fromDate>06/12/09</fromDate><fromLocation>LGW</fromLocation><id>f8def3a6-9814-4a83-9aad-68aaa4bae3f6</id><noOfPeople>2</noOfPeople><toDate>13/12/09</toDate><toLocation>FLR</toLocation></arg0></_ns_:searchAsynch></soapenv:Body></soapenv:Envelope> And this is what gets passed on.  Note that the Header tag has been cleaned out of all the good stuff Tuscany added for itself: <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header /><soapenv:Body><_ns_:searchAsynch xmlns:_ns_="http://common.tuscanyscatours.com/"><arg0 xmlns:ns2="http://common.tuscanyscatours.com/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="tripLeg"><fromDate>06/12/09</fromDate><fromLocation>LGW</fromLocation><id>f8def3a6-9814-4a83-9aad-68aaa4bae3f6</id><noOfPeople>2</noOfPeople><toDate>13/12/09</toDate><toLocation>FLR</toLocation></arg0></_ns_:searchAsynch></soapenv:Body></soapenv:Envelope> The only thing I'm doing before passing the message on is to log it.  I've tried messing with various settings on the proxy config, but nothing changes.  Here it is from the synapse config file:    <syn:proxy name="HotelSearch" transports="http" startOnLoad="true" trace="enable">         <syn:target>             <syn:endpoint>                 <syn:address uri="http://mitch-linux.corp.shutterfly.com:8086/Hotel/Search"/>             </syn:endpoint>             <syn:inSequence>                 <syn:log level="full"/>             </syn:inSequence>             <syn:outSequence>                 <syn:log level="full"/>                 <syn:send/>             </syn:outSequence>         </syn:target>         <syn:publishWSDL uri="http://mitch-linux.corp.shutterfly.com:8086/Hotel/Search?wsdl"/>     </syn:proxy> So, does anyone know what would cause the ESB (or maybe its Axis) to rip out all the header info?  It seems to me that unless explicitly told, it should leave everything alone.