Weblogic 8.1 throws javax.xml.soap.SOAPException: There should be only one Content-Type MimeHeader [SWS-37]

[gregturn]

Arjen Poutsma opened SWS-37 and commented

When running any spring-ws app on BEA Weblogic 8.1, the following exception is thrown:

javax.xml.soap.SOAPException: There should be only one Content-Type MimeHeader.

Apparently, Weblogic returns the Content-Header as part of the headers retrieved by getHeaderNames(). We should check for this.

---

Affects: 0.9, 0.9.1, 1.0 M1

[gregturn]

Arjen Poutsma commented

I've fixed this particular bug, and spring-ws runs on Weblogic 8.1, but it is not easy.

You basically have to override every XML api provided WL, and use more recent versions instead. This basically means putting a recent Xerces, Xalan, and XML-APIs in the WEB-INF/lib, using the AxiomSoapMessageFactory, and using the following in the weblogic.xml:

<weblogic-web-app>
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
</weblogic-web-app>