Really broken soap message

From: Ryan Shoemaker - JavaSoft East <Ryan.Shoemaker_at_Sun.COM>
Date: Tue, 09 Jan 2007 20:55:23 -0500

I upgraded to jaxws-ri-21 hudson-1608 and code that has been working
fine for months now sends a really broken soap message:

<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
   <S:Header>
     <To xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://tini.east.sun.com:8080/wstx-services/wscoor/coordinator/register</To>
     <Action xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://schemas.xmlsoap.org/ws/2004/10/wscoor/Register</Action>
     <ReplyTo xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">
       <MessageID xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">uuid:248c24c6-7f0c-40ae-89cf-3b862c47a97b</MessageID>
       <jaxws:objectId xmlns:jaxws="http://jax-ws.dev.java.net/xml/ns/" xmlns="http://schemas.xmlsoap.org/ws/2004/10/wscoor" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns2="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:ns3="http://java.sun.com/xml/ns/wsit/coord" xmlns:ns4="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">3d3bc0af-58e2-4ed1-a4a1-2e6d2f7a1708</jaxws:objectId>
     </ReplyTo>
     <S:Body>
       <Register xmlns:ns2="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns="http://schemas.xmlsoap.org/ws/2004/10/wscoor">
         <ProtocolIdentifier>http://schemas.xmlsoap.org/ws/2004/10/wsat/Durable2PC</ProtocolIdentifier>
         <ParticipantProtocolService>
           <ns2:Address>http://tini.east.sun.com:3861/wstx-services/wsat/2pc</ns2:Address>
           <ns2:ReferenceParameters>
             <jaxws:objectId xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:jaxws="http://jax-ws.dev.java.net/xml/ns/">6bd56e6c-d084-4589-975f-bce39b67e533</jaxws:objectId>
           </ns2:ReferenceParameters>
         </ParticipantProtocolService>
       </Register>
     </S:Body>
   </S:Header>
</S:Envelope>

The <S:Body> is contained within the <S:Header>.

Anyone know why this might be?

I'll investigate more tomorrow, but I wanted to get this issue out
in case someone knows what's going on... There was a jump in the
jaxws-ri-unit-21 test failures as of jaxws-ri-21 hudson-1607 which
corresponds to a commit Vivek made for to add support for multiple
body parts in the SOAP messages. I'll roll back to hudson-1605
tomorrow and see if that makes my issue go away.

--Ryan