BPEL engine sets wrong Content-Type on calling external web service

[steveNZ]

Hi,

I have a WSDL for an external web service (which is actually running in Websphere locally) and have implemented it as a partnerlink on a BPEL diagram in an SOA composite project.
The binding style is Document and if you use SOAPUI to test it it works fine. Tracing on the web service's server shows the SOAP request coming in. It has a content-type of text/xml, as expected. If I do a JUnit test from NetBeans based on this WSDL it also works. BUT if I do a full test and call my BPEL process the invocation of this service from BPEL fails. On the trace I see it now has Content-type of application/xop+xml. Why would the BPEL engine change this? I just accepted the usual defaults when I created the PartnerLink and the Invoke.

As far as I'm aware I'm just using SOAP1.1. This is NetBeans 6.5 with Glassfish 2.1. I tried with NetBeans 6.7 and it got worse, not better.
Would appreciate any advice?
Have attached small project, WSDL is POTValidate7Services.wsdl.

Thanks
Steve